I am in the process of porting my EZWeb application framework to ASP.NET 2.0.  Of course, this process will be similar to many projects that are currently in VS.NET 2003 format.  VS.NET 2005 will automatically convert the project.  I accepted the default option, and VS pulled all my code files into the newly-created “Code” folder, but my (converted) code-beside files were left with the corresponding ascx files.  I tried to run the application, and I ran into a roadblock.  It wouldn’t build because my .cs files that didn’t make it to the code directory were ignored.  Obviously I don’t want my code-beside files to be physically separated from the ascx files, so I think that the Code directory model is only useful for non-enterprise projects where you might want to deploy the source with the application and put all code in <script runat=server/> blocks in the ascx files.  Small hobbyist projects will probably benefit from this model because the deployed code-base and be modified directly without going through a lengthy develop-test-deploy cycle.  Academia will also probably use this model.  Especially with the free Visual Web Dev, intellisense in the HTML view will enable students to write Page_Load code, and they can even write classes and put them in the Code directory.  In my opinion, this change makes ASP.NET 2.0 viable for college classes.

But this still leaves me to explore another model for my enterprise-level web project.  I’m also a little annoyed that my favorite shortcut Ctrl+Shift+B (Build) was removed, and I’ll have to remap it.