vs2010... redux [modified]
-
I Believe In GOD wrote:
I know nothing , I know nothing ...
For a guy who says he knows nothing, you sure do talk a lot about this god stuff!
I Believe In GOD wrote:
When someone believe in GOD ,
He really sold the world , because his reward will be the heaven , not this Cruel world !Alright, just kidding you :-D
Regards, Nish
Are you addicted to CP? If so, check this out: The Code Project Forum Analyzer : Find out how much of a life you don't have! My technology blog: voidnish.wordpress.com
-
:)
Regards, Nish
Are you addicted to CP? If so, check this out: The Code Project Forum Analyzer : Find out how much of a life you don't have! My technology blog: voidnish.wordpress.com
-
oh.my.god. vs2010 ... still the biggest pile of crap i've seen since kdevelop v1.0 what's with the window layout? mdi workspace anybody? color schemes? changing the window positions to how *i* want them? this is really the future of development using MS tools?? *shakes head* utterly appalling [edit] current line highlighting anyone? W.T.F. are these people on??? really? every editor i've used since 1995 has current line highlighting ... vs2010 still doesn't???? utterly and absolutely appalling [/edit]
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
modified on Sunday, May 1, 2011 2:11 PM
l a u r e n wrote:
mdi workspace anybody?
I too sorely missed this. However, I found the ability to move a source file to a new vertical tab (thereby allowing me to see two source views side by side - which is pretty much how I used pre-VS2010 MDI) to be an acceptable workaround. I also recommend that you install these (free) extensions. I can't live without them anymore!
/ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Yep - that's one of my biggest complaints as well. I *like* the MDI interface. The reason it's not there is because the IDE is written in WPF, and WPF isn't MDI-friendly. There are other reasons it's a steaming pile as well, but I figured I'd leave the discovery phase in your hands. FWIW, I posted some VS2010 bugs on MSDN Connect, and was told that they weren't going to fix them for VS2010, and that they might not even be fixed for the next version. Thank you for using development tools from Microsoft - where management is an even bigger tool.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997FTFY: Thank you for using development tools from Microsoft - we're Microsoft and you're not.
Best wishes, Hans
-
oh.my.god. vs2010 ... still the biggest pile of crap i've seen since kdevelop v1.0 what's with the window layout? mdi workspace anybody? color schemes? changing the window positions to how *i* want them? this is really the future of development using MS tools?? *shakes head* utterly appalling [edit] current line highlighting anyone? W.T.F. are these people on??? really? every editor i've used since 1995 has current line highlighting ... vs2010 still doesn't???? utterly and absolutely appalling [/edit]
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
modified on Sunday, May 1, 2011 2:11 PM
I have no choice about this with some clients, so I'll just let you know right now: it gets worse the more you use it. Take macros, for example. I have a bunch I've been using for years. In VS2008, I have a nice little toolbar, with a button for each macro. In VS2010, that same toolbar would fill half the screen. Why?, you ask. It's because in VS2010 there's no way to assign an icon to a toolbar command, so you're stuck with a huge long text button. I keep reading blogs of Microsofties, but I haven't yet found one that says: "I was just fired from Microsoft because of the crappy job I did on the VS2010 IDE." I will keep reading until I do.
Best wishes, Hans
-
oh.my.god. vs2010 ... still the biggest pile of crap i've seen since kdevelop v1.0 what's with the window layout? mdi workspace anybody? color schemes? changing the window positions to how *i* want them? this is really the future of development using MS tools?? *shakes head* utterly appalling [edit] current line highlighting anyone? W.T.F. are these people on??? really? every editor i've used since 1995 has current line highlighting ... vs2010 still doesn't???? utterly and absolutely appalling [/edit]
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
modified on Sunday, May 1, 2011 2:11 PM
I can't think of a single good reason to upgrade to VS2010 and will avoid it all costs. All I hear are scare-stories and tales of negative experiences. VS2008 does the job for my C++ work (and I have no interest C++0x at the moment) so hopefully I can carry on like this for a few more years. Thankfully I don't need the latest and greatest MS frameworks and my future is going to be spent doing a lot more Unix and web work so maybe VS2008 will be the last MS development environment I ever use.
-
oh.my.god. vs2010 ... still the biggest pile of crap i've seen since kdevelop v1.0 what's with the window layout? mdi workspace anybody? color schemes? changing the window positions to how *i* want them? this is really the future of development using MS tools?? *shakes head* utterly appalling [edit] current line highlighting anyone? W.T.F. are these people on??? really? every editor i've used since 1995 has current line highlighting ... vs2010 still doesn't???? utterly and absolutely appalling [/edit]
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
modified on Sunday, May 1, 2011 2:11 PM
l a u r e n wrote:
current line highlighting anyone? W.T.F. are these people on??? really? every editor i've used since 1995 has current line highlighting ... vs2010 still doesn't???? utterly and absolutely appalling
You get this with the Power Commands extension (which admittedly should have really been part of the standard install). /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
-
I'm not a masochist: just because it's there, doesn't mean I have to use it! ;)
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
-
oh.my.god. vs2010 ... still the biggest pile of crap i've seen since kdevelop v1.0 what's with the window layout? mdi workspace anybody? color schemes? changing the window positions to how *i* want them? this is really the future of development using MS tools?? *shakes head* utterly appalling [edit] current line highlighting anyone? W.T.F. are these people on??? really? every editor i've used since 1995 has current line highlighting ... vs2010 still doesn't???? utterly and absolutely appalling [/edit]
"mostly watching the human race is like watching dogs watch tv ... they see the pictures move but the meaning escapes them"
modified on Sunday, May 1, 2011 2:11 PM
It's been WPFed (or it that WTFed?). Crap, really. We're sticking with VS2008 until a fully compliant C++ 11 compiler arrives in the shape of VS2012 (or whatever it ends up called) whereupon we'll have to put up with the UI. IIRC current line hightlighting is somewhere in the options. Can't remember where though.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
I have no choice about this with some clients, so I'll just let you know right now: it gets worse the more you use it. Take macros, for example. I have a bunch I've been using for years. In VS2008, I have a nice little toolbar, with a button for each macro. In VS2010, that same toolbar would fill half the screen. Why?, you ask. It's because in VS2010 there's no way to assign an icon to a toolbar command, so you're stuck with a huge long text button. I keep reading blogs of Microsofties, but I haven't yet found one that says: "I was just fired from Microsoft because of the crappy job I did on the VS2010 IDE." I will keep reading until I do.
Best wishes, Hans
The toolbar command button thing is a pain, but I'm pretty sure it was fixed in the RTM. Unfortunately by then we'd ported Visual Lint[^] to a VSX package implementation which uses the lower level interfaces used by language services themselves. However, ResOrg 2.0[^] seems to have no problems with command buttons in VS2010, and given that it uses the automation interfaces macros also use for all versions of Visual Studio it's a pretty safe bet it should work for your macros, at least in the RTM.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
I can't think of a single good reason to upgrade to VS2010 and will avoid it all costs. All I hear are scare-stories and tales of negative experiences. VS2008 does the job for my C++ work (and I have no interest C++0x at the moment) so hopefully I can carry on like this for a few more years. Thankfully I don't need the latest and greatest MS frameworks and my future is going to be spent doing a lot more Unix and web work so maybe VS2008 will be the last MS development environment I ever use.
Marginally OT, but last month we saw a very interesting presentation by Scott Meyers on Move Semantics (move constructors, r-value references etc.) in C++ 11. I'd not paid them much attention until then, but from what I can see they're a win-win feature - they eliminate unnecessary copy operations and thus can boost the speed of your code significantly. The best bit is this is something you can add support for incrementally and the compiler will just figure out when they can be used or when conventional copy assignment/constructors should be called instead. The code just keeps working, but gets faster.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
The toolbar command button thing is a pain, but I'm pretty sure it was fixed in the RTM. Unfortunately by then we'd ported Visual Lint[^] to a VSX package implementation which uses the lower level interfaces used by language services themselves. However, ResOrg 2.0[^] seems to have no problems with command buttons in VS2010, and given that it uses the automation interfaces macros also use for all versions of Visual Studio it's a pretty safe bet it should work for your macros, at least in the RTM.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
Anna-Jayne Metcalfe wrote:
it's a pretty safe bet it should work for your macros
I wish that were so! Unfortunately, it is not. There is no way to add a macro to a toolbar, and then specify an icon for it. When I discovered this, I immediately went to MSDN to find out how to do it, and I saw there many, many people trying to do the same thing. Microsoft support acknowledged this was the case. However, if you believe that this is possible, then please write a Tip on how to do it. I can guarantee you will have the highest-rated Tip of all time. :)
Best wishes, Hans
-
I'm not a masochist: just because it's there, doesn't mean I have to use it! ;)
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
OriginalGriff wrote:
I'm not a masochist developer: just because it's there, doesn't means I have to use it!
No charge for the line edit.
I wanna be a eunuchs developer! Pass me a bread knife!
-
OriginalGriff wrote:
I'm not a masochist developer: just because it's there, doesn't means I have to use it!
No charge for the line edit.
I wanna be a eunuchs developer! Pass me a bread knife!
Good! :laugh: I may be a developer, but I don't press black controls, labelled in black on a black background, in case a little black light lights up black to let me know I've done it.
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Manfred R. Bihy: "Looks as if OP is learning resistant."
-
Anna-Jayne Metcalfe wrote:
it's a pretty safe bet it should work for your macros
I wish that were so! Unfortunately, it is not. There is no way to add a macro to a toolbar, and then specify an icon for it. When I discovered this, I immediately went to MSDN to find out how to do it, and I saw there many, many people trying to do the same thing. Microsoft support acknowledged this was the case. However, if you believe that this is possible, then please write a Tip on how to do it. I can guarantee you will have the highest-rated Tip of all time. :)
Best wishes, Hans
Are you talking manually through the UI, or via the automation interface? The latter is definitely possible so you should be able to write a macro for it.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
I can't think of a single good reason to upgrade to VS2010 and will avoid it all costs. All I hear are scare-stories and tales of negative experiences. VS2008 does the job for my C++ work (and I have no interest C++0x at the moment) so hopefully I can carry on like this for a few more years. Thankfully I don't need the latest and greatest MS frameworks and my future is going to be spent doing a lot more Unix and web work so maybe VS2008 will be the last MS development environment I ever use.
Rob Caldecott wrote:
All I hear are scare-stories and tales of negative experiences.
That is all I heard as well, and I was terrified of the upgrade here. It was totally smooth, but overall - I actually am really impressed with the new IDE.
- It loads faster
- My projects compile and run in about half the time
- The font rendering is excellent. It is so much easier on my eyes
- The ctrl+mousewheel to zoom the text window is useful, and fun
- I get to use .Net 4, which is a win for us
There are downsides, but I just wanted to say it isn't all completely scary and awful. And in response to part of the root post, current line highlighting - who uses that anyway? It's the first thing I turn off in every editor I've used since 1992. My blinking caret is enough.
