Designers and Developers can live together.
We've been trying to find a solution whereby the totally none-coding designer works with the crayola wielding developers and the simple "Make a static page with some content" people. Dreamweaver templates are excellent for this but VS.NET makes them an impossible solution.
What happens is the template inserts a comment just below the HEAD tag of the simple html page.
<!-- InstanceBegin template="/Templates/test.dwt.aspx" codeOutsideHTMLIsLocked="false" -->
The designer saves the page, it all works and then the developer sets about making it work. As soon as they open the page in design view, the template is screwed because VS.NET moves the instanceBegin comment to after the title tag
<HEAD>
<title>template</title>
<!-- InstanceBegin template="/Templates/test.dwt.aspx" codeOutsideHTMLIsLocked="false" -->
The consequence of this is that Dreamweaver now finds nested editable regions, therefore breaking the functionality of the template 'philosophy'.
http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=457479
http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=441814
http://www.asp.net/Forums/ShowPost.aspx?tabindex=1&PostID=391742
Now, I'm led to believe that Whidbey leaves your code alone and basically, I can’t progress some kind of totally safe shared environment without that functionality. Dreamweaver is an awesome web design tool - especially when coupled with Photoshop and someone who knows how to use it (If you're reading this, then you aren't one of those people :P )
VS.NET will always screw over your code so while Dreamweaver is the tool of choice for frontend stuff, it won’t work with VS.NET (nothing will as VS.NET html mangles everything). However, code development with VS.NET is 10 times quicker than with any other IDE that I know of so whatever solution we use, it has to be VS.NET compatible, not the other way round.
I've looked at BasePages and they seem cool - John Rebbeck and Russ Neimhausers articles are succinct and clear but IMO its not going from A to B when all you want to do is server HTML with some dynamic content. Surely the fastest served page is control light with pure HTML in - not something that is inherited and processed, and then controls moved here and there to make it fit?
So - Whidbey - is it what I'm led to believe it is? I'll let you know.