In our previous episode we dug into the mystery of the single \app_code page stub when none was created for any of the other four sample project wizards. Here we'll close out the series with a few other words from ScottGu's email describing his experience migrating my ASP.NET 1.1 app to ASP.NET 2.0. As a reminder, the complete ScottGu email is posted in HTML format here.
Before we go to the GuMeister, here's a screenshot of the app in VS2003 and the same app in VS2005 as proof of a successful migration.
Scott writes.
What remains to look at now is whether there is a better way to structure the inheritance hierarchy of the classes in your app_code\migrated directory (which is where all stub-classes are stored). In looking at the classes, it appears that you have several common methods on each of the individual stubs – my recommendation would be to consider encapsulating these in 1-3 common base classes or interfaces that you use as a clean contract that your base classes worked with (this should also scale better as you start to add more wiz controls).
Excellent advice.
Here is Scott's closing paragraph. I'll let you draw your own conclusions as to what he might be telling us.
One of the other things we are looking to talk about very shortly (sometime later this month) is a way for VS 2005 to also support projects that are built more like the VS 2003 web projects (1 single .dll for everything) than the new web-site model (where we compile into multiple dlls). We think the new web-site model brings a lot of new benefits (and so we will still be pointing people towards that as the default way to build new apps), but we also want to make sure we can enable easy migration without requiring code-changes. The good news is that I was able to try out the project you sent me with the new project template, and was able to get it converted over in about 90 seconds – with no code changes required (all of your existing code and directory structure stayed the same – the migration wizard doesn’t refactor your code at all). I’ll send you a pointer to this as we start talking about it soon. This might be an alternative approach for you to take if you want to quickly migrate your app forward to ASP.NET V2.0 without requiring you to spend anytime on migration.
The only thing left to say is that it's been a Great ScottGu Day!
Oh, and one other thing. THANK YOU, SCOTT GUTHRIE!