It's the little things

  • Thread starter Thread starter CMM
  • Start date Start date
C

CMM

Do the developers of Visual 2005 actuall use it??? There's lots of great
things in VS2005 (mostly related to the outstanding work done on the CLR)...
but in general the LITTLE THINGS totally drag it down.. especially the
slightly-improved-but-not-all-that-much IDE. I waited for 3 years for this?
Who's in charge of this mess?

1)
Editing a web form in the designer... I think I'm totally misunderstanding
the usage of CSS stylesheets and classes. Why can't I pick from a CSS style
in the CssClass property in the property window? I can manually enter a
style and it'll work... but there's no "dropdown" to select one. I have to
remember the names of all the styles in my stylesheet? That's not very
helpful. Am I doing something wrong?

2)
Also, CSS styles in the linked stylesheet also don't show up in the "Block
Format" dropdown in the toolbar. I think they should... am I wrong?
Furthermore, why can't I link (via the Property Editor) to multiple
stylesheets. HTML supports this and it is used often... why doesn't the
designer support this? I know I can drop to the source editor and add them
to the HEAD section manually but this is also not very helpful in the grand
scheme of things. No wonder Visual Studio 2005 defaults to showing you the
source HTML/ASP tags.... because it's visual web form editor plain sucks.

3)
Why doesn't the ClassKey property in the Expressions window show resource
files that are in App_GlobalResources??? You have to manually type in the
name of the resource file. Not only that, but even if you type in the name
of the resource file, you still have to manually give it the the name of the
resourse string!!!???? Why no dropdown? Not only that, but if you go back
into it, then a list of resource keys DO show up? Amazing! This is a flat
out bug... not a missing feature or a misunderstanding of the developer's
intent. Whatever programmer was in charge of this feature simply went to
sleep on it.

I understand that it works better if you have a resource file for EACH web
form... because then the Expressions Editor doesn't act so STUPID. But, this
is unnacceptable. The implementation of Globalization via Resource files in
the ASP Web Forms designer is HORRID.

4)
Is it me or does intellisense behave weird in the Immediate Window? When I'm
in debug mode and I go to the Immediate window and type ? System. no
intellisense after the period! But if I hit enter after typeing ? system (I
get an error of course) but then after that typing ? System. does trigger
intellisense and I'm shown all the stuff in the System namespace. Huh?

5)
F1 is unpredictable. It doesn't work from the immediate window It doesn't
really work from the Property Editor. It works OK from source code... but
then it gets confused if you have nested parethesis and such. It took me
forever to realize that I should NOT select an entire word and hit F1...
that this instead does a "generic" search instead of the actual TYPE of the
variable or keyword selected. Not highligting the word does cause F1 to
behave as you would expect and it zeroes in exactly on the keyword or
function it should in the Help files. I don't dislike this behavior... but,
I was confused by it at first.

6)
Don't even get me started on why VS2005 INSISTS on creating an EMPTY UNUSED
subfolder every time it starts in my My Documents folder even though I have
changed all its paths elsewhere.

7)
Import/Export settings is a cool idea (actually stolen from good ol' Visual
Interdev about 7 years late). But badly implemented. I would prefer to see a
drop down or menu somewhere where I can easily change "Environment Settings"
without worrying about saving, switching around physical files, or playing
musical chairs. Something like View | Environment -> C#, VB, Custom, Define
Views (similar to the way Outlook does "Views.")
 
I suggest you protest this incompetence by only using the command line tools
until VS 2007 is released. That'll show 'em.

:)

tm
 
CMM said:
Do the developers of Visual 2005 actuall use it??? There's lots of great
things in VS2005 (mostly related to the outstanding work done on the CLR)...
but in general the LITTLE THINGS totally drag it down.. especially the
slightly-improved-but-not-all-that-much IDE. I waited for 3 years for this?
Who's in charge of this mess?

Takes all kinds. I love VS.2005 - especially the menus that offer to
write stubs to implement interfaces implicitly (public methods) or
explicitly, the menus that offer to qualify names or add a using
statement, the menus that can generate the prototype for a method that
you've used before defining it. The autoformatter is improved, too, as
is toolwindow dragging. Intellisense seems cleverer, too.
 
I love VS.NET in general... and 2005 is not ALL bad...VS.NET was pretty
awesome to begin with. But is 2005 really worth all the hype after THREE
years. I expected it to be a lot more mature than it was... and I DEFINATELY
didn't expect to see some of the quirks and out and out bugs present in it.
I expected more after three years and from a dev team as large as this.
 
Nah... 2005 ain't all that bad. ;-) (but neither was 2003)
I just hope we don't have to wait a long 2 years for v2.1. I've really begun
to hate MS's development cycles and marketing driven hype releases.
 
CMM said:
1)
Editing a web form in the designer... I think I'm totally misunderstanding
the usage of CSS stylesheets and classes. Why can't I pick from a CSS style
in the CssClass property in the property window? I can manually enter a
style and it'll work... but there's no "dropdown" to select one. I have to
remember the names of all the styles in my stylesheet? That's not very
helpful. Am I doing something wrong?

