- 25 2月, 2020 1 次提交
-
-
由 Joey Robichaud 提交于
Make unit testing analyzer a singleton
-
- 22 2月, 2020 4 次提交
-
-
由 Artur Spychaj 提交于
-
由 Artur Spychaj 提交于
-
由 Artur Spychaj 提交于
-
由 Artur Spychaj 提交于
-
- 21 2月, 2020 2 次提交
-
-
由 Jason Malinowski 提交于
Change our error handling for GraphQueryManager
-
由 Charles Stoner 提交于
-
- 20 2月, 2020 5 次提交
-
-
由 Jason Malinowski 提交于
Calls to our remote process are wrapped in a "SoftCrashException" in an attempt to prevent crashes; this exception derives from OperationCanceledException. This backfires: our GraphQueryManager does support reporting exceptions to an info bar, so this means anything that goes wrong in the RPC then gets silently swallowed because we think it's cancellation instead. Unwrapping makes things better again. This commit should be reverted when we remove SoftCrashException in https://github.com/dotnet/roslyn/issues/40476.
-
由 Jason Malinowski 提交于
Previously, something going wrong would crash the process due to our fatal error handling in SafeContinueWith. Now we'll just report a non-fatal error report.
-
由 Jason Malinowski 提交于
-
由 msftbot[bot] 提交于
Merge release/dev16.4 to release/dev16.5
-
由 Joey Robichaud 提交于
Always return available for SyncClassView command
-
- 19 2月, 2020 2 次提交
-
-
由 Joey Robichaud 提交于
Fix classview sync
-
由 Joey Robichaud 提交于
-
- 14 2月, 2020 1 次提交
-
-
由 Andy Gocke 提交于
The changes made in https://github.com/dotnet/roslyn/pull/41123 fix the GetHashCode for SubstitutedMethodSymbol for more nullability scenarios, but end up hashing all generic methods with a non-generic containing type into the same bucket. This can cause large performance regressions for the compiler. This change ensures that substituted symbols which have substitutions equivalent to their original methods' type parameter continue to be equal, but substituted methods with different type substitutions are not considered equal.
-
- 13 2月, 2020 3 次提交
-
-
由 Joey Robichaud 提交于
Skip flaky Emit test
-
由 Joey Robichaud 提交于
-
-
- 11 2月, 2020 1 次提交
-
-
由 Joey Robichaud 提交于
Switch to UI thread before invoking Workspace.TryApplyChanges
-
- 10 2月, 2020 1 次提交
-
-
由 msftbot[bot] 提交于
LOC CHECKIN | dotnet/roslyn master | 20200204
-
- 08 2月, 2020 1 次提交
-
-
由 Joey Robichaud 提交于
Change to the VS release queue for integration tests
-
- 07 2月, 2020 2 次提交
-
-
由 Joey Robichaud 提交于
-
由 Manish Vasani 提交于
We recently changed this code to switch from using the Workspace Options setter (now deprecated) to Workspace.TryApplyChanges. This causes an intermittent exception [here](https://github.com/dotnet/roslyn/blob/aeb47891e92341b700c3a290a92553b8a91b445a/src/VisualStudio/Core/Def/Implementation/ProjectSystem/VisualStudioWorkspaceImpl.cs#L374-L377) when TryApplyChanges is invoked from a background thread. Fixes internal Watson bug [#1062942](https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1062942)
-
- 06 2月, 2020 1 次提交
-
-
由 Jason Malinowski 提交于
Delete the lazy caching of GetLatestProjectVersion()
-
- 05 2月, 2020 3 次提交
-
-
由 msftbot[bot] 提交于
Update arcade to support SDK publishing
-
-
由 Jason Malinowski 提交于
Solution.GetLatestProjectVersion() returns the highest project version of any of the Projects in the Solution. This is lazily computed, but the lazy computation has a fatal flaw. It's implemented with a Lazy<VersionStamp>, and if a Solution is changed and no project was changed (say, you only modified a document's text), the existing Lazy<VersionStamp> is reused. This causes us to root an older SolutionState or ProjectState until somebody were to call GetLatestProjectVersion() and cause the Lazy<VersionStamp> to be evaluated. Except...that would never happen. It turns out that nothing calls GetLatestProjectVersion() in Visual Studio anywhere that I can find. The only call is in one unit test that calls it and then ignores the result. Thus, we'd simply leak the SolutionState/ProjectState until some code ran that knew it could explicitly state the value instead of reuse the existing Lazy<VersionStamp>. Looking through history, it appears that this used to be used more regularly as a part of an older implementation of the ProjectDependencyGraph, but that was removed in abd7654e. Since nobody calls this, and the actual computation (just looping through all projects to find the newest stamp) is fairly trivial, I'm just going to delete all the lazy handling and just inline the computation. In the unlikely case that this ever becomes a hot path, we can revisit the laziness at that time.
-
- 04 2月, 2020 12 次提交
-
-
-
由 Jason Malinowski 提交于
Run naming styles on closed files
-
由 Chris Sienkiewicz 提交于
* MethodSymbol and FieldSymbol equality fixes: - Defer the equality of method/field symbol to the substituted symbol when compared - Make the hashcode of substituted method/field defer to the original definition
-
由 Joey Robichaud 提交于
Preserve "unsafe" when refactoring between properties and methods
-
由 Sam Harwell 提交于
Allow -launch to be used without -build
-
由 Sam Harwell 提交于
Annotate implementations of IEventSymbol
-
由 Sam Harwell 提交于
Annotate implementations of ILabelSymbol
-
由 Julien Couvreur 提交于
Rename from IncludeNonNullableReferenceTypeModifier to IncludeNotNullableReferenceTypeModifier (#41332)
-
由 Tomáš Matoušek 提交于
* Set TEMP environment variable to $TempDir on CI machines https://github.com/dotnet/arcade/pull/4744 reverted setting the variable in `tools.ps1` due to issues it caused in other repos.
-
由 Manish Vasani 提交于
Stop Simplifier.ReduceAsync removing empty arg lists from delegates
-
由 Allison Chou 提交于
Fix for Visual Studio crashes when adding a parameter to a function
-
由 Sam Harwell 提交于
-
- 03 2月, 2020 1 次提交
-
-
由 Sam Harwell 提交于
-