Something thta was actually improved is going from VS2008 to 2010
-
Giving credit where credit is due since we normally post threads bashing it for steps backwards... In VS 2k8 the Tasklist dialog was only useful in VB projects because while with VB.net it showed all the //TODO comments in the solution, with C# it only showed them for open files, and in C++ only for the file being displayed. These weren't user changeable. The only way you could get something close in a large project was via #warning TODO, and then doing a build all... I just discovered that 2010 lists //TODO comments solution wide for C# solutions. (I don't have a C++ one to test against.) I'm not sure if I like having them in a separate list from any warnings since both are things that you need to go back and fix later; but at least they made the function useful...
3x12=36 2x12=24 1x12=12 0x12=18
-
Giving credit where credit is due since we normally post threads bashing it for steps backwards... In VS 2k8 the Tasklist dialog was only useful in VB projects because while with VB.net it showed all the //TODO comments in the solution, with C# it only showed them for open files, and in C++ only for the file being displayed. These weren't user changeable. The only way you could get something close in a large project was via #warning TODO, and then doing a build all... I just discovered that 2010 lists //TODO comments solution wide for C# solutions. (I don't have a C++ one to test against.) I'm not sure if I like having them in a separate list from any warnings since both are things that you need to go back and fix later; but at least they made the function useful...
3x12=36 2x12=24 1x12=12 0x12=18
-
Giving credit where credit is due since we normally post threads bashing it for steps backwards... In VS 2k8 the Tasklist dialog was only useful in VB projects because while with VB.net it showed all the //TODO comments in the solution, with C# it only showed them for open files, and in C++ only for the file being displayed. These weren't user changeable. The only way you could get something close in a large project was via #warning TODO, and then doing a build all... I just discovered that 2010 lists //TODO comments solution wide for C# solutions. (I don't have a C++ one to test against.) I'm not sure if I like having them in a separate list from any warnings since both are things that you need to go back and fix later; but at least they made the function useful...
3x12=36 2x12=24 1x12=12 0x12=18
That's good: but just set "Treat warnings as errors" to "All" and you have to fix them pretty immediately... Personally, I prefer to have this set as a default - the compiler is clever enough nowadays that a warning is something you should look at. Not like the old days when warnings were just a PITA...
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
-
Giving credit where credit is due since we normally post threads bashing it for steps backwards... In VS 2k8 the Tasklist dialog was only useful in VB projects because while with VB.net it showed all the //TODO comments in the solution, with C# it only showed them for open files, and in C++ only for the file being displayed. These weren't user changeable. The only way you could get something close in a large project was via #warning TODO, and then doing a build all... I just discovered that 2010 lists //TODO comments solution wide for C# solutions. (I don't have a C++ one to test against.) I'm not sure if I like having them in a separate list from any warnings since both are things that you need to go back and fix later; but at least they made the function useful...
3x12=36 2x12=24 1x12=12 0x12=18
Another thing I just noticed yesterday that I like. It's a small thing but nice. The IntelliSense is smarter. Say you have a class called Transaction and a property TransSize. And a variable/object of type Transaction named t. Now after the dot in t. If you type Size/size you still get the TransSize property. Prior to VS 2010 you wouldn't get it. I'm sure I've used it before. Just that I haven't noticed it. :)
All the best, Dan
-
That's good: but just set "Treat warnings as errors" to "All" and you have to fix them pretty immediately... Personally, I prefer to have this set as a default - the compiler is clever enough nowadays that a warning is something you should look at. Not like the old days when warnings were just a PITA...
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
I'll agree with it being something you should look at; but it doesn't have to be something that needs fixed immediately. eg xml comments not existing/matching when in the middle of writing/modifying a method. In general I make sure any code I commit doesn't have any (new) warnings; there've been people I worked with I wished I could force no warnings in a commit on. Especially since at times their issues weren't just stuff like missing comments but actual, bugs that he made repeatedly. Warnings as errors is even more problematic when you have 3rd party authored code in your project. In my current project I have about 3 dozen files with this
#pragma warning disable 1591, 1572, 1573 //1591 missing comment, 1572 parameter not in definition, 1573 parameter not in comment
#warning Lots of missing/outdated xml comments in this fileat the start. These files combined had about 800 missing/invalid xml comment warnings behind them. I'm filling them in as I go, but stopping for a week or two to figure out WTF each method did would not be a reasonable use of my time. Then there's a half dozenish variables that are either leftover from code that was removed, or were added in anticipation of features that aren't implemented yet. Figuring them out all at once would also be a pain...
3x12=36 2x12=24 1x12=12 0x12=18
-
I'll agree with it being something you should look at; but it doesn't have to be something that needs fixed immediately. eg xml comments not existing/matching when in the middle of writing/modifying a method. In general I make sure any code I commit doesn't have any (new) warnings; there've been people I worked with I wished I could force no warnings in a commit on. Especially since at times their issues weren't just stuff like missing comments but actual, bugs that he made repeatedly. Warnings as errors is even more problematic when you have 3rd party authored code in your project. In my current project I have about 3 dozen files with this
#pragma warning disable 1591, 1572, 1573 //1591 missing comment, 1572 parameter not in definition, 1573 parameter not in comment
#warning Lots of missing/outdated xml comments in this fileat the start. These files combined had about 800 missing/invalid xml comment warnings behind them. I'm filling them in as I go, but stopping for a week or two to figure out WTF each method did would not be a reasonable use of my time. Then there's a half dozenish variables that are either leftover from code that was removed, or were added in anticipation of features that aren't implemented yet. Figuring them out all at once would also be a pain...
3x12=36 2x12=24 1x12=12 0x12=18
I'd be tempted to send the error list to the company and complain: but then I'm a contrary bod at times. That's actually part of why I prefer to run with warnings as errors: it forces me to keep the documentation up to date (as I know I will have difficulty finding time to go back and do it later).
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
-
I'd be tempted to send the error list to the company and complain: but then I'm a contrary bod at times. That's actually part of why I prefer to run with warnings as errors: it forces me to keep the documentation up to date (as I know I will have difficulty finding time to go back and do it later).
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
-
Why am I not surprised? :laugh:
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together. Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
