dreamweaver mx 2004 or VS.NET for ASP.NET??

[RedDevil]

Hi guys!!

I want to ask for your opinion on dreamweaver mx 2004 and VS.NET for ASP.NET. Which is better? I'm learning both at the same time and i find that there are pros and cons for both the SW. I will describe the pros and cons below:

DWMX 2004 PROS:
1) Learn HTML more effectively
2) new functions that make things easier
3) Very powerful
4) ASP, ASP.NET, JSP, HTML usable
5) (cant thing of anything yet)

DWMX 2004 CONS:
1) creating a template is like HELL!!
2) very hard to learn if you are new to DWMX 2004
3) generate useless codes in the HTML
3) (cant thing of anything yet)

VS.NET PROS:
1) if you know VB.NET, doing ASP.NET is like doing in VB.NET!!
:bigyello:
2) don't need to build any template because you can design any where in the page!!
3) new learner can learn very fast
4) (cant thing of anything yet)

VS.NET CONS:
1) TOO EASY!! what is the point of doing ASP.NET is VB.NET style??
2) Not much knowledge of HTML is needed to do it
3) It doesn't support classic ASP(am i right? Correct me if im wrong)
4) (cant thing of anything yet)

That is all i can think off. Please state your opinion here. Thanks!!

Cheers!!

[<ABX]

First of all....

VS.Net was never intended to support ASP.


VS.NET CONS:
1) TOO EASY!! what is the point of doing ASP.NET is VB.NET style??
2) Not much knowledge of HTML is needed to do it


1: THAT IS THE MAJOR BENIFIT OF USING ASP.NET! If you have learnt VB.Net or C# for Desktop Development it doesnt take much more to learn how to create dynamic websites. ASP.NET was never intended to be a language, its just a framework for website development. EASY IS GOOD (when you still maintain control)!

2: How is this bad?

FYI: You can design anywhere in the page w/ dreamweaver too. (an with any text editor).

----------------------------------------------------------------------------------

I prefer Dreamweavers html/xhtml editor for designing (i dont use the designers at all). Then i copy the html over to VS.net and do all the coding there.

and Personally i would prefer template support in VS.net.

[mendhak]

Simple answer:

VS.NET :wave:

[venerable bede]

When I first started .net I made the mistake of using Dreamweaver MX.

DONT!!!

Dreamweaver doesn't support code behind pages (I have read that you can work around this but why?)

If you use behaviours (Wizards) you will find that Dreamweaver generates some of the most convoluted crap code imaginable.

You cannot compile you're code so its slower.

There is no Intellisence and considering there are more methods and properties in .net then hairs on Bodwads back this is a pain.

On saying all of that I still use Dreamweaver for my HTML stuff but nothing else.

Dreamweaver is for webchicks (Graphic Designers) who as we all know smell, are untrustwothy, drink like girls and have bad breath.