It's not exactly easy for VS to know what CSS classes you have, it would
have to spider the current page (and all of it's includes, the master
page, etc - more could even be added programmatically/at runtime...),
then it would have to make a list of all the classes from these files.
From that you'd have a list with hundreds of classes in a tiny drop
down... Not useful one bit. Or perhaps it would have to do filtering on
the entities to see what could apply to whatever you're styling (that
would be complicated, not so reliable, and would make the IDE super
slow, yet still list hundreds of classes in a tiny dropdown).
2)
Also, CSS styles in the linked stylesheet also don't show up in the "Block
Format" dropdown in the toolbar. I think they should... am I wrong?
Furthermore, why can't I link (via the Property Editor) to multiple
stylesheets. HTML supports this and it is used often... why doesn't the
designer support this? I know I can drop to the source editor and add them
to the HEAD section manually but this is also not very helpful in the grand
scheme of things. No wonder Visual Studio 2005 defaults to showing you the
source HTML/ASP tags.... because it's visual web form editor plain sucks.

I don't know really... I always work in source mode no matter what IDE I
use. Can't stand any of those visual drag n drop things (they're not
very productive usually either - I see some webmasters spend like 5
3)
Why doesn't the ClassKey property in the Expressions window show resource
files that are in App_GlobalResources??? You have to manually type in the
name of the resource file. Not only that, but even if you type in the name
of the resource file, you still have to manually give it the the name of the
resourse string!!!???? Why no dropdown? Not only that, but if you go back
into it, then a list of resource keys DO show up? Amazing! This is a flat
out bug... not a missing feature or a misunderstanding of the developer's
intent. Whatever programmer was in charge of this feature simply went to
sleep on it.

I understand that it works better if you have a resource file for EACH web
form... because then the Expressions Editor doesn't act so STUPID. But, this
is unnacceptable. The implementation of Globalization via Resource files in
the ASP Web Forms designer is HORRID.

I haven't really had any issues loading resources. Honestly, I'm quite
pleased with the localization features (some things are still a pain to
localize, like javascripts, but markup wise it's easy and works well).
4)
Is it me or does intellisense behave weird in the Immediate Window? When I'm
in debug mode and I go to the Immediate window and type ? System. no
intellisense after the period! But if I hit enter after typeing ? system (I
get an error of course) but then after that typing ? System. does trigger
intellisense and I'm shown all the stuff in the System namespace. Huh?

Intellisense sometimes crashes on me, I'll grant you that :)
5)
F1 is unpredictable. It doesn't work from the immediate window It doesn't
really work from the Property Editor. It works OK from source code... but
then it gets confused if you have nested parethesis and such. It took me
forever to realize that I should NOT select an entire word and hit F1...
that this instead does a "generic" search instead of the actual TYPE of the
variable or keyword selected. Not highligting the word does cause F1 to
behave as you would expect and it zeroes in exactly on the keyword or
function it should in the Help files. I don't dislike this behavior... but,
I was confused by it at first.

I'm not a very big F1 user, can't really say much here...
6)
Don't even get me started on why VS2005 INSISTS on creating an EMPTY UNUSED
subfolder every time it starts in my My Documents folder even though I have
changed all its paths elsewhere.

Hard to say. What's the name?
7)
Import/Export settings is a cool idea (actually stolen from good ol' Visual
Interdev about 7 years late). But badly implemented. I would prefer to see a
drop down or menu somewhere where I can easily change "Environment Settings"
without worrying about saving, switching around physical files, or playing
musical chairs. Something like View | Environment -> C#, VB, Custom, Define
Views (similar to the way Outlook does "Views.")

I have no complaints here but I see your point.
 
john smith said:
It's not exactly easy for VS to know what CSS classes you have, it would
have to spider the current page (and all of it's includes, the master
page, etc - more could even be added programmatically/at runtime...), then
it would have to make a list of all the classes from these files. From
that you'd have a list with hundreds of classes in a tiny drop down... Not
useful one bit. Or perhaps it would have to do filtering on the entities
to see what could apply to whatever you're styling (that would be
complicated, not so reliable, and would make the IDE super slow, yet still
list hundreds of classes in a tiny dropdown).

Come on... it does a pretty good job of parsing a gazzillion <ASP:Control>
elements at design time to render the designer.... but, I guess I see what
you mean... however it's a lot simpler than you describe. Say I have a
linked stylesheet... added the way the MS Gods want you to do it (via the
"Stylesheet" property of the page). I select a label and go to the CssClass
property in the Property Editor.... why is it a dumb text box?

And by the way... not that I'm an avid user of it.... but FrontPage parses
stylesheets at design time JUST FINE. So it's not impossible. In fact, it
should be a no-brainer.
I don't know really... I always work in source mode no matter what IDE I
use. Can't stand any of those visual drag n drop things (they're not very
productive usually either - I see some webmasters spend like 5 seconds
going thru tool palettes to add a <br /> tag...), I type whatever I want
in.


