- 12 5月, 2020 5 次提交
-
-
由 Charles Stoner 提交于
-
由 Tomáš Matoušek 提交于
-
由 Tomáš Matoušek 提交于
-
由 Joey Robichaud 提交于
Remove skipAnalyzers from vscode tasks
-
由 Sam Harwell 提交于
Remove pooled Stopwatch
-
- 11 5月, 2020 6 次提交
-
-
由 Joey Robichaud 提交于
Fix link in readme
-
由 Sam Harwell 提交于
Add 'using' misplacement fixer to code-cleanup
-
由 Sam Harwell 提交于
SharedStopwatch already offers a more efficient alternative.
-
https://github.com/dotnet/roslyn由 dotnet-maestro[bot] 提交于
- Microsoft.Net.Compilers.Toolset: 3.7.0-1.20254.1 -> 3.7.0-2.20259.1 Co-authored-by: Ndotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com>
-
由 Shimmy Weitzhandler 提交于
-
由 Yair Halberstadt 提交于
-
- 09 5月, 2020 11 次提交
-
-
由 Neal Gafter 提交于
Relates to #44102
-
由 msftbot[bot] 提交于
When caching dependent-type-results, don't try to re-infer the originating project.
-
由 Cyrus Najmabadi 提交于
-
由 CyrusNajmabadi 提交于
Code fix for CS0109 (The new keyword is not required)
-
由 Allison Chou 提交于
Remove changes to XAML and F# IInlineRenameInfo interfaces
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Cyrus Najmabadi 提交于
-
由 Rikki Gibson 提交于
-
由 Manish Vasani 提交于
Skip executing analyzers by default on local builds for solutions in the repo
-
由 Joseph Musser 提交于
-
- 08 5月, 2020 9 次提交
-
-
由 Tomáš Matoušek 提交于
-
由 Joey Robichaud 提交于
Exclude csc.exe from optprof profiling
-
由 Manish Vasani 提交于
-
由 Charles Stoner 提交于
-
由 Sam Harwell 提交于
Cache export provider factories
-
由 Manish Vasani 提交于
This reverts commit 71716fd5.
-
由 Sam Harwell 提交于
-
由 Manish Vasani 提交于
-
由 Manish Vasani 提交于
This change skips executing analyzers by default on explicit builds (both inside VS and on command line prompt). This should speed up the overall build time of Roslyn.sln when building locally. The only time a developer would want analyzers to run locally outside the typing scenario is to compute the exact set of warnings for a specific project/solution before pushing your local changes to CI. They can now perform the following steps to achieve this: 1. On command line: Build with `/p:UseRoslynAnalyzers=true` or `/p:RunCodeAnalysis=true` 2. Inside VS: 1. Start VS with `%RoslynEnforceCodeStyle% = true`, all builds in VS should execute analyzers 2. Use `Run Code Analysis` command from `Analyze` menu on selected project/solution
-
- 07 5月, 2020 9 次提交
-
-
由 msftbot[bot] 提交于
Merge release/dev16.7-preview1 to master
-
由 msftbot[bot] 提交于
Fix regression using alias qualified name in an is-type expression
-
由 Julien Couvreur 提交于
-
由 msftbot[bot] 提交于
Merge release/dev16.7-preview1 to master
-
由 Manish Vasani 提交于
Use a shared shadow copy assembly loader for all VisualStudioAnalyzer…
-
由 Fredric Silberberg 提交于
-
由 Neal Gafter 提交于
Fixes #44019
-
由 Allison Chou 提交于
-
由 Allison Chou 提交于
-