Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't update to beta-004 #35

Closed
marcpiechura opened this issue Apr 22, 2015 · 6 comments
Closed

Can't update to beta-004 #35

marcpiechura opened this issue Apr 22, 2015 · 6 comments

Comments

@marcpiechura
Copy link
Contributor

Hi, i wanted to upgrade to beta-004 but reciving a strange error message from nuget.
Upgrade to beta-002 is working fine, so I found a difference between the two versions.
In beta-004
image
In beta-002
image

Is this correct, the "Unsupported, Version=0.0" ?

I don't know if it's helpfull but here is the nuget error
image

System.InvalidOperationException: Failed to add reference to 'System.Runtime'. Please make sure that it is in the Global Assembly Cache. ---> System.Runtime.InteropServices.COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.
at VSLangProj.References.Add(String bstrPath)
at NuGet.PackageManagement.VisualStudio.VSMSBuildNuGetProjectSystem.AddGacReference(String name)
at NuGet.PackageManagement.VisualStudio.VSMSBuildNuGetProjectSystem.AddFrameworkReference(String name)
--- End of inner exception stack trace ---
at NuGet.PackageManagement.NuGetPackageManager.d__d2.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.PackageManagement.UI.UIActionEngine.d__1b.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at NuGet.PackageManagement.UI.UIActionEngine.d__0.MoveNext()

@jbogard
Copy link
Owner

jbogard commented Apr 23, 2015

What NuGet version are you using?

@jbogard
Copy link
Owner

jbogard commented Apr 23, 2015

I think you might need to upgrade to NuGet 2.8.5 http://blog.nuget.org/20150331/nuget-2.8.5.html

@tawman
Copy link

tawman commented May 7, 2015

FWIW, I installed MediatR 2.0.0-beta-004 via package manager console in VS 2013 yesterday without issue into new solution.

C:\Program Files (x86)\Microsoft Visual Studio 12.0>nuget
NuGet Version: 2.8.50506.491

@marcpiechura
Copy link
Contributor Author

Sorry, totally missed this issue,I will try it again tomorrow or next week.
Was VS 2015 CTP 6, maybe it's fixed in the RC.

@marcpiechura
Copy link
Contributor Author

Isn't working in the RC with Nuget 3..
But as @tawman mentioned, it's a nuget error and not related to MediatR so forget about it ;-)

@eddiegroves
Copy link

I noticed that the reason 004 installs in VS2013 and doesn't get the same error as in VS2015 is that NuGet 2.8 is pulling 'Facade references' for System.Runtime, System.Threading.Tasks, System.Linq and System.Collections. Since these DLLs are GAC'd for 4.5.1 I believe it's safe to then remove the facade references from the project. Interesting behaviour...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants