Re: Where's the NG to complain about VS 2003 IDE?
From: Alvin Bruney [MVP] (vapor)
Date: 02/08/04
- Next message: DalePres: "Re: CryptoStream question"
- Previous message: Jerry III: "Re: why won't JIT inline this?"
- In reply to: Bret Pehrson: "Re: Where's the NG to complain about VS 2003 IDE?"
- Next in thread: Rob Teixeira [MVP]: "Re: Where's the NG to complain about VS 2003 IDE?"
- Reply: Rob Teixeira [MVP]: "Re: Where's the NG to complain about VS 2003 IDE?"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 7 Feb 2004 22:52:06 -0600
I agree the html component of studio needs some work but it isn't as bad as
what you are griping about. Consider that MS is really pushing code-behind
so that is where you should be migrating too.
I think it's the right approach to wean developers out of that classic ASP
inline page junk. The list is too long to warrant any time and effort as to
why it's terrible to program this way with the new model.
I suspect that is the large part of the reason the HTML editor sucks. It
just isn't priority. And rightly so because ASP is past tense. The
code-behind portion is excellent. Occasionally, I do need to muck with the
aspx code but I tend to avoid it as much as possible. Most everything can be
done from the code-behind. Most everything.
-- Regards, Alvin Bruney [ASP.NET MVP] Got tidbits? Get it here... http://tinyurl.com/3he3b "Bret Pehrson" <bret@infowest.com> wrote in message news:4025B8E1.88F19E56@infowest.com... > Nah, I don't mind you asking... > > First, the visual designer is pure junk. Laying out HTML components is next to > impossible. You can't select anything (you click on one thing, and something > else gets selected), you don't have access to a lot of the HTML properties (try > setting up cell gridlines), etc. etc. etc. I usually end up doing my HTML > design in Front Page, then paste it into the VS page. What a mess that is. > Also, it would *REALLY* be nice if when switching from design view to HTML the > selected item was highlighted in the HTML code. > > Another major gripe is the error output -- if you have an undefined type when > compiling, it usually shows up as the *next* type, which is usually defined. > So, you go pulling your hair out trying to figure out why the defined symbol > isn't defined according to the compiler, until you figure out or remember that > it really is the previous symbol that is undefined. I've spent more than a few > hours on that stupid bug. > > Third, the visual designer has a nasty tendency to overwrite your raw code (it > happens all the time in the raw HTML code). (And no, the code isn't in a wizard > section...) > > Blah, blah, blah... > > C# Learner wrote: > > > > Bret Pehrson <bret@infowest.com> wrote: > > > > >Hey, which newsgroup is for complaining about how amazingly crappy the Visual > > >Studio 2003 IDE is? > > > > > >Thanks > > > > If you don't mind me asking, what's so bad about it? I'm curious > > since I've not used it before and, up until now, I've only ever heard > > good comments about it. > > > > Cheers > > -- > Bret Pehrson > mailto:bret@infowest.com > NOSPAM - Include this key in all e-mail correspondence <<38952rglkwdsl>>
- Next message: DalePres: "Re: CryptoStream question"
- Previous message: Jerry III: "Re: why won't JIT inline this?"
- In reply to: Bret Pehrson: "Re: Where's the NG to complain about VS 2003 IDE?"
- Next in thread: Rob Teixeira [MVP]: "Re: Where's the NG to complain about VS 2003 IDE?"
- Reply: Rob Teixeira [MVP]: "Re: Where's the NG to complain about VS 2003 IDE?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|