guard us from build errors which are marked as CS or VBXXXX for a lin…

Disable useUserOverride in CultureContext

Remove InitialTargets=MakeCompilerScriptsExecutable

Merge `private protected` feature into master for C# 7.2 and VB 15.6.

Merge master into privateProtected branch

Fixed Inline Temporary Variable refactoring

Updating some nuspec to list the correct framework requirements and dependencies.

guard us from build errors which are marked as CS or VBXXXX for a linked file that doesnt belong to current solution we have.

this can happen for a project that is just added or already removed or project is added but design time build is not finished.

previously, that could crash VS, but now we will handle it gracefully.

we should now also maintain orders build error is reported.

Delete .Next projects

* Remove context (enclosing type name) from C# parser.
* Add a test demonstrating that unicode escapes are significant to determining if a method is a ctor.
This is a prerequisite to #367

Merge master into privateProtected

Fix up .gitattributes to clone .sh files with LF

This transfers all the VSIX contents of VisualStudioSetup.Next
back to VisualStudioSetup, making VisualStudioSetup a Dev15 VSIX again.

We don't need the split anymore now that we're only supporting Dev15.

Unfortunately this required the introduction of a NuGet package that
has a namespace "Workspace" to our VS project, which meant I had to
disambiguate Workspace wherever it's used in that layer. I considered
doing an extern alias instead to disambiguate, but applying that to a
ProjectReference isn't supported. That's tracked by NuGet/Home#4989.

This lived in EditorFeatures.Next since it depended on Dev15 features,
but EditorFeatures is now Dev15 only so we can move this.

These helpers allowed us to do lightup between Dev14 and Dev15 for some
features. We no longer support Dev14, so that is unnecessary.

Previously, we supported a light-up ability where we would use the
appropriate Navigate To APIs for Dev14 or Dev15 depending upon which
version of Visual Studio we were targeting. We no longer support such
a configuration, so we can flatten all the code and indirection back
down.

Previously, we supported a light-up ability where we would use the
appropriate completion APIs for Dev14 or Dev15 depending upon which
version of Visual Studio we were targeting. We no longer support such
a configuration, so we can flatten all the code and indirection back
down.

Fix completion crash in tuple in alias

Stop swallowing JTF exceptions

Merge dev15.4.x to master

This should have been removed in an earlier commit, but was forgotten

Fix issue with merging parameters