we will move away from IVsHierarchy and start to use ProjectIdGuid instead.

This ensures that the url displayed in the tooltip is more human readable.

added explict DocumentCloseAsync to incrementalAnalyzer so that re-analysis and close action have different behavior.

outcome of this change is that, when a user close a document without saving, diagnostics will be cleared as expected.

We decided that the current design of this feature would not add much to
the user experience, so we're backing out the parts that have been
committed already. Nothing is using these pieces, so this should even
impact any tests.

* Rename RQNameService to RQName and make public.
* Rename TryBuildForPublicApi to From and have it return null.
* Remove TryBuild, since we *only* build RQNames for public Api's now.
* Clean up implementation to not pass flag around for buildForPublicApi
* Remove RQDynamicType
* Create a singleton for System.Object.
* Add a comment explaining why we erase dynamic.

Fixes #55.

refactored esent code to support project k and save project name along with project path. this is slightly different than saving context but should fulfill the need.

Display a tooltip containing url destination for hyperlinks in the error list and light bulb preview pane UIs.

Also use full fidelity (i.e. substituted)  error message in the search query in the case of hyperlinks that redirect to bing search so that we can present more relevant search results.

Expose overloads of Formatter.GetFormattedTextChanges that correspond to
the overloads of Formatter.Format.

Reduce both methods to a single internal implementation and remove
optional parameters from them.

Use SpecializedCollections.SingletonEnumerable when calling Format and
GetFormattedTextChanges.

Fixes #778.

Many entries come through Project.GetCompilationAsync, which immediately
turns around and gets the project again to call SupportsCompilation.
Provide an overload that just takes the project directly to skip the
GetProject call in the middle.

Fixes #1220.

Previously, we'd store a direct pointer to the IUnknown instance and
unwrap that in the MTA.  The IENCSymbolReaderProvider interface is
being changed to prevent calls from an STA by returning the IUnknown
instance directly, rather than a pointer to it.

Thus, we need to add a layer of indirection (marshal the IUnknown
in a Stream and pass a pointer to the Stream instance to the MTA).

Move the analyzer assembly loaders out of `CodeAnalysis.Desktop` and
into the individual host projects (csc. csi, vbc, vbi, etc.). This
solves two issues:

1. The loader types can now be made internal.
2. `CodeAnalysis.Desktop` no longer has a dependency on the loader
implementation, and the loaders can be swapped or modified on a per-host
basis as needed.

Fixes internal bugs 991517 and 1142701

Commit rename on the following commands:

- Cut/Paste, if the operation occurs outside a rename span
- MoveSelectedLines
- Command-based refactorings (Change Signature, Extract Interface, and
Encapsulate Field)

made preview dialog window to use a bit more expansive diff mode if it has fewer diff than compiler diff result.

- Fixes #496, an error when finding reference on namespaces defined in
metadata
- Groups all namespace definitions & references under a single node,
which itself is non-navigable. Prior to this change, there would be lots
of top-level nodes for the same namespace with 0 references.

The only remaining uses were in tests for this type.

The `AnalyzerFileWatcherService` currently depends on the
`InMemoryAssemblyProvider` to tell it when it when an analyzer assembly
has been loaded so that it can watch for changes to the file on disk.
Instead, we can get this information directly from the language service.

This change also removes the code that tries to map from a dependency
back to some analyzer that directly or indirectly loaded it. In general
we can't rely on being able to create a chain back to an analyzer, and
it shouldn't be as much of a problem now that we require dependencies to
be declared.

Also, when adding or removing analyzer dependencies we need to kick off
the dependency analysis just like we do with analyzers.

Fixes #1123

Update the ThemeColorFixer to trigger on IClassificationFormatMap.ClassificationFormatMappingChanged. This allows us to update the tooltip classifications when the user manually changes colors or imports color settings.

We previously listened for WM_SYSCOLORCHANGED and WM_THEMECHANGED, but those are now redundant and have been removed.

Currently we expect that an analyzer's dependencies are located next to
it in the file system, and we do not require that those dependencies be
explicitly passed to the compiler. These requirements are changing. We
will now allow analyzers and their dependencies to be located anywhere,
and this requires that the full set of analyzers and dependencies be
passed in so that we know where to find them.

In order to load analyzers and dependencies under these new
requirements, this commit introduces the SimpleAnalyzerAssemblyLoader.
This type loads assemblies with a simple `Assembly.LoadFrom`, but it
also hooks the `AppDomain.AssemblyResolve` event in order to find and
load items from its list of dependencies.

Csc.exe and vbc.exe have been updated to use this loader instead of
calling directly into `Assembly.LoadFrom`. It is also exposed to the
workspace layer through the IAnalyzerService type.

Upgrades System.Collections.Immutable to 1.1.34-rc and
System.Reflection.Metadata to 1.0.19-rc.

TryCombine should never throw exception.

First is cleanup some infobar code such as adding copyright header, adding internal, removing unused usings and etc.
Second is adding more info in exception log.
Last is making code action more resilient to null return value from user code.

Fix #1980 : CodeModel was not handling Conversion operator declarations
in few areas. This change addresses these issues

Fix #1923 AbstractCodeType should return only a namespace when asked for
a CodeNamespace but not a Type

now, error list will have column (which is off by default) that shows source of each errors in a
format "assembly name" for analyzers node. and "assembly name" [vsix name] for vsix