Wednesday, 21. December 2005
VS.Net 2005 Rewrites Old Web Projects on First Open12/21/2005 08:22 PM
This is pretty wacky for a development
environment to do. When you open an old VS.Net 2003 web project,
it rewrites a lot of your source files and moves files around to new directories
(although it does warn you before you do this). I can understand
changing configuration files or project files, but this is a bit too much:
- Your old "Web References"
subdirectory with all your web services references has now been renamed
App_WebReferences. You can no longer look at or edit the web services
proxy code; this was useful in .Net 1.1 when we had to hack in WSE 2.0
support.
- All your non-ASPX code is moved into
an App_Code subdirectory.
- Your ASPX files are modified to be "partial
classes" instead of private classes. The web designer initialization
code is now hidden from your ASPX file and from you.
- Adds every file in your project directory
(including map files and any test files you have to your new VS.Net 2005
migrated project). If you right click and exclude them from VS.Net
2005, it renamed the file by appending a ".exclude" file extension;
if you try deleting them from your new VS.Net project, it'll ask you if
you want to delete the file.
What exactly is wrong with keeping files the way they were and just compiling
to .Net 1.1 until you ask your development environment to migrate the project
for you? I guess they just couldn't make VS.Net 2005 backwards compatible
w/ VS.Net 2003 projects. If you want to keep your project compatible
with .Net 1.1, this basically means you're stuck on VS.Net 2003. Talk
about a forced migration path...I won't even talk about how VS.Net 2005
has a 250MB-300MB working set in memory now..oink oink... :-P
Ken's Blog
-