I haven't really had any issues loading resources. Honestly, I'm quite
pleased with the localization features (some things are still a pain to
localize, like javascripts, but markup wise it's easy and works well).

OK.


Intellisense sometimes crashes on me, I'll grant you that :)

OK.


I'm not a very big F1 user, can't really say much here...

Well, I use it all the time... because I guess that after 10 years, well,
I'm still dumb.
Hard to say. What's the name?

Um, "Visual Studio 2005"

..... and it's empty because I've changed all paths to a different dir
(including via the registry). I delete it... and it comes back (empty again)
when I start VS. I have resorted to marking it +h +s to make it a hidden
system file so I don't have to look at it.
I have no complaints here but I see your point.

I have no complaints either. I just don't use it.
It's a very cumbersome feature that might have been useful if implemented
with brains.
 
CMM said:
Do the developers of Visual 2005 actuall use it??? There's lots of great
things in VS2005 (mostly related to the outstanding work done on the
CLR)... but in general the LITTLE THINGS totally drag it down.. especially
the slightly-improved-but-not-all-that-much IDE. I waited for 3 years for
this? Who's in charge of this mess?

=> <URL:http://lab.msdn.microsoft.com/productfeedback/>
 
Do the developers of Visual 2005 actuall use it??? There's lots of great
things in VS2005 (mostly related to the outstanding work done on the
CLR)... but in general the LITTLE THINGS totally drag it down.. especially
the slightly-improved-but-not-all-that-much IDE. I waited for 3 years for
this? Who's in charge of this mess?

It's important to differentiate between using VS.Net 2005 for ASP.Net
development, and for every other type of development. From what I've heard,
it's buggy when it comes to ASP.Net development, but the ASP.Net object
model has been changed quite a bit from the 1.1 platform. I'm not saying
this is an excuse, but a contributing factor.

However, I've developed all kinds of non-ASP.Net apps with it, and it's a
tremendous improvement over 2003. There are changes to the CLR, but these
pale in comparison to the changes in the IDE. There have been quite a few
actually, but don't let the fact that it looks almost the same throw you
off. There has been a heck of a lot of enhancement to the IDE. I use
Refactoring on a regular basis. It's one of the best things about it. The
intellisense is *much* better. For example, you can go to a locally-defined
variable (inside a method) now. Code Snippets are highly useful. The XML
tools are amazing. And that's just off the top of my head. There is quite a
bit more in there as well. A great productivity tool.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Who is Mighty Abbott?
A twin turret scalawag.
 
Just to answer the one question that few others attempted...

CMM said:
Do the developers of Visual 2005 actuall use it???

Yes. Every iteration... Even the really raw unfinished versions.

They lived every bug. They worked with the tool to build the tool. It is
part of the Microsoft philosophy: be your own first and most-demanding
customer. Long before it was released, other groups were using this tool to
build other apps and products.

Even the Microsoft internal IT groups used the beta versions, and provided
feedback, in order to improve the tool before it was released.


--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik

Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
 
Glad to hear it. And all the "new" features in VS2005 are very good and very
welcomed. I just don't think it was worth 3 years and the hype (well, the
clr and language features were worth it!... but not much else). I expected a
release as mature and slick as VS2003... not unpolished and incomplete as
2005 seems to be.
 
Nick said:
Just to answer the one question that few others attempted...



Yes. Every iteration... Even the really raw unfinished versions.

They lived every bug. They worked with the tool to build the tool.
It is part of the Microsoft philosophy: be your own first and
most-demanding customer. Long before it was released, other groups
were using this tool to build other apps and products.

Even the Microsoft internal IT groups used the beta versions, and
provided feedback, in order to improve the tool before it was
released.

While I know MS employees 'dogfood' their own products, I can't
understand why these same MS employees accept silly things, like really
tiny windows you can't resize and in which you have to scroll a lot.

Or the silly new search/replace dialog which lacks a close button and
has an action button on the spot where you would expect a close button.
Every time I have to stop myself clicking that darn button. Very
annoying, and because it's annoying, I then wonder: am I the only
person who thinks that's annoying, and if not, why didn't any MS
employee shoot an email to the dev group asking for an explanation why
it's not setup properly?

FB

--
 
Frans,

I have once asked this in a chat to Microsoft.Especially about the Project
Reference box which was in my opinion terrible to use.

It will not be the reason that I have asked it, however most dialogwindows
in version 2005 that I have seen are now resizable (including that search
box). However they lack a grip in the window and therefore I did think a
well a while that they where not resizable.

I agree with you that it is still annoying that Microsoft uses non Microsoft
standards for the control box on a dialogbox.

Cor
 
Or the silly new search/replace dialog which lacks a close button and
has an action button on the spot where you would expect a close button.
Every time I have to stop myself clicking that darn button. Very
annoying, and because it's annoying, I then wonder: am I the only
person who thinks that's annoying, and if not, why didn't any MS
employee shoot an email to the dev group asking for an explanation why
it's not setup properly?

The new search and replace does have a close button. It's the little "x" in
the upper right-hand corner. It can also be closed by hitting the ESCAPE
key. And it can be configured to close as soon as it finds the first match.
After that, you can continue finding matches by hitting the F3 Key.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
Who is Mighty Abbott?
A twin turret scalawag.
 
Back
Top