No... it won't move "back".  In this incarnation we have the best of both worlds... and to move back would keep us from being able to "move forward" as VS2005 and DNN continue to evolve.

---

Scott Willhite, Co-Founder DNN

A lot of time/effort was invested in delivering a migration strategy for DotNetNuke on ASP.NET 2.0. Based on the recent announcements from Microsoft of the new Web Application Project model ( which is essentially their way of saying that they made a mistake in deprecating it in the first place ), DotNetNuke can now benefit from 2 development methodologies. The new Web Site Project model available in the VS2005 release ( which supports the free Visual Web Developer development tool ) is a RAD methodology for building DNN4 modules which do not need to be packaged/distributed as binaries ( ie. Intranets, vertical market applications, etc... ). The Web Application Project model ( which is currently available as a VS2005 patch from the Microsoft site ) allows DNN module developers to easily upgrade their current module projects ( as long as they have Visual Studio 2005 Standard Edition or higher ) and continue to package/distribute them as binaries ( ie. commercial modules ). Since we support both methodologies and all levels of development tools, DotNetNuke truly does leverage the "best of both worlds" ( as Scott mentions above ). I hope this helps dispel that notion that this is an "either/or" proposition - DotNetNuke supports both ,which allows you to leverage the model which best suits your business needs.

---

My comments are my own and are offered WITHOUT PREJUDICE

Shaun Walker
http://www.siliqon.com