We need to attach the same information to DkmEvaluationResults and
DkmEvaluationResultEnumContexts, but they have different lifetimes.  Enum
contexts, which are, in some sense, the children of evaluation results are
closed first.  As such we don't want to clean up our attached information
until the evaluation result is closed.  When we are informed that this has
happened (by a call to EvalResultDataItem.OnClose), we call Close on the
associated DkmClrValue.

We hope that actively managing the lifetime of DkmClrValue instances will
improve perf by reducing the amount of work that the debugger has to do on
each evaluation (which is proportional to the number of live
DkmClrValues).

Unfortunately, this will not improve perf in the large-array case because
DkmEvaluationResults are not closed as they are scrolled out of view.

Associated with DevDiv #1094428 (not yet on GitHub).

The DeclarePublicAPI draws attention to changes to the public API
surface area in order to prevent breaking changes and to encourage
careful design when adding new APIs. It requires that every project with
a public API capture the public types and members in a file called
PublicAPI.txt, and creates errors when this file does not match the
actual symbols in the project. This makes changes very obvious in code
reviews and source control history.

Currently PublicAPI.txt does not capture the return types of members
(field, properties, methods, and events) so these can changes without it
being caught by the tool. This changes updates the analyzer to include
the return type.

A nice feature of the associated code fix is that it sorts PublicAPI.txt
alphabetically, and since type names are fully qualified this naturally
groups together types in the same namespace, members in the same type,
overloads, etc. To preserve this property we put the return type at the
end of the line, after the type and member name.

while creating pull request, I left out this change

but continue to report the diagnostic if "strict" mode is requested.
Fixes #324

Construct EnumContextDataItems on demand.  Also, don't access their properties before checking for null.

these tests will be re-enabled once we patch build machine with new interfaces.

We need to attach the same information to DkmEvaluationResults and
DkmEvaluationResultEnumContexts, but they have different lifetimes.  Enum
contexts, which are, in some sense, the children of evaluation results are
closed first.  As such we don't want to clean up our attached information
until the evaluation result is closed.  When we are informed that this has
happened (by a call to EvalResultDataItem.OnClose), we call Close on the
associated DkmClrValue.

We hope that actively managing the lifetime of DkmClrValue instances will
improve perf by reducing the amount of work that the debugger has to do on
each evaluation (which is proportional to the number of live
DkmClrValues).

Unfortunately, this will not improve perf in the large-array case because
DkmEvaluationResults are not closed as they are scrolled out of view.

Associated with DevDiv #1094428 (not yet on GitHub).

It is likely the character was inserted by accident. There is no reason
to use it in the code. It is a valid Unicode whitespace, but not a valid
ASCII. Since the containing file has no encoding bytemarks, the behavior
of this char is dependent on default encoding. Indeed, the file compiles
on Windows and fails on Linux.
As far as I could find, this is the only case where this character is
used in actual code (not in tests) in Roslyn codebase.

NavigateTo doesn't support cancellation when computing the display properties so the cancellation token is getting removed rather than having to manually handling OperationCanceledException.

Ensure that FileKey's timestamp is Utc by adding a Debug.Assert
Use LastWriteTimeUtc in MetadataCache.

This change deletes code we use to determine if a rule set file is one
that shipped with VS, and thus cannot be modified or deleted. It was
largely copied from code in
Microsoft.VisualStudio.CodeAnalysis.Sdk.UI.dll, and we should just use
the original instead.

Fix #323 bug in SemanticModel.GetAwaitExpressionInfo when await expression used as an expression statement.

It looks like this got lost when the new open Roslyn.sln was created.

The BuildAndTest.proj was failing because a number of our suites aren't
correct when run in parallel.  Disabling them for now and letting #321
track reenabling them.

Disabling the HandleSolutionProjectTypeSolutionFolder test as it is
failing in Jenkins.  Filed issue #317 to track this test.

This makes the necessary changes to allow for Roslyn.sln to build from
the command line.

A bit of cleanup of assembly signing interop interfaces making the code portable. (changeset 1412135)

Fixes a crash while generating debug information for a compilation with two metadata references that represent the same assembly, first with no aliases and second with an alias.   (changeset 1412130)

There are cases where underlying platform does not provide signing services in the form that we consume. We need to be able to handle such cases gracefully without crashes.
***NO_CI***
 (changeset 1412127)

Avoid a couple of VB iterator allocations for emitting custom attributes and interfaces. Combined, this is 0.5% of allocations in the "Roslyn Full" build. (changeset 1412086)

1. Reduce allocations when reading from FileStream.
2. Pre-compute checksum if possible.
3. Reduce allocations for lazily computed checksums.
4. Avoid LOH allocations for large source text.
5. Update EditorTextFactory to optimize for reads from temporary storage

Perf results for the Picasso rebuild scenario:
184 MB total allocations saved. Including: 78 MB of char[], 73 MB of Byte[], 9 MB of string. Also, 35 MB of LOH allocations were eliminated.
 (changeset 1412085)

In a benchmark with 200,000 methods in a type, ChildThatContainsPosition was the clear bottleneck. For such cases, the syntax list is represented using a special type called WithLotsOfChildren (both VB and C# have this optimization) that has a constant-time implementation of GetSlotOffset. Given that, we can find the correct slot via binary search instead of a linear search.
With this change, the benchmark compilation went from 45 seconds to 25 seconds. (changeset 1412034)

CR: jasonmal;joshs;jaredpar;hechang (changeset 1412012)

Move Roslyn.DebuggerVisualizers to open. This project contains VS debugger visualizers of IL, PDB and metadata blobs helful for debugging Roslyn issues. (changeset 1411991)

Disable Microsoft.VisualStudio.LanguageServices.Implementation.EditAndContinue.VsENCRebuildableProjectImpl.TrackingSpansChanged(bool) pending perf investigation (issue #291). (changeset 1411936)

 (changeset 1411873)