I am having problem getting the MS Visual Studio Remote Debugger to connect to my local IE instance as it is running as a 64-bit rather than a 32-bit process.
Every time I try to run it currently in Visual Studio I get the The 32-bit version of the Visual Studio Remote Debugging Monitor (MSVSMON.EXE) cannot be used to debug 64-bit processes or 64-bit dumps”.
Investigating a bit, I think I have narrowed it down to the web asp service being run as a x64 process rather than a x86 (which both Visual Studio, and the silver light application are running as). I confirmed it as running as a 64-bit process by trying to “attach” visual studio to the process when the application was running in the ASP.Net Development Server. Converting PDF page to jpg in 32-bit servers, showing jpg image from pdf in asp.net page.
Simply put: Is there a setup I am actually overlooking someplace to oblige Aesthetic Workshop to operate the ASP.Net service as a 32-bit process? I have reviewed utilizing a variable in the web.config treatment pool to make use of 32-bit (using the enable32BitAppOnWin64 config option), however it seems to be to merely function in IIS, not ASP.net Dev web server.
Any type of thought and feelings?
Edit For Clarity: I am actually running Microsoft window 7 64-bit, Aesthetic Center 2010 (which is actually managing as a 32-bit procedure). Currently it is introducing ASP.NET Development Server (not IIS) to throw the rear end web service. I am hoping I may simply “correct” this using a setting, however or even my back-up will be actually to operate IIS Express.
IIS Manager/Application Pools-> decide on the correct pool for your application/Advanced Settings/Enable 32-Bit Applications-> set it to real!
I possessed issue similar to this previously which cost me 1-2 days, hope this assists!
Examine also Project/Properties/Build/ Platform intended-> this need to be actually Any sort of Central Processing Unit.
I am actually not managing a complete blown IIS hosting server for my dev atmosphere. Rather, I am actually simply utilizing the ASP.Net Progression web server (which receives launched by Visual Studio). Probing around, I discovered many pointers concerning transforming the environment on the manufacturing web server, but none for setting up the ASP.Net Development server.