Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge master to features/source-generators #44111

Merged

Conversation

dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from master into features/source-generators.

git fetch --all
git checkout merges/master-to-features/source-generators
git reset --hard upstream/features/source-generators
git merge upstream/master
# Fix merge conflicts
git commit
git push upstream merges/master-to-features/source-generators --force

Once all conflicts are resolved and all the tests pass, you are free to merge the pull request.

y87feng and others added 30 commits April 10, 2020 21:19
…ceDistanceComparer.cs

Co-Authored-By: Andrew Hall <ryzngard@live.com>
…ceDistanceComparer.cs

Co-Authored-By: Andrew Hall <ryzngard@live.com>
…sualBasicAddExplicitCastCodeFixProvider.vb

Co-Authored-By: CyrusNajmabadi <cyrus.najmabadi@gmail.com>
…sualBasicAddExplicitCastCodeFixProvider.vb

Co-Authored-By: CyrusNajmabadi <cyrus.najmabadi@gmail.com>
…ddExplicitCastCodeFixProvider.cs

Co-Authored-By: Andrew Hall <ryzngard@live.com>
…ddExplicitCastCodeFixProvider.cs

Co-Authored-By: Andrew Hall <ryzngard@live.com>
msftbot[bot] and others added 20 commits May 7, 2020 05:33
…-to-master

Merge release/dev16.7-preview1 to master
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
Cache export provider factories
 Exclude csc.exe from optprof profiling
Skip executing analyzers by default on local builds for solutions in the repo
…Rename

Remove changes to XAML and F# IInlineRenameInfo interfaces
…-fix

Code fix for CS0109 (The new keyword is not required)
When caching dependent-type-results, don't try to re-infer the originating project.
Copy link

@ghost ghost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approval

@ghost ghost merged commit 4a0a0fc into features/source-generators May 11, 2020
@ghost ghost deleted the merges/master-to-features/source-generators branch May 11, 2020 19:48
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.