All geek questions in one place

This is a 32-bit ASP.NET application running on 64-bit Windows LARGEADDRESSAWARE

I have an existing 32-bit ASP.NET application that uses 32-bit unmanaged DLLs.

If I run this on a 64-bit OS, will it automatically LARGEADDRESSAWARE (i.e. have access to the full 4 GB of virtual memory)?

If not, what can I do to do this LARGEADESSESSAWARE?

Googling raised this question , but he lacks the answer to the above question.

EDIT

This blog assumes that the ASP.NET 1.1 workflow is LARGEADDRESSAWARE, but does not talk about ASP.NET 2.0:

If the system boots with / 3Gb, enable boot.ini (only Enterprise Editions and Data Center Windows 2000 and all versions of Windows XP and Windows Server 2003 are supported), and the process associated with / LARGEADDRESSAWARE can "see" 3Gb. Aspnet_wp.exe is related to what is in version 1.1 and may benefit from this.

EDIT 2

This is another blog that assumes that 32-bit ASP.NET LARGEADDRESSAWARE applications, but does not mention the version of ASP.NET

We found components that were hosted in ASP.NET using memory> 2 gigabytes of space

I must say that I am amazed at the lack of authoritative published information on this issue.

+3
source share
2 answers

Windows 2003 SP2, , 32- ASP.NET LARGEADDRESSAWARE 4 .

:

  • w3wp.exe(32- IIS) "dumpbin/headers". , LARGEADDRESSAWARE .

  • 32- ASP.NET, 2 : .

, Windows 2008/IIS7, .

+4

, . , IIS 64- ( WOW). , 32- DLL 64- .

asp.net 64- ( ). 32- , 32- DLL. 64- . , ASP.NET 32- , , 32- IIS 64- . - 32- DLL , 64- . 32- 64- , "" .

ASP.NET ( , ) 64- , 32- .

-1

Source: https://habr.com/ru/post/1721704/

More articles:


All Articles