Why visual studio sucks today
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
This was the case with VS 2008 too. If you have any file open with CSS/HTML errors they are displayed in the task list. I always go to the output window to see the real errors. Alternatively, you can disable HTML validation.
-
Christian Graus wrote:
I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
This was the case with VS 2008 too. If you have any file open with CSS/HTML errors they are displayed in the task list. I always go to the output window to see the real errors. Alternatively, you can disable HTML validation.
These are not HTML errors, they are errors with code accessing server controls. Will that fix those, too ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
How can this thing be so broken ?
because it started as a small tool for a 6 month project that too many people got their hands on before the developer could kill it over kludge.
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
The real error is generally the last one in the list!
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
the error list gives a ton of 'the element xxx does not exist' errors
That started with 2005. You'd thinks someone at M$FT would have noticed the problem by now. . .
“The whole aim of practical politics is to keep the populace alarmed (and hence clamorous to be led to safety) by menacing it with an endless series of hobgoblins, all of them imaginary.” ~ H.L. Mencken
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Perhaps I lead a charmed life, or I'm blissfully ignorant, but I don't have any problems with VS2010. It is fast and reliable for me even while doing SharePoint applications.
I know the language. I've read a book. - _Madmatt
-
Perhaps I lead a charmed life, or I'm blissfully ignorant, but I don't have any problems with VS2010. It is fast and reliable for me even while doing SharePoint applications.
I know the language. I've read a book. - _Madmatt
Mark Nischalke wrote:
Perhaps I lead a charmed life, or I'm blissfully ignorant, but I don't have any problems with VS2010.
Same. Sometimes it gets a little slow. Or has some querks. A screen loading weird, or having to re-open files but I have about 100 million add ons so it is probably me :D
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
I often just switch to the output window, it often makes more sense ... possibly because of intellisense :-O
-
Mark Nischalke wrote:
Perhaps I lead a charmed life, or I'm blissfully ignorant, but I don't have any problems with VS2010.
Same. Sometimes it gets a little slow. Or has some querks. A screen loading weird, or having to re-open files but I have about 100 million add ons so it is probably me :D
jgasm wrote:
100 million add ons
That's almost as many apps in the Windows Phone 7 AppStore :laugh:
I know the language. I've read a book. - _Madmatt
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
I'd go about searching for the changes you need to make in another way: 1. Add a new constructor with the new parameter you need and maybe chaining to the existing one if that fits your needs. 2. Use "Find all references" on the constructor you wanted to replace. 3. After fixing all constructor invocations from step two to accord with the new constructor you're free to delete the one you wanted to replace (see 1. though if you chained the new constructor to old one it has to be integrated into the new one or has to stay in place) I know that this is just a workaround to the quirky VS behavior, but if it works what the heck! Cheers!
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
How can this thing be so broken ?
Because even though it is so broken, everyone buys it anyway?
-
Christian Graus wrote:
How can this thing be so broken ?
Because even though it is so broken, everyone buys it anyway?
We are addicted to the whole MS thing. But then in terms of interoperability there is little else out there. Ho hum, rough with the smooth I suppose.
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC League Table Link CCC Link[^]
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
Funny, I appear to have used this title before...
I thought you owned the copyright... ;P
-
Funny, I appear to have used this title before... So, I started this new website with VS2010, only to find it was so slow, buggy and unstable that I forever banished it from my electronic kingdom. VS2008 is *better*, but if I ever break my code, the error list gives a ton of 'the element xxx does not exist' errors, in pages not even related to the one that's broken. Just now, I decided to change how I do something, so I added an argument to a constructor ( which I needed to do ) and did a build for the error list to show me where I assign these objects, the code I now need to change. This error did not even appear, just a ton of errors claiming that page elements I access as variables do not exist, through the project. I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Christian Graus wrote:
I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
I remember learning (or trying to learn) PASCAL when I was 17, on some mainframe computer. I misplaced semicolon, and I would get hundreds of errors, at least one for every subsequent line of code. Took me days to realize the compiler was dumber than George Bush. Hmmm. That's sort of a broken metaphor. Oh well. Marc
-
Christian Graus wrote:
I find in general that one real error, will generate 20-30 bogus ones. How can this thing be so broken ?
I remember learning (or trying to learn) PASCAL when I was 17, on some mainframe computer. I misplaced semicolon, and I would get hundreds of errors, at least one for every subsequent line of code. Took me days to realize the compiler was dumber than George Bush. Hmmm. That's sort of a broken metaphor. Oh well. Marc
I had the same experience learning COBOL, Pascal was relatively easy using Turbo Pascal.
-
We are addicted to the whole MS thing. But then in terms of interoperability there is little else out there. Ho hum, rough with the smooth I suppose.
------------------------------------ I will never again mention that I was the poster of the One Millionth Lounge Post, nor that it was complete drivel. Dalek Dave CCC League Table Link CCC Link[^]