this is to make develop - debug cycle easiler when adding new features to service hub.

to enable this, turn on Roslyn/FeatureManager/Features/RemoteHost and RemoteHostInProc

once enabled, InProcRemoteHostClient will be used instead of ServiceHubRemoteHostClient

except concrete type of RemoteHostClient, all other parts, exactly same code will be used.

InProcRemoteHostClient can be used in unit test to test client and server side as they are.

The tool now lives under dotnet/roslyn-tools.

This reverts commit 720f5c5e, reversing
changes made to 6a6043c3.

The dependency projects serve a few purposes:

- Help ensure package unity by serving as a single place for a NuGet reference.
- Make NuGet updates simple by having a single place to change.
- Grouping together related packages to make it easy to take a dependency on say Visual Studio editor.

The first two points are largely obsolete now that our project.json references are strictly validated on every build and have a single update mechanism.  This meant a lot of our depnedency projects were just making Roslyn.sln bigger.

As such I went through and deleted all of them which had only 1 or 2 project.json entries.  I left the VS ones which tend to group 10+ references together.  They are still serving a valid "reference VS" purpose.

changes include
make SourceText::GetChecksum and AnalyzerTelemetry contructor public.

added MustRunInProc in IBuiltInAnalyzer and some clean up around serializing Solution/Project/DocumentId and how DocumentState is exposed.

simplified temporary storage service's temporary storage management and added ability to attach to existing temporary storage

solution checksum and serialization service.

added remote host client
- this gives an ability for host (vs) to talk to remote host (service hub)

rename and moving files between feature/workspace layers
- only real change is having ICompilerDiagnosticAnalyzer interface which can either have inproc implementation or out of proc implementation.
- inproc is needed since diagnostics are in feature layer and one who uses feature layer out side of VS host need an implementation.

added RemoteWorkspace
- RemoteWorkspace has host agnostic implementation of roslyn features/services/workspace that will run in remote host

added service hub component and setup project for service hub
- service hub component is basically thin layer that deals with converting data to pass in to RemoteWorkspace

made devdiv insertion tool to ignore servicehub related files

support byte and char array natively in ObjectReader/Writer

service hub component is basically thin layer that deals with converting data to pass in to RemoteWorkspace

This reverts commit f88047f5, reversing
changes made to b9438f7c.

Now that the telemetry API is consumable from OSS and the code is there, no
need to have a dedicated binary + vsix for it.

We need to consume the VSSDK nugets for these assemblies in order to
build/run on a machine without VS 2015.

Batch sign tool for speeding up our signed build time.

* Comments on perf test

* address feedback

* fixed spacing issues

* add flag for specifying trace upload location

* start porting the command line parser

* finish mono option parsing

* switch to project.json

* stash

* added project.json

* disable signing

* Add projects for the runner and utilities

* added benview uploader

* added trace-file backup

* remove old scripts and tools

* Misc fixes

* Added a test-this-please jenkins job

This code has been moved to http://dotnet/roslyn-project-system

* Create vsix that contains all roslyn dependencies

To prevent projects across the tree from having different dependencies, we unify
external package dependencies by creating empty C# projects that represent them.
We then make use of project.json package inheritance (where a project inherits
all packages dependencies from their dependencies) to unify it across the tree.

No projects outside of this tree, should be directly referencing versions of
these dependencies manually.

For this check-in I've tackled Metadata, Reflection, and DiaSymReader. Will tackle
the rest in future commits.

What's been done:
- All the RTM references have not been changed
- All the prerelease refs have been bumped
- All the projects with prerelease refs have been
  changed to use netstandard1.3 instead of dotnet5.4
- Crossgen has been updated to point to the new CLR directory
- The NuSpecs have been updated to use the new refs

There is also now a stand-alone project for referencing
CoreCLR that can be updated independently of corefx. It will
need to be added to the closed solution before the refs in
the existing projects can be removed.