ResetInteractive base class is not coupled to VS and therefore is much easier to test.

now we will show <Unknown> for such project.

now, we will automatically re-enable full solution analysis (if user didn't explicitly disabled it) when new solution is opened.

user can either explicitly turn it back on or re-start VS to re-enable the full solution analysis.

By design, dependencies of analyzers must be specified explicitly to ensure that builds are consistent. However, this is surprising and the warning that is generated when a dependency is missing does not give any hints as to how the problem might be solved. I updated the warning to clearly explain what must be done to resolve it.

Old warning: "Analyzer assembly '{0}' depends on '{1}' but it was not found. Analyzers may not run correctly."
New warning: "Analyzer assembly '{0}' depends on '{1}' but it was not found. Analyzers may not run correctly unless the missing assembly is added as an analyzer reference as well."

Fixes #4057

Add support for adding/removing suppressions for diagnostics with no source location. Additionally,  when the diagnostics being suppressed or unsuppressed are across different languages, instead of showing a preview changes dialog per-language, we now show a single preview changes dialog for the entire changed solution.

This change enables "Remove Suppression(s)" context menu command in the error list to enable bulk selecting suppressed issues and removing the suppressions on them.

1. Add IVisualStudioDiagnosticListSuppressionStateService to maintain information about the suppression state of specific set of items in the error list. This service will be used by error list context menu command handlers to query available commands and also used by the fix service.

2. Add IVisualStudioSuppressionFixService to allow adding or removing bulk suppressions (in source or suppressions file), optionally filtered to a specific project. This command will be used by all baselining scenarios to compute diagnostics and apply bulk suppressions fix.

3. Add a SuppressionStateEventProcessor to process selection changed events in the error list and update the suppression state service information.

Fixes #3805 and #2990

now user has a easy way to see just errors from build. the content should be exactly same as what output build window shows.

this change set also includes several misc changes such as adding support for error source and build tool.

This commit updates the `AnalyzerDependencyChecker` type to reflect the
recent changes to require all analyzers and dependencies to be
specified, and the changes in how we load analyzer assemblies.

Now that we require all analyzers and dependencies to be specified, we
no longer look next to the specified analyzers to optimistically locate
dependencies. Instead, we only consider the list of passed-in analyzers
*plus* the assemblies already loaded into the `AppDomain`. The latter
avoids unhelpful warnings in the event that the analyzer assembly
includes a code fix that take a dependency on a Visual Studio assembly,
which of course can't be included in the list of analyzers. We now
create a warning when we identify a missing dependency.

We now also check analyzers themselves for conflicts (i.e., assemblies
at different paths with the same identity but different contents)
instead of just their dependencies.

The RoslynPackage type originally lived in a seperate assembly than
Microsoft.VisualStudio.LanguageServices when it was important for us
to be able to support the core parts of Roslyn being installed atop
the existing Visual Studio 2013 language services. This is no longer
a supported scenario anywhere, so we should just get rid of the
assembly.

Doing this is easy, it's just a matter of moving the files and related
assets to the LanguageServices assembly. A MEF interface is added
to prevent a circularity around triggering a load of stuff in the
SolutionExplorerShim. That could be delt with later by moving the core
of that code back to LanguageServices, but I don't want to touch that
now since it's very sensitive.

Fixes internal TFS bug 1043580.

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.

This reverts commit 3971cbc4.

small changes

    - Adding code refactoring tests
    - Using the error logger for cases where there is not UI to show the user
    - Made sure the cookie registered with the IDE gets unregistered on close
    - Responding to general fixup comments

Updating the extension manager to report code-fix exceptions to the user. In Visual Studio this will cause an infobar to appear giving the user the option to either re-enable the crashing code-fix or re-enable it and ignore future crashes for that session of Visual Studio.

Updating the extension manager to report code-fix exceptions to the user. In Visual Studio this will cause an infobar to appear giving the user the option to either re-enable the crashing code-fix or re-enable it and ignore future crashes for that session of Visual Studio.

Fixes internal issue #1138943.

In the SymbolFinder API, references to constructors are included as references to both the constructor method symbol and the related type symbol. Because reference locations are deduplicated across all results shown in Find References, we have to decide which definition node to use as the parent. Prior to this change the first related definition returned to us by the SymbolFinder won, but this ordering was not guaranteed to be consistent. This change introduces a precedence ordering for definitions returned by the SymbolFinder that currently guarantees that members will be preferred over types.

Additionally, this change removes the requirement that definitions shown in Find References have distinct locations. This allows us to meaningfully separate references between a type and its default constructor which has the same location.

In this initial implementation, find references results are now grouped by the definition that they directly reference.

For symbols defined in metadata, we previously showed the references without showing the definition itself. We now show the metadata definition as well.

Consider what happens if you have two analyzers, A and B, that each depend on an assembly named C.

  Directory 1:
    A.dll
    C.dll

  Directory 2:
    B.dll
    C.dll

If both copies of C have the same identity (name, version, culture, public key token, etc.) then only one of them is actually going to be loaded into VS. If both copies are identical then it doesn't matter, but if their contents differ the analyzers may not work the way they are supposed to or may fail outright.

Here we attempt to let the user know that this might happen. Whenever an analyzer is added or removed we identify the transitive set of assemblies the analyzers' may load and identify assemblies that have the same identity. We then hash the file contents of these assemblies and compare. If they are different we surface a conflict in the Error List.

In solutions with many different analyzers or dependencies this is a potentially expensive operation. To limit the impact on the system we only allow one of these operations to run at a time. If an analyzer is added or removed while a check is in progress we immediately signal for cancellation, wait for the existing task to finish up, and only then start the new one. (changeset 1411056)

1. Stop displaying superfluous 'No Preview' under the header section of the preview pane for fixes such as 'rename tracking' and 'generate type dialog' that don't provide any visual preview.

2. Make preview pane header font use the VS 'Environment' font settings so that user can change /scale the font.

3. We were not displaying the preview header in the case of hidden diagnostics (which don't show up in the error list) - start displaying the header for hidden diagnostics (except if the diagnostic is a 'trigger' diagnostic).

4. Disable tab stop / focus in the code diff view portion of the preview pane. When using keyboard, we were allowing user to stop in the diff view portion - this ended up causing confusion since we would display a blinking cursor in the code diff view portion giving users the impression that they could type something there.

5. Set Focusable=true on the preview pane control. Light bulb checks for this before shifting keyboard focus to the preview pane in the case where there are no 'flavored' actions under the preview pane (such as 'Preview Changes' and 'Fix All Occurrences'). (changeset 1410707)