added better handle for anonymous method expression in formatting.

it contiains two changes

1. made anonymous method expression to be handled same as lambda expression

2. made formatting engine to handle new option added for lambda expression to be handled properly in other places. (changeset 1234191)
Add the (already existing) visualizer projects to roslyn.sln

CR: VSadov; GNamboo (changeset 1234211)
Make our use of DebuggerDisplayAttribute more consistent (changeset 1234216)
Move linked file tracking from the Workspace into the Solution and other small linked file bug fixes. (changeset 1234227)
added formatting rule for member acessor syntax "."

simple vb formatting bug fix around "." (changeset 1234325)
SemanticModel.LookupSymbols should return extern aliases (internal version already does).

CR: tomat (changeset 1234383)
fixed two bugs

1. removed automatic string literal fix up in VB.
    with new multiline string literal supports in VB, this fix up doesn't provide any meaningful help to user anymore. most likely it will always put " at the end of file most of time.

2. fixed vb formatting around xml member accessor .
 (changeset 1234391)
Fixing a typo. (changeset 1234665)
Fix DiagnosticAnalyzer project GUIDs and add missing build configurations for the Visualizer projects. (changeset 1234903)
Comment out not used error code, and remove the corresponding resource strings (changeset 1234955)
made AdjustNewLinesOption to use same name pattern as AdjustSpacesOption in formatting options (changeset 1235061)
Modify test case to acknowledge actual behavior (changeset 1235084)
DependentProject equality

DependentProject should override Equals and GetHashCode and should be IEquatable since it's used in a HashSet

Fixes #87 (changeset 1235229)
667303-allow enum underlying type to be spelled out (changeset 1235281)
Fix typos (changeset 1235318)
Reduce the size of GetSimpleBuiltInOperators for both Unary and Binary operator kinds.
These showed up as very large ngen'd methods. Use array literal initialization to reduce the code size. (changeset 1235371)
MethodCompiler refactorings:
     - We mix "CompilerGenerated" and "Synthesized", but they mean the same - renames the former to the latter. The latter is less ambiguous since we also name "generated" the result of CodeGen phase.
     - Merges Compiler.cs into MethodCompiler.cs, CSharpCompilation.cs and Binder_Initializers.cs -- to match VB.
     - Renames misc members/types so that those that serve the same purpose in C# and VB are called the same. (changeset 1235392)
deterministic compiling

We make the compilers (both C# and VB) deterministic (identical inputs cause identical outputs). In theory this may make distributed and incremental builds much easier to implement. It will also allow one to determine easily if any API has changed or not by simply generating a reference assembly and checking if it is identical to the previous one.

Two things needed to change:
(1) The timestamp in the header is replaced with 0 (which is specifically allowed by the spec)
(2) The module version ID Guid (Mvid) is computed by hashing the contents of the generated assembly (with zero
      where the Mvid will go for the purposes of computing the hash)

The name of the "private implementation details" class no longer includes the Mvid.

In order to simplify things, I removed the parameter from a few emit APIs where the caller provides the Guid for the Mvid. It turns out that nobody nowhere used it. So when emitting in the normal way, we don't know the Mvid ahead of time. For edit-and-continue, however, we always reuse the Mvid for the original assembly as before.

I implemented this assuming that everyone wants this new behavior. Some may worry that perhaps some unknown tool depends on the presence of the timestamp. I'd prefer to push it this way and see if anything breaks, because it will be simpler for it to just always work this way rather than having an option to turn it on and off. Also, I look forward to seeing if there is any performance impact due to running SHA1 over the whole in-memory stream. I suspect it will be unmeasurably small.

By the way, strong name signing happens after this is done, so there is no need to worry that a signature will introduce nondeterminism in the mvid. The strong name signature includes mvid in the data it signs. See Compilation.SerializeToPeStream to see the sequence. (changeset 1235486)
more clean up on lambda formatting/smart indentation behavior.

now it should behave a bit better than before while typing. (changeset 1235522)
Adds a failing EnC test. (changeset 1236309)