Website set as application?

[Juan T. Llibre]

OK...

If you open the VS.NET 2002 project in VS.NET 2003,
VS.NET 2003 will attempt to convert the project
and report back any problems which it found.

It also should create a backup of your 2002 project files.

Then, when you attempt the build, you may find build errors.
You would then have to determine the correct way to fix them.

What I would do is *not* try to open the old project.

I'd create a new, empty, web project, in VS.NET 2003,
and use the "add existing items" feature of VS.NET
to thenew project.

Then, I'd look in the previous project's VS.NET project file,
identify the references which don't exist in the empty
project, and add them to the new project.

That would ensure that the references are correct for .Net 1.1

Then, I'd compile the new version in VS.NET 2003.

You still might get build errors which you'd have to fix,
but you won't be saddled with conversion problems
should there be any.

Another thing to watch out for is whether the "old" project
had sub-projects in it.

Some web applications use more than one project.
You'd have add the additional projects, too, if there's any.

Hopefully it's a one-project solution and it'd be simpler.




Juan T. Llibre
ASP.NET MVP
===========

 

[Juan T. Llibre]

re:

I'd create a new, empty, web project, in VS.NET 2003,
and use the "add existing items" feature of VS.NET
to thenew project.

That should read :

I'd create a new, empty, web project, in VS.NET 2003,
and use the "add existing items" feature of VS.NET
to add the source files in the old project, one by one,
to the new project.



Juan T. Llibre
ASP.NET MVP
===========