Skip to content

Conversation

@dotnet-bot
Copy link
Collaborator

This is an automatically generated pull request from dev15.7.x into dev15.7.x-vs-deps.

git fetch --all
git checkout merges/dev15.7.x-to-dev15.7.x-vs-deps-20180205-080023
git reset --hard upstream/dev15.7.x-vs-deps
git merge upstream/dev15.7.x
# Fix merge conflicts
git commit
git push merges/dev15.7.x-to-dev15.7.x-vs-deps-20180205-080023 --force

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

sharwell and others added 30 commits May 4, 2017 20:35
This lock is only being used to protect access to an instance which contains
internal synchronization.
Roslyn is designed to have the simplest possible contribution story:
clone then build. Every pre-req needed is either located on the machine
or bootstrapped via NuGet. All the way down to using an xcopy MSBuild if
needed.

The one case which causes a problem is the VS command prompt. In this
case MSBuild is pre-installed on the machine and may or may not be
suitable for building Roslyn.

Previously when building from a VS command prompt we just used whatever
MSBuild was provided. The assumption being a developer command prompt
was an explicit statement of whath MSBuild you wanted to use. Based on
all of our customer reports though this does not seem to be the
assumption that consumers of our repo have. The build gave them no
explicit errors about the provided toolset and hence when the build
failed they assigned flakiness to our repo.

Going forward we are applying the same version validation to MSBuild
when provided via a developer command prompt. If it doesn't match we
will refuse to build asking the user to upgrade VS or build from a
normal command prompt.
Better handle surrounding directives when inlining a local variable.
Support negative null-checks when we offer a fix to use pattern-matching
#24458)

* fix a case where persistent storage registration fails and some clean up code around it.

* added readonly

* address PR feedback

* removed comments no longer relevant

* renamed lock name
…s are defined. (#24512)

* put listener change back in (#24120)

* leave old types in legacy folder until partner teams move to new interface

* added legacy waiter to support partner teams
jasonmalinowski and others added 20 commits January 31, 2018 14:39
It turns out we had some tests, but the tests were disabled. This was
because the tests weren't working properly anyways: they were calling
into UpdateProjectBinPath which only updated some (but not all) of
the project state. That was an internal helper method that shouldn't
be used by tests. Updating the tests to use
SetBinOutputPathAndRelatedData works better.
This was some legacy code that tried to verify that the references
we have from the project system match up to what DTE and other sources
say. This was debug-only, and the actual asserts were commented out.
This is deadweight at this point, so delete it.
also added RoslynActivityLogger that can be enabled through project-system-tool
Remove duplicate lock DocumentState.s_syntaxTreeToIdMapLock
…0180201-080013

Merge dev15.6.x to dev15.7.x
Omit Default modifier style & code fix
CS1628 error text mentions in parameters; fixes #24584
Previously we were using xunit.console for desktop tests and dotnet-xunit for our
CoreClr tests. This change unifies us on top of xunit.console (now that it has a
netcoreapp2.0 version available).
Verify MSBuild version in Developer CMD prompt
Move to xunit.console for CoreClr tests
@dotnet-bot dotnet-bot requested review from a team as code owners February 5, 2018 08:00
@AbhitejJohn
Copy link
Contributor

@heejaechang : There just seem to be a chain of merge issues after this PR. Tried to fix a few but that seems to lead to others. Can you take a look please.
@jasonmalinowski FYI.

@AbhitejJohn
Copy link
Contributor

Abandoning this in favour of #24665.

@AbhitejJohn AbhitejJohn closed this Feb 6, 2018
@AbhitejJohn AbhitejJohn deleted the merges/dev15.7.x-to-dev15.7.x-vs-deps-20180205-080023 branch February 6, 2018 18:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.