I've got a .NET 1.1 application which I'm trying to convert to 2.0. When I try to convert the code using MS's converter, I get:

Configuring web site to ASP.NET 2.0 failed. You may need to manually configure this site for ASP.NET 2.0 in order for your site to run correctly.

Then, after fixing the myriad warnings and errors VS 2 issued, I get this when I try to run:

Unable to stasrt debugging on the web server. The server does not support debugging of ASP.NET or ATL Server applciations. Click Help for more information on how to enable debugging.

Help contains no information on enabling debugging that I can find, however. Is there some magical order of steps necessary to get VS 2.0 to convert 1.1 applications correctly on the first try?

Considering the lack of responses, it appears I am the only person struggling with this problem, as usual. Should some other poor souls suddenly find themselves confronted with this same problem, though, I believe I have resolved my problems converting the old ASP.NET application. The conversion wizard just would not work with this project no matter what I tried.

So, I had VS 2005 create a new web project for me with the desired name. Then I manually added each of the form and class files from my old ASP.NET application to the new project. After numerous new error and warning corrections (v2 is so much pickier), I am now able to compile using the debugger.

Hi Ron,

Did you try to upgrade the site with the new "Web Application Project" feature? This new project model, more closely mimicking the behavior of ASP.NET 1.x *should* enable you to upgrade 1.x projects to .NET 2.... More information can be found here:

http://webproject.scottgu.com/

A bit late, but it might help....

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: Eraser by Nine Inch Nails (Track 11 from the album: The Downward Spiral) What's This?

Nope. I just tried using the built-in wizard, which didn't seem to do much except break my code badly. I'm now deeply into manual conversion and probably don't want to go back and start over unless this coverter will somehow avoid the zillions of errors I'm now getting for silly things like changing "<BR>" to "<br/>" because the tag is in mixed case and also missing the closing "/" that VS 2005 now seems to need where old VS did not. It wouldn't be so bad if old VS hadn't created most of the problems I'm now having to fix. TYVM once again, MS! :(

If you don't *want* to fix the errors, you could try setting the xhtmlConformance setting in the web.config file. This influences the way the mmarkup is rendered, and may also change te validation scheme for VS 2005:

<system.web>
  <xhtmlConformance mode="Legacy" />
<system.web>

Other modes are strict and transitional. Not sure if that fixes your problems, but it;s worth a try of you're willing to live with non XHTML markup.

Look at it from the bright side: it has finally been fixed in VS 2005. Indeed there's a lot of 1.x mess to clean up, but it should be better from this point onwards....

The project I pointed you to adds a new project type in VS 2005, so you can use the 1.x project model, where a site is based on a project and compiles to a single assembly. It's meant especially for working with 1.x style projects, so it might do the trick for you....

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.
While typing this post, I was listening to: Jennifers Body by Hole (Track 5 from the album: Live Through This) What's This?

I certainly don't *want* to fix all these errors. OTOH, it would sure be nice if my pages behaved correctly, and for many reasons, some of which I admit causing myself, they don't always do so. :D So, I think I would be better off biting the bullet now (bullets missing the closing </li> tag are another example of malformed html caused by old VS, btw) than trying to figure out some bizarre behavior down the road. Thanks for the alternative, though, should I find myself needing to convert something more quickly.

Yeah, I agree. It's better to clean up the mess right now, and use valid XHTML generated by VS from now on. The HTML editor behaves pretty well, a million times better than the 2003 version...

Imar
---------------------------------------
Imar Spaanjaars
Everyone is unique, except for me.

I agree! It hasn't eaten any of my HTML so far, and I am making MASSIVE changes to clean up 1.1's mess, so I'm glad for that small favor.

Test