Software management consultant and CTO, Headspring Systems
I'm going to post my experiences with VS 2005 Beta 2 so you can hopefully save some time when you migrate. My company has converted completely and has deprecated v1.1. My group is a large web project with several class libraries. I'm excited and disappointed with the new web projects. I've been working for 2 weeks now with the new web project, and I like most of what they've done. The following are the things I don't like:
- No more pre or post build events
- No project references (just .dll files copied to the bin directory)
- partial classes hide code I'm interested in and hides things from me.
I'm almost to the point where I'm going to use a class library project to develop my ASP.NET 2.0 web projects as well. I will sacrifice some designer support, but I don't depend on that anyway. If you are using class library projects in v1.1, don't run your project through the converter. Just open the project in VS 2005 and keep it as a class library. It will be a seemless upgrade with few problems.
When I start new web projects from scratch, I'll be using class libraries. The new web site layout will be good for hobbyists developing with VWD, but it has too many limitations for me. I really like a lot of what they've done, but a few things just ruin a good thing.
About Jeffrey Palermo
Jeffrey Palermo is a software management consultant and the CTO of Headspring Systems in Austin, TX. Jeffrey specializes in Agile coaching and helps companies double the productivity of software teams. Jeffrey is an MCSD.Net , Microsoft MVP, Certified Scrummaster, Austin .Net User Group leader, AgileAustin board member, INETA speaker, INETA Membership Mentor, Christian, husband, father, motorcyclist, Eagle Scout, U.S. Army Veteran, and Texas A&M University graduate.
