Re: Asp.net 2.0 and Dreamweaver
- From: "tshad" <tfs@xxxxxxxxxxxxxx>
- Date: Thu, 16 Feb 2006 22:30:56 -0800
"Darren Kopp" <darrenkopp@xxxxxxxxx> wrote in message
news:1140148789.438297.100960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Are you talking about the code as inline code rather than code in a
code behind? I use VS.Net 2003 with dreamweaver (dreamweaver for
design stuff), but I will always jump back to VS for adding controls to
the page and such (since it creates the stuff i need automatically in
the code behind).
Just go to a aspx file in the solution explorer, right click, open
with, then add the dreamweaver executable to the list (you can make it
default, but messes with code behind or resx, something).
If you could clarify what you mean by "DW code inside" that would help.
When I talk about code-inside, I am talking about one page for both code and
design as opposed to code behind. This is also the direction MS is taking
in VS 2005. You now have 3 models, apparently.
In VS2003, you had to use Code behind, so that if you used a single page, it
wouldn't work in VS 2003.
I have a site with all my pages single .aspx pages. There are no .aspx.vb
(or aspx.cs).
Thanks,
Tom
Regards,
Darren Kopp
http://blog.secudocs.com/
.
- Follow-Ups:
- Re: Asp.net 2.0 and Dreamweaver
- From: Darren Kopp
- Re: Asp.net 2.0 and Dreamweaver
- References:
- Asp.net 2.0 and Dreamweaver
- From: tshad
- Re: Asp.net 2.0 and Dreamweaver
- From: Darren Kopp
- Asp.net 2.0 and Dreamweaver
- Prev by Date: How do I?
- Next by Date: "Page Cannot be Displayed" problem with aspx on IIS6
- Previous by thread: Re: Asp.net 2.0 and Dreamweaver
- Next by thread: Re: Asp.net 2.0 and Dreamweaver
- Index(es):
Relevant Pages
|