- #VISUAL STUDIO 2022 RESHARPER UPDATE#
- #VISUAL STUDIO 2022 RESHARPER FULL#
- #VISUAL STUDIO 2022 RESHARPER PROFESSIONAL#
If you think these posts do not belong here, please leave a comment, and I'll consider moving my development articles to a separate blog.Everyone knows Visual Studio 2010 can be slow. Im gonna run mine with the commands you suggested and will upload the reports.ĮDIT: Side, the same freezes i also experience in DotPeek (not within VS, the application), i often select a couple of assemblies, and before I can even hit the generate pdb button, the app freezes and never unfreezes again - i have to kill it from the task manager then.Another post for ASP.NET/C# developers reading this blog. Somestimes Resharper does syncing even when nothing happened in 10 minutes (verified by filesystem attributes). And before you ask: All my files are on PCie SSDs.
And while VS always at least remained usable during syncs, with 17.2 - its extreme. I dont know much about the internals of Resharper, but it seems like it doesnt use its cache as efficient as it used to be - so often intensive syncs starting, just because i saved a single js or whatever.
Im publishing a project, the process is not even done, Resharper starts the intense "project sync". One thing that was quite obvious to me, Resharper kicks in too aggressively on this VS version. Sometimes minute long UI freezes, 40GB of Memory Usage from background analysis of a single large file (before 17.2 memory usage never went above single digit numbers, vs complete frezees so i have to crash it - and twice it even lead to a complete computer freeze.
#VISUAL STUDIO 2022 RESHARPER UPDATE#
The update to VS 17.2 felt like being thrown back to a bad experience i had years ago. Thankfully that MVVM toolkit was just something I had in one package, out of interest, not being dependant on it - so removing it causing not a single issue.
#VISUAL STUDIO 2022 RESHARPER FULL#
So far, until VS17.2/2022.1.1 these things never caused issues, but after removing this little nuget, everything is back to normal for the moment: Allocations are low (even less memory used by Resharper than previously), full analysis on all large files dont let resharper use more than 6- 8 at max GB (and only temporartly before dropping back to like 3GB), repeated builds without freezes. I was wondering why i got such extreme complete UI stucks, with the cpu not even under load, and also not much blocking from file access, but to me it explains a lot, also why ReSharper felt like kicking in too aggressively and too often - i assume its the source generators, that are causing this. And somehow, in VS 17.2 there seems now to be a situation, where these 3 participants move into each others way continously, leading to extreme allocations, and freezes.
I actually had this package on a single small library, and not even used - i havent referenced a single type (yet), BUT, it installed MVVM analyzers and (most obviously more responsible for this s**it) source generators into every single project of the solution, even the static asset libraries.
It seems there is some bad synergy between VS 17.2 / Resharper 2022.1.1 and a little bad nuget package: CommunityToolkit.Mvvm in Version 7.12.
#VISUAL STUDIO 2022 RESHARPER PROFESSIONAL#
Stats that every professional would tell you, that your application has serious issues -laugh- but, its not directly Resharpers fault as it turned out. In the first minute after starting and opening the solution there was nearly 60GB of Memory allocation, 10 seconds of UI Freeze und nearly 20% of cpu time consumed by GC. So, I was actually Profiling Visual Studio while I run it under the Resharper verbose logging command.
0 kommentar(er)
