Re: Is Visual Studio .NET ideal for ASP.NET + HTML site?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Glenn Doten (gdoten_at_gmail.com)
Date: 08/04/04 

Date: 4 Aug 2004 07:27:42 -0700

Scott M. wrote:
> I've been hearing these complaints since FrontPage 97. And, I have
to say
> that many (not all) of the complaints come from folks who either
don't know
> how to configure the product to their liking (see my earlier reply in
this
> thread about turning off auto-formatting) or they don't understand
how MS
> intends their products to be used.
>
> MS FrontPage is a wonderful HTML designer/editor with many site
management
> capabilities. VS .NET is more of a hard-core development environment
and
> not so much a site management tool.
>
> You can use FP for low end HTML design if you like as well as site
> management and VS .NET for the programming.
>
> "Mark Rae" <mark@mark-N-O-S-P-A-M-rae.co.uk> wrote in message
> news:uMYuuHaeEHA.712@TK2MSFTNGP09.phx.gbl...
> > "Lucas Tam" <REMOVEnntp@rogers.com> wrote in message
> > news:Xns953A8980C7E36nntprogerscom@140.99.99.130...
> >
> > > I wholeheartedly agree. Dreamweaver kicks VS.NET's *** when it
comes to
> > > HTML editing.
> >
> > Are you listening to this, Microsoft? 'Cos if you're not, you
should be! A
> > whole slew of your users think that part of one of your flagship
> development
> > tools is not as good as the opposition, which is what you hate more
than
> > anything else, right...?
> >
> > And I agree with them, BTW...:-)
> >
> >

Scott, these aren't complaints with FP/VS; they're outright bugs!

Can you honestly say that switching between HTML to design then back to
HTML view has not corrupted your HTML in any of the ways I've already
listeds? These are definitely bugs and have nothing to do with
configuration or understanding some MS design methodology.

FP hasn't know what the term HTML means, even when Vermeer Technologies
owned it. 

--
-glenn-
Quantcast