- 26 10月, 2016 8 次提交
-
-
由 Jason Malinowski 提交于
Consume .editorconfig options for standard .editorconfig values
-
由 Heejae Chang 提交于
Fix CodeLens test indicators for OOP
-
由 Paul Vick 提交于
-
由 Jonathon Marolf 提交于
update MicroBuild.Plugins.SwixBuild
-
由 AlekseyTs 提交于
Strengthen the check that detects nullable lifting for a user-defined conversion during lowering.
-
由 AlekseyTs 提交于
Type comparison should ignore insignificant differences like tuple name mismatch, etc. Fixes https://devdiv.visualstudio.com/DevDiv/_workitems?id=269808.
-
由 Jared Parsons 提交于
Compiler server should be tolerant of corrupted application settings
-
由 Ravi Chande 提交于
Make target type preselection less aggressive
-
- 25 10月, 2016 14 次提交
-
-
由 Jonathon Marolf 提交于
We received e-mails over the weekend specifying some changes that were needed to our setup authoring. This makes the requested modifications.
-
由 Paul Vick 提交于
Fix JSON remoting for CodeLens
-
由 Paul Vick 提交于
-
由 Paul Vick 提交于
-
由 Ravi Chande 提交于
-
由 Ravi Chande 提交于
-
由 Jared Parsons 提交于
-
由 Ravi Chande 提交于
Port https://github.com/dotnet/roslyn/pull/14289 to RC
-
由 Ravi Chande 提交于
Signature help improvements for C# tuples (renamed to work around jenkins issues)
-
由 Ravi Chande 提交于
-
-
由 Jason Malinowski 提交于
-
由 David Poeschl 提交于
Convert Naming Styles to a grid-based UI and enable rules by default
-
由 David Poeschl 提交于
Add NamingPreferences to the SimplificationOptionProvider
-
- 24 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
When a machine.config or app.config is corrupted it's possible for `ConfigurationManager.AppSettings` to throw an exception. The compiler server was not tolerant of such a failure and as a result would terminate immediately after startup. The compiler workflow is generally very tolerant of failures in the server. It is an optimization only, and any crashes, bad results, etc ... are ignored and the workflow will fall back to the command line. Failing on startup is one case the workflow does not handle well right now. The workflow does not distinguish between a crash at startup and a very slow JIT situation (as is the case with old, single core machines). As such it ends up adding an unnecessary 25 second delay to the compilation. Issue #14265 tracks fixing this delay but it won't make RC. Up until now only one incident of corrupted app settings was reported and it was considered an extremely unlikely problem (as it would break a lot of apps). Going through VS feedback last night I found one other incident which could would be explained by this problem. Hence it's possible this is more likley than originally thought (although still very rare) and decided to put it into RC. closes #14288
-
- 23 10月, 2016 1 次提交
-
-
由 Jared Parsons 提交于
Handle TMP correctly in compiler server
-
- 22 10月, 2016 5 次提交
-
-
由 Jared Parsons 提交于
-
由 David Poeschl 提交于
Don't null ref if we can't find the host document in SetDocumentContext
-
由 Ravi Chande 提交于
Port https://github.com/dotnet/roslyn/pull/14251 to RC
-
由 David Poeschl 提交于
Fixes internal bug #237579
-
由 David Poeschl 提交于
This allows the VSI option resetter to reset the option (so that stale default values aren't used).
-
- 21 10月, 2016 11 次提交
-
-
由 Heejae Chang 提交于
fix null exception happening due to OOP analyzer engine not providing right AnalyzerOptions
-
由 CyrusNajmabadi 提交于
Truncate resource string as it affects internal tooling.
-
由 CyrusNajmabadi 提交于
Fix out of range exception when producing classified text for FindReferences
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 CyrusNajmabadi 提交于
-
由 Heejae Chang 提交于
-
由 Heejae Chang 提交于
fixed 2 issue where IDE analyzer throws null exception and host analyzer exception message not going away from error list issue.
-
由 CyrusNajmabadi 提交于
-
由 Tanner Gooding 提交于
Updating our swr files to use 'Microsoft.Net.4.6.1.FullRedist.Resources' instead of 'Microsoft.Net.4.6.1.FullRedist.Resource'
-
由 Tanner Gooding 提交于
Updating our swr files to use 'Microsoft.Net.4.6.1.FullRedist.Resources' instead of 'Microsoft.Net.4.6.1.FullRedist.Resource'
-