Dreamweaver MX and Visual Studio

  • Thread starter Thread starter Amy Snyder
  • Start date Start date
A

Amy Snyder

I use both development tools when creating my apps. Dreamweaver is so
much easier to work with when it comes to designing the interface where
as VS makes it easier to write the code-behind.

Is there such a thing in Dreamweaver - code behind that is? It seems it
is very difficult to try and work with both now. Does anyone use both
of these tools? If so, how do you integrate?
 
i use both, but it's a pain in the arse.

I find I have to create the ASPX pages in dreamweaver, then "include" them
in VS...this updates the @Page directive for codebehind, etc.
Avoid using <%...%> as VS Will not display the WYSIWYG editor, I also have
the problem of using Dreamweaver MX (not 2004) which means my ASP textboxes
and other controls are all a default size, and the MX editor doesn't
recognise server side attribs on the control (unlike VS)
So.. you still have to do resizing of server-side controls in the VS editor.

i know that doesn't help. but you asked

sam
 
I use FrontPage, but the principle is the same. In any case, I use FrontPage
to design my HTML, and then paste it into my Pages and User Controls in
Visual Studio. A web development toolkit is best used for developing HTML
and other client-side stuff. Visual Studio is the best tool for doing the
programming.

--
IMHO,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
I do the same as you, and agree that it's a pain. Beyond what the others
said, I'll add that before editing anything in VS, I first open all project
..aspx pages in Dreamweaver. That way, if VS decides rewrite my HTML, I can
simply switch back to Dreamweaver and resave the document - thereby
preserving my original HTML. This scenario rarely occurs because tend I
follow my own rule of never opening an aspx page in VS, and instead using VS
only to do the code-behind work; all layout and site management tasks are
done in Dreamweaver.

HTH

Jeff
 
Hey MS are you listening. This thread is about the multi thousanth thread
about the abysmal HTML editor in Visual Studio.

Please fix it so that your customers (yes that is right the people who pay
to use these products) can do their development without having to fight the
tool that they are using to develop them.

Lloyd Sheen
 
Agreed - and one new feature that would save us a lot of pain would be for
us to easily disable VS from rewriting HTML. It's frustrating to spend hours
creating uncluttered page layout in HTML(using any tool other than VS), and
then open the same page in VS and change one simple property value of one
control that appears on the page -- and then have VS COMPLETELY REARRANGE
the layout. It's not that VS simply reproduces the same layout you started
with but with its own HTML version - you actually get a page that looks
NOTHING LIKE the original page. When this happens once or twice you learn
quickly to keep a clean version of the page opened in some other tool
outside of VS.NET so you can resave it there to keep your pristine HTML and
layout intact. Just give us a checkbox in the VS Options labeled something
like "don't screw up my HTML" and have it checked by default....
 
Hey Lloyd, are you keeping up? Microsoft is aware of this issue, has been
for quite some time, and has promised much better in the next release.

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
Thanks for the replies everybody. I do seem to have to create the new
aspx file using VS so as to get the right syntax on the page for the
code behind. Then I will go to DW to design. Is that what you do to?

I agree Microsoft has got to do something about the HTML editing part.
VS has been poor in this department ever since 1.0.
 
Back
Top