Last post Dec 06, 2012 05:30 AM by ahmedilyas
Nov 27, 2012 10:30 PM|ahmedilyas|LINK
So I have an old project that my client has which is .NET 1.1 and cannot be upgraded to even .NET 2.0 as bare minimum.
So I am using a VM environment with WS2008R2 + all updates and have VS .NET 2003 installed and IIS 7.5
I managed to get it to talk to IIS 7.5 and setting the apppool to run 32 bit apps. I can now create web projects - great!
But when I run within VS.NET 2003, I ALWAYS get this error and not sure where to go from here:
--------------------------- Microsoft Development Environment ---------------------------
Error while trying to run project: Unable to start debugging on the web server. There is no managed code running in the process. In order to attach to a process with the .NET debugger, managed code must be running in the process before attaching.
Click Help for more information. --------------------------- OK Help ---------------------------
of course, if I open up IE and browse to the website - it runs fine but I NEED it to run within VS.NET 2003 so I can debug....
Nov 28, 2012 01:37 PM|ahmedilyas|LINK
Nov 29, 2012 04:15 AM|Angie xu - MSFT|LINK
using a VM environment with WS2008R2 + all updates and have VS .NET 2003 installed and IIS 7.5
ASP.NET 1.1 is not supported or compatible with IIS 7.5, but Virtual Machine can prevent changes to system.
So whether there is something wrong with .NET 1.1 on Windows 2008 R2, you could try this about installing .NET 1.1 on Windows 2008 R2.
And check whether helpful to you.
Dec 06, 2012 04:11 AM|ahmedilyas|LINK
Thanks. I already have done this however this does not answer the question about being able to debug within VS2003/run the web project with debugging on WS2008R2 (which has .NET 1.1 installed and configured).
running the web site request works just fine. serves the page fine. but when running VS2003 and you are debugging - it fails with the error message stated in my opening thread :)
Dec 06, 2012 05:30 AM|ahmedilyas|LINK
this fixed it:
To install on Windows 2008 Server – click Start and then “Server Manager”.
Under Web Server (IIS), click Add Role Services.
Ensure that IIS Metabase Compatibility is installed.
I installed .Net 1.1 in the following order:
I still got a compatibility warning, but chose “Run Program” to continue.
Installing Service Pack 1 is likely to require a reboot.
Following the steps in option 2 made ASP.NET v1.1.4322 available on my ISAPI and CGI Restrictions dialog, but was disabled by default. Open Internet Explorer, click on your server name and choose ISAPI and CGI Restrictions from the IIS section. Enable ASP.Net
v1.1.4322 as a valid ISAPI extension.
We need ASP.NET 1.1 to ignore IIS configuration sections, so open machine.config for Framework 1.1 (%windir%\Microsoft.NET\Framework\v1.1.4322\config\machine.config) and add the following towards the end of configSections.
1: <section name="system.webServer" type="System.Configuration.IgnoreSectionHandler,
2: System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
I now needed to tell my application to use the application pool ASP.NET 1.1. Use IIS Manager, choose the site that you are working with and choose “Advanced Settings”. Adjust the application pool to use ASP.NET 1.1 which will use .Net Framework 1.1.
IIS runtime detected that I was running on a 64 bit operating system, so it attempted to load .net framework configuration from Microsoft.Net\Framework64, but this doesn’t exist for .Net Framework 1.1. The solution is to copy the 32 bit version into the
appropriate 64 bit folder.