- 08 5月, 2020 1 次提交
-
-
由 Sam Harwell 提交于
-
- 07 5月, 2020 3 次提交
-
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
Fixes VSO [#1109876](https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1109876) Verified manually that we no longer generate the CS8032 warnings for projects referencing analyzer assemblies with analyzer dependencies. NOTE: This is a targeted fix for 16.7 Preview1. We can potentially add a regressiont test for this scenario to verify that all VisualStudioAnalyzer instances share the same shadow copy assembly loader. However, @tmat is planning to soon delete VisualStudioAnalyzer and avoid loading analyzers in devenv process, so this code will go away soon.
-
由 Sam Harwell 提交于
-
- 06 5月, 2020 1 次提交
-
-
由 Jason Malinowski 提交于
We were incorrectly emitting our dependency of Microsoft.VisualStudio.Composition and Microsoft.CSharp; instead of pointing to the version that we were actually consuming, we were emitting our version in place of version we depending on.
-
- 05 5月, 2020 3 次提交
-
-
由 Allison Chou 提交于
-
由 Allison Chou 提交于
-
由 Sam Harwell 提交于
-
- 04 5月, 2020 1 次提交
-
-
由 Sam Harwell 提交于
-
- 03 5月, 2020 6 次提交
-
-
由 Tomáš Matoušek 提交于
* Remove direct usage of Connection * Refactor connection pooling * SolutionChecksumUpdater * GlobalNotificationRemoteDeliveryService
-
由 Tomáš Matoušek 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Tomáš Matoušek 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
- 02 5月, 2020 8 次提交
-
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Tomáš Matoušek 提交于
-
由 Sam Harwell 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-
- 01 5月, 2020 4 次提交
-
-
由 Sam Harwell 提交于
-
由 Jason Malinowski 提交于
It's possible to have a batch remove and re-add a project reference to the same project, even if you're removing different reference paths. If that happened, we'd try to add the duplicate reference first which would crash. Fixes https://github.com/dotnet/roslyn/issues/39032 Fixes https://github.com/dotnet/roslyn/issues/43632
-
由 Jason Malinowski 提交于
These should only get called as a part of a larger operation that is already holding the lock; we can assert that directly and then remove the extra lock statements.
-
由 David Barbet 提交于
-
- 30 4月, 2020 10 次提交
-
-
由 Sam Harwell 提交于
-
由 Jason Malinowski 提交于
-
由 Jason Malinowski 提交于
-
由 Manish Vasani 提交于
Fixes #43812 My prior Options related code refactoring causes certain CodeStyle option updates in the CodeStyle Tools Options page to not get saved properly. As a result, updating these options in this page has no effect and user is forced to workaround by manually updating/creating an editorconfig file. The core issue is that `SetOptionAndUpdatePreview<T>` method is invoked in two different ways for CodeStyle options: 1. 'T value' argument is the new underlying bool/enum CodeStyle value to set. 1. 'T value' argument is the new CodeStyle option wrapping the new underlying bool/enum + notification preference to set. We were only handling the first case, and the second one silently throws a cast exception, rendering the option set having no effect. Now we handle both cases. I have manually verified that updating all the CodeStyle Options on the page and closing/re-opening the page has changed values. We are also doing couple of follow-up items to guard against such regressions in future: 1. Adding the verification of CodeStyle options page scenarios to our internal manual test pass scenario list. These will be manually verified prior to each release. 2. #43813: Investigate writing an integration test for Tools Options CodeStyle page
-
由 Tomáš Matoušek 提交于
* Move RazorRemoteHostClient functionality to ExternalAccess.Razor * Add file
-
由 Andrew Hall 提交于
Sometimes we do want the preview/provisional tab to receive focus. For example, when navigating to definition of a symbol and there's only one definition. Fixes #43585
-
由 David Poeschl 提交于
-
由 David Poeschl 提交于
-
由 David Poeschl 提交于
- 29 4月, 2020 3 次提交
-
-
由 Sam Harwell 提交于
-
由 Sam Harwell 提交于
-