Help converting VS2005 to Dreamweaver

Tell them not to be silly, if you have VS.NET 2005 its just plain stupid to
switch to DW for ASP.NET applications, DW is handy for tweaking the layout
and tags but it's completely hopeless for editing .NET code when compared
against MS tools, even the free ones.

--
Kevin Marshall
WebXeL.com Ltd
http://www.webxel.com

ASP.NET Dreamweaver Extensions
http://www.webxel-dw.co.uk

"weatherworman" <webforumsuser@macromedia.com> wrote in message
news:eq09qc$ebf$1@forums.macromedia.com...
> My client's IT dept recently chose to switch to DW for web development. I
> am
> mid-stream in a development project for one of their branches using Visual
> Studio 2005. Does anyone have experience converting from 1 to the other?
>
> I am specifically concerned about the portability of some .net components
> (ALGRID) and if .dwt files can handle a ContentPlaceholder control.
>
> Any information would be very much appreciated.
>
>
>

Just from some of the people I have worked withs experiences ...

1. VS is much better for .net stuff, DW is better at the front end stuff ...
2. DW is quite a good code editor, but your almost better off leaving the
development in VS and where possible using (brains funny this morning)
external code.

Sorry if this isn't the best response - DW is only really good at coding its
own code, and not always great at that!

Gerry


http://www.Usablehost.co.uk



"weatherworman" <webforumsuser@macromedia.com> wrote in message
news:eq09qc$ebf$1@forums.macromedia.com...
> My client's IT dept recently chose to switch to DW for web development. I
> am
> mid-stream in a development project for one of their branches using Visual
> Studio 2005. Does anyone have experience converting from 1 to the other?
>
> I am specifically concerned about the portability of some .net components
> (ALGRID) and if .dwt files can handle a ContentPlaceholder control.
>
> Any information would be very much appreciated.
>
>
>