Opinions of VS2019's FxCop analyzers
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
MS saw that Node had NPM, and thought it was a good thing.
Wrong is evil and must be defeated. - Jeff Ello
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
Mike Barthold wrote:
we don't want to have 100's of copies of the same crap running around on the dev machines.
If you use the
PackageReferencesformat of csproj file, you don't end up with multiple copies; you use the same one (as long as the version is the same). -
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
I have no opinion on FxCop because I don't use it and the only time I looked at using it, I couldn't run fast enough away from it.
Latest Articles:
16 Days: A TypeScript application from concept to implementation -
I have no opinion on FxCop because I don't use it and the only time I looked at using it, I couldn't run fast enough away from it.
Latest Articles:
16 Days: A TypeScript application from concept to implementationLucky you. Unfortunately this decision is not up to me. I only have to live with it X|
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
-
I have no opinion on FxCop because I don't use it and the only time I looked at using it, I couldn't run fast enough away from it.
Latest Articles:
16 Days: A TypeScript application from concept to implementationTo be fair, I tried FxCop many times, and once, like in 2005 perhaps? it gave me good tip on how to properly implement IDisposable! Although, since then, it has done nothing else good! :-O :doh:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
I think it's great!!! I use it in every .NET project I have by default. It's in my default Solution-wide Directory.Build.props file, so I don't even have to think about it in any new project, it's just there already.
-
I think it's great!!! I use it in every .NET project I have by default. It's in my default Solution-wide Directory.Build.props file, so I don't even have to think about it in any new project, it's just there already.
Me too, I think it's great. An advanced developer might find some of the warnings unnecessary (myself included) but you just suppress them if you know what you're doing. The real benefit is for junior devs that don't understand the implications of their code (not properly implementing IDisposable for example). I probably won't use it in older, existing projects because I'd be overrun with warnings but I always use it in new code.
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
We use it and have over 75 projects in our solution, and so far it's been, well, a non issue. (I won't say "great" since that implies too much). I can't speak to the startup times (they have always been a bit slow for my liking) but the most important thing for us is we use a custom ruleset so it doesn't complain about dumb things like the way we prefer to format code. For us it's been an important tool to help keep things consistent.
cheers Chris Maunder
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
Same here I'm pissed too - i totally aggree with you Mike - And I like FXCop. Everyone that says "oh i had 100 warnings then" has written code "not good". Normally from 100 FxCop Warning only 3-4 are to ignore… But this update mess with VS 2019 is complete crap.
-
Honestly... it gets worse and worse and worse with Microsoft. What was wrong with the code analysis in VS2017? * perfectly integrated, just runs with the build * no additional installs (or nuget-mayhem) needed * compiler-warnings and all perfectly there for any logs NOW * "install this extension" _or_ "you can do it as nuget" * give a warning of deprecated analysis in each and every project * go there, click install for this, and configure that * starting time of VS tripled since this crap has been installed OMG really??? In a multi-product environment with 100+ solutions which are opened at least once a week (throughout the team) the nuget-mayhem is no option - we don't want to have 100's of copies of the same crap running around on the dev machines. The CI server plays the song of death The performance is down to the late 90's WHY... microsoft... WHY? Do you really want to push us all to the java world with intelliJ? It was already lightyears ahead of Visual Studio and now you implemented the Hogwarts Express from VS to intelliJ. Good job. I'm totally pissed. Have a nice day :-)
|| You know nothing, Jon Snow. || My Android Label (mbar Software) || My Android Apps in Play Store
It slowed things down to a dead crawl, and gave me over 8000 warnings. Of those, roughly 7800 were complete rubbish, yet considered so Very Very Very important (in someone's imagination) that they couldn't be turned off. Pitched it after a few hours.
-
I have no opinion on FxCop because I don't use it and the only time I looked at using it, I couldn't run fast enough away from it.
Latest Articles:
16 Days: A TypeScript application from concept to implementationI look at FXCop maybe once a year, I don't really care for it, but it does once in a while give me a good tidbit that I'll start using, but most of it is just nit picky