Nuget package depending on older version of other nuget package.

Tormod

LINQPad crashed. I wanted to add this message to the crash report, but pressed the "submit" a bit fast.

When I start a new query and attempt to add Nuget dependency to RazorEngine, it fails. Googling the error message (could not find RazorEngine compatible with Asp.Net3) turns up posts saying that this was resolved by updating the nuget package manager.

If I attempt to add dependency to version 3.5.3 of RazorEngine (not latest 3.6.0), then LINQPad crashes (null reference exception).

JoeAlbahari

The RazorEngine NuGet package includes a repeated reference to Microsoft.AspNet.Razor, once for Framework 4.0 and again for Framework 4.5. This appears to be upsetting NuGet.Core, which LINQPad uses to download NuGet packages.

The current LINQPad beta uses the latest version of NuGet.Core.dll (2.8.3), and it appears the problem still exists in this library. You can verify this running the following query in LINQPad, after adding a NuGet reference to NuGet.Core:

var repo = PackageRepositoryFactory.Default.CreateRepository ("https://nuget.org/api/v2" ) ;
var packageManager = new PackageManager (repo, @"c:\temp\");
packageManager.InstallPackage ("RazorEngine");   // throws exception

FWIW, this isn't a problem with the newer RazorEngine NuGet package which is in prerelease.

JoeAlbahari

FWIW, I've found a workaround, so this should be fixed for the next beta.

Tormod

Nice work. My "workaround" was to use visual studio to get the package and then do a normal browse for it. I will be reverting back to a NuGet reference when the fix is out.

Nitancy

What version of LINqPad incorporates this fix?

brendandixon

Hmm, I am completely unable to add a RazorEngine reference (for 3.7.0 -- it complains about the dependency on Microsoft.AspNet.Razor). However, the same works fine under VS...

JoeAlbahari

The latest beta can download RazorEngine.

http://www.linqpad.net/Download.aspx