Update NuGet EF Package to 6.0.0-Beta1: Bugreport
Use object initializer
Enable test that JSON serialize error is logged
Add failing ReferenceLoop tests
Upgrade to Json.NET 5.0.6

Note that this version of Json.NET does ship with a net45 version,
but it causes problems with ILMerge. Resolved by referencing net40.

See #451 for discussion.
Set Json.NET ReferenceLoopHandling = Ignore
Remove client source from .net server
Merge pull request #451 from dahlbyk/ReferenceLoop

Reference loop => JSON.NET 5.0.6
Fixed Issue #407 - Prevented EF upgrading the databases
Proposed change to fix Issue 491.
Changed to point to http://getglimpse.com/Help/Troubleshooting instead of the IIS website, as requested.
Fixed typo in constant name.
Changed references towards glimpse.js

After removing the Glimpse.Javascript project, the solution failed to
build due to bad referenes to a glimpse.js file
Add catch for #453. Needs testing once build is working again.
Merge pull request #494 from Glimpse/MakeSolutionBuildAgain

Changed references towards glimpse.js to make solution build again
Made Glimpse NuGet package discovery more stable

When there are assemblies in the application's run directory that give
an exception when requesting custom attributes, the whole glimpse.axd
page crashed. This fix will list those "bad" assemblies and prevent the
glimpse.axd from crashing
Renamed NuGet package discovery classes

Since they are not Glimpse specific but are actually intended to
discover NuGet packages. The idea is to have the NuGetPackageAttribute
moved to NuGet eventually.
Aligned NuGetPackageAttribute values

- An explicit value of Glimpse for the Core projecten (otherwise we
would get Glimpse.Core as package name)
- An explicit value for the "normal/base" projects
- No value (so that it will be determined based on the assembly at
runtime) for the .NET framework version specific projects
Preload assemblies during Glimpse Runtime startup
Handle error BuildManager.GetReferencedAssemblies

Unittests fail on the call to BuildManager.GetReferencedAssemblies,
since the BuildManager is supposed to run in the context of an ASP.NET
runtime. So a try catch has been added to logs succes or failure of the
called method.