3 ms·

Interesting. I've observed the opposite, with VS 2017 often being unbearably slow in comparison as the codebase gets large. But I can appreciate that you may be

Interesting. I've observed the opposite, with VS 2017 often being unbearably slow in comparison as the codebase gets large. But I can appreciate that you may be experiencing the opposite. I highly recommend filing issues, especially if you can do so with a specific, reproducible problems. Those tend to get resolved quite quickly.

Const-me 7y ago
> Those tend to get resolved quite quickly. The issues are getting resolved in the public bug trucker, pretty quickly indeed, typically saying "can't reproduce, won't fix", sometimes "not a bug, won't fix". I'm not sure the software problems are getting resolved.
- phillipcarter 7y ago
  You can look through GH milestones to see specific issues fixed in results. For example, here are the 230 tracked items done for the VS 16.4 public release: https://github.com/dotnet/roslyn/milestone/53?closed=1 https://github.com/dotnet/roslyn/milestone/53?closed=1 You can also see that there are many more resolved issues in previews of that public release: https://github.com/dotnet/roslyn/milestones?state=closed https://github.com/dotnet/roslyn/milestones?state=closed So there are a _lot_ of legitimate problems being fixed and enhancements being added over pretty short periods of time. When something is resolved as "no reproduction" or "not a bug", that's because there was an earnest attempt to reproduce an issue with the latest bits set to go out to a release with no reproduction, or something is truly by design (e.g., user files an issue because they would prefer a feature to do something different than it does today).
  - Const-me 7y ago
    My experience might be irrelevant to Roslyn, I experienced these things when reporting Visual Studio bugs in general. Examples: https://developercommunity.visualstudio.com/content/problem/402401/clexe-compiler-driver-cannot-handle-long-file-path.html https://developercommunity.visualstudio.com/content/problem/... (BTW, people have been reporting that bug for years now) https://developercommunity.visualstudio.com/content/problem/630991/windows-runtime-doesnt-initialize-some-dll-modules.html https://developercommunity.visualstudio.com/content/problem/... https://developercommunity.visualstudio.com/content/problem/123503/fatal-error-c1001-an-internal-error-has-occurred-i-8.html https://developercommunity.visualstudio.com/content/problem/... https://developercommunity.visualstudio.com/content/problem/723192/memory-mapped-file-accessor-ignores-structlayout-a.html https://developercommunity.visualstudio.com/content/problem/...

Const-me 7y ago

> Those tend to get resolved quite quickly. The issues are getting resolved in the public bug trucker, pretty quickly indeed, typically saying "can't reproduce, won't fix", sometimes "not a bug, won't fix". I'm not sure the software problems are getting resolved.

phillipcarter 7y ago
You can look through GH milestones to see specific issues fixed in results. For example, here are the 230 tracked items done for the VS 16.4 public release: https://github.com/dotnet/roslyn/milestone/53?closed=1 https://github.com/dotnet/roslyn/milestone/53?closed=1 You can also see that there are many more resolved issues in previews of that public release: https://github.com/dotnet/roslyn/milestones?state=closed https://github.com/dotnet/roslyn/milestones?state=closed So there are a _lot_ of legitimate problems being fixed and enhancements being added over pretty short periods of time. When something is resolved as "no reproduction" or "not a bug", that's because there was an earnest attempt to reproduce an issue with the latest bits set to go out to a release with no reproduction, or something is truly by design (e.g., user files an issue because they would prefer a feature to do something different than it does today).
- Const-me 7y ago
  My experience might be irrelevant to Roslyn, I experienced these things when reporting Visual Studio bugs in general. Examples: https://developercommunity.visualstudio.com/content/problem/402401/clexe-compiler-driver-cannot-handle-long-file-path.html https://developercommunity.visualstudio.com/content/problem/... (BTW, people have been reporting that bug for years now) https://developercommunity.visualstudio.com/content/problem/630991/windows-runtime-doesnt-initialize-some-dll-modules.html https://developercommunity.visualstudio.com/content/problem/... https://developercommunity.visualstudio.com/content/problem/123503/fatal-error-c1001-an-internal-error-has-occurred-i-8.html https://developercommunity.visualstudio.com/content/problem/... https://developercommunity.visualstudio.com/content/problem/723192/memory-mapped-file-accessor-ignores-structlayout-a.html https://developercommunity.visualstudio.com/content/problem/...