VS2010 is now uninstalled.
-
It was a moment of regrettable naivete that led me to install this POS to begin with. The joke documentation system updates have been the last straw. This POS is coming off my machine and will not be re-installed. If I need to do any native development that can't be done with VS2008, it'll be done with NetBeans. VS2010 is an unusable pile of steaming shit. And it's the last product I'll acquire via an MSDN license - that won't be renewed again, either. If this is the pinnacle of MS dev tools, I won't miss them.
L u n a t i c F r i n g e
-
It was a moment of regrettable naivete that led me to install this POS to begin with. The joke documentation system updates have been the last straw. This POS is coming off my machine and will not be re-installed. If I need to do any native development that can't be done with VS2008, it'll be done with NetBeans. VS2010 is an unusable pile of steaming shit. And it's the last product I'll acquire via an MSDN license - that won't be renewed again, either. If this is the pinnacle of MS dev tools, I won't miss them.
L u n a t i c F r i n g e
Strange, I had the trial version for a couple of months and found it really good, even on my old P4 system with 2Gb memory. The only reason I did not buy it was purely down to cost - I only write code for my own entertainment these days. I still use VC++ 2010 Express and VCS 2010 Express, and am more than happy with both of them. You don't actually say what problems it has caused you, apart from stating your opinion that it's a POS; maybe you'd care to elaborate.
Just say 'NO' to evaluated arguments for diadic functions! Ash
-
Strange, I had the trial version for a couple of months and found it really good, even on my old P4 system with 2Gb memory. The only reason I did not buy it was purely down to cost - I only write code for my own entertainment these days. I still use VC++ 2010 Express and VCS 2010 Express, and am more than happy with both of them. You don't actually say what problems it has caused you, apart from stating your opinion that it's a POS; maybe you'd care to elaborate.
Just say 'NO' to evaluated arguments for diadic functions! Ash
I've posted a couple of times about the customization problems - productivity tricks that had been around since VS6 disappeared because it was more important that the product be used as a showcase of WPF than it be a useful tool for end users. And I've written a couple of times about the documentation system problems that render the help system unuseable. As Roger mentioned the last time I brought it up, I'd be better off using Google anyway. I did switch to Rob Chandler's help viewer, which kicks the snot out of the MS version. But even with that viewer, you're dependant on the MS doc system to update the help files, and that is a complete fail. The fact that it doesn't work, combined with the fact that every failed attempt to update docs costs me several GB of network bandwidth, makes it as worthless as a steaming pile of shit. There. Enough detail? ;) [edit] And this is just so typical - now that VS2010 is no longer installed, I can update the help. I couldn't while VS2010 was installed. So I guess that's the drill, then - when new help updates are released, I uninstall VS2010, perform the update, then re-install. Or not. Much more likely. [/edit]
L u n a t i c F r i n g e
modified on Friday, September 24, 2010 8:36 AM
-
I've posted a couple of times about the customization problems - productivity tricks that had been around since VS6 disappeared because it was more important that the product be used as a showcase of WPF than it be a useful tool for end users. And I've written a couple of times about the documentation system problems that render the help system unuseable. As Roger mentioned the last time I brought it up, I'd be better off using Google anyway. I did switch to Rob Chandler's help viewer, which kicks the snot out of the MS version. But even with that viewer, you're dependant on the MS doc system to update the help files, and that is a complete fail. The fact that it doesn't work, combined with the fact that every failed attempt to update docs costs me several GB of network bandwidth, makes it as worthless as a steaming pile of shit. There. Enough detail? ;) [edit] And this is just so typical - now that VS2010 is no longer installed, I can update the help. I couldn't while VS2010 was installed. So I guess that's the drill, then - when new help updates are released, I uninstall VS2010, perform the update, then re-install. Or not. Much more likely. [/edit]
L u n a t i c F r i n g e
modified on Friday, September 24, 2010 8:36 AM
Haven't you learnt by now that Help gets worse with each new version of VS?:) I just use Google anyway. For F1 Help I've used that VS 2005 Search Macro hooked up to Google for many years - faster and more accurate than VS's own F1. I assume it should still work with VS 2010 but I don't have full VS 2010 to test.
-
Haven't you learnt by now that Help gets worse with each new version of VS?:) I just use Google anyway. For F1 Help I've used that VS 2005 Search Macro hooked up to Google for many years - faster and more accurate than VS's own F1. I assume it should still work with VS 2010 but I don't have full VS 2010 to test.
Kevin McFarlane wrote:
Haven't you learnt by now that Help gets worse with each new version of VS?
Yeah, yeah... I know, I know... ;)
Kevin McFarlane wrote:
For F1 Help I've used that VS 2005 Search Macro hooked up to Google for many years
I have that set up too, but therein lies (at least part of) the rub - one of the UI shortcomings that drove me over the edge was the fact that you could no longer hook a macro up to a bitmap toolbar button. Macros could only be hooked up to buttons with text labels that held the complete name of the macro. You couldn't modify that behavior. There HAS been an add-in released after the fact that tries to correct this shortcoming, but it's buggy to the point that it's not worth using. There WAS this blog entry that seems to have disappeared at MS, written by the author of said add-in. This blog entry described how the ability to customize macro-connected toolbar buttons came to be left out. Two factors were in play. The first was the time pressure resulting from the decision to trash their UI and re-implement it in WPF. The second factor, IIRC, was that the individual responsible for developing customization code had graduated from college two years previously, and had a total of two years experience w/ VS. He openly stated that he didn't think this capability was a priority because he'd never used it. In his two years of experience. Strangely, this blog entry seems to have disappeared.
L u n a t i c F r i n g e
-
Kevin McFarlane wrote:
Haven't you learnt by now that Help gets worse with each new version of VS?
Yeah, yeah... I know, I know... ;)
Kevin McFarlane wrote:
For F1 Help I've used that VS 2005 Search Macro hooked up to Google for many years
I have that set up too, but therein lies (at least part of) the rub - one of the UI shortcomings that drove me over the edge was the fact that you could no longer hook a macro up to a bitmap toolbar button. Macros could only be hooked up to buttons with text labels that held the complete name of the macro. You couldn't modify that behavior. There HAS been an add-in released after the fact that tries to correct this shortcoming, but it's buggy to the point that it's not worth using. There WAS this blog entry that seems to have disappeared at MS, written by the author of said add-in. This blog entry described how the ability to customize macro-connected toolbar buttons came to be left out. Two factors were in play. The first was the time pressure resulting from the decision to trash their UI and re-implement it in WPF. The second factor, IIRC, was that the individual responsible for developing customization code had graduated from college two years previously, and had a total of two years experience w/ VS. He openly stated that he didn't think this capability was a priority because he'd never used it. In his two years of experience. Strangely, this blog entry seems to have disappeared.
L u n a t i c F r i n g e
I hate it went software vendors remove functionality. MS aren't the only ones to do this. They seem to think that if a feature is only used by a minority they can get rid of it! I was annoyed when in VS 2005 they removed the toolbar buttons for match case and match whole word and also made them non-keyboard shortcut enabled too, so you always had to open the dialog box to select the option. Fortunately someone provided an add-in hat restored the buttons. But they've never been put back into the main product. I do feel that each new VS is on the whole better than the previous (may be different for C++ devs) but they do also tend to add some usability regressions. Customising the toolbars is now more awkward for example.
-
It was a moment of regrettable naivete that led me to install this POS to begin with. The joke documentation system updates have been the last straw. This POS is coming off my machine and will not be re-installed. If I need to do any native development that can't be done with VS2008, it'll be done with NetBeans. VS2010 is an unusable pile of steaming shit. And it's the last product I'll acquire via an MSDN license - that won't be renewed again, either. If this is the pinnacle of MS dev tools, I won't miss them.
L u n a t i c F r i n g e
I'm sure that I'm having more crashes with vs2010 then with vs2008. Also my colleges have that impression, I guess I was to soon to upgrade. Especially with wpf, I got one error and the error list got 200 errors that have nothing to do with it and only way to get rid of them is to do a rebuild. Also now my unit test don't work anymore (check three posts above). Guess they have to make some serious service packs...
-
It was a moment of regrettable naivete that led me to install this POS to begin with. The joke documentation system updates have been the last straw. This POS is coming off my machine and will not be re-installed. If I need to do any native development that can't be done with VS2008, it'll be done with NetBeans. VS2010 is an unusable pile of steaming shit. And it's the last product I'll acquire via an MSDN license - that won't be renewed again, either. If this is the pinnacle of MS dev tools, I won't miss them.
L u n a t i c F r i n g e
-
It was a moment of regrettable naivete that led me to install this POS to begin with. The joke documentation system updates have been the last straw. This POS is coming off my machine and will not be re-installed. If I need to do any native development that can't be done with VS2008, it'll be done with NetBeans. VS2010 is an unusable pile of steaming shit. And it's the last product I'll acquire via an MSDN license - that won't be renewed again, either. If this is the pinnacle of MS dev tools, I won't miss them.
L u n a t i c F r i n g e
As a C++ developer, IMHO VC++ 6.0 was the pinnacle. Unfortunately since this has been dropped by M$ I reluctantly upgraded to VS2005 and then VS2008 both of which are great lumbering beasts - trying to be all things to all men. Compiling takes an age, the resource editor is rubbish and as for help - well thats already been covered. Fortunately I still have the MSDN library 2000 CD installed which gets me what I want - and fast. Is ther a "I hate Visual Studio 20XXX" web site or forum where we can all vent our spleens? :laugh:
-
As a C++ developer, IMHO VC++ 6.0 was the pinnacle. Unfortunately since this has been dropped by M$ I reluctantly upgraded to VS2005 and then VS2008 both of which are great lumbering beasts - trying to be all things to all men. Compiling takes an age, the resource editor is rubbish and as for help - well thats already been covered. Fortunately I still have the MSDN library 2000 CD installed which gets me what I want - and fast. Is ther a "I hate Visual Studio 20XXX" web site or forum where we can all vent our spleens? :laugh:
-
It was a moment of regrettable naivete that led me to install this POS to begin with. The joke documentation system updates have been the last straw. This POS is coming off my machine and will not be re-installed. If I need to do any native development that can't be done with VS2008, it'll be done with NetBeans. VS2010 is an unusable pile of steaming shit. And it's the last product I'll acquire via an MSDN license - that won't be renewed again, either. If this is the pinnacle of MS dev tools, I won't miss them.
L u n a t i c F r i n g e