Is there any problem with using XP x64 and vs.net 2003 for developing 32Bit window applications
Thanks
VS.NET 2003 and XP x64
Hot Topic
- openssl pem and .NET
- memory leak in window.open() method
- connections over internet
- How do I set up remoting with VS 2005?
- 2 projects same solution
- Receiving outside events (Messages)
- bug in Int32.Parse
- TransactionScope and TableAdapters
- Impossible Question
- ILGenerator.BeginCatchBlock() & ILGenerator.EndExceptionBlock() emit unwanted 'leave' instruction
.NET Development
- WSE/DIME - WSE352: The size of the record uuid:{g-u-i-d} exceed its limit
- The conversion of a char data type to a datetime data type resulted in an out-of-range datetime
- Is there any bug in RevokeCertificate() of IcertAdminLib
- adding new record best practice?
- Process.Start() of xcopy only works under the debugger?
- XML TO MS WORD2003
- CodeDOM - Reflection question
- How can I extract a string from a string?
- Need help with editing XML files in ASP.NET 2
- xml serialization problem
VS.NET 2003 and XP x64
mmikey121
When debugging an ASP.NET application using VS.NET 2003 on XP x64 I noticed that the w3wp.exe *32 process does not seem to end when selecting "Stop Debugging". I can observe the process continuing to run in Windows Task Manager.
To verify that the process is continuing to run the thread I initiated and then attempted to stop, I sent some output to the VS.NET "output" window using WriteLn. After I start and then stopping the debugger the w3wp.exe *32 process was still running, but output was no longer going to the output window in VS.NET. However, if I start the debugger again on the same project, I begin getting output for my new debug PLUS output from the original debug that I supposedly stopped--although, based on the progress information I put in the output, the original thread seems to have continued to run in the background even after I used "Stop Debugging".
This effect seems to be cumulative such that if I start/stop X number of debuggers, each thread seems to run in the background until completion. The only way I seem to be able to stop code that I am debugging from running is to end the w3wp.exe *32 process using Windows Task Manager.
dpollo
swebber27
VS.NET 2003 should be fully supported on XP x64.
Are you having trouble with that combination
Thanks,