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

Microsoft.Practices.Unity 3.5.0.0 or 4.0.1? #229

Closed
RafaelPlantard opened this issue Oct 15, 2015 · 4 comments
Closed

Microsoft.Practices.Unity 3.5.0.0 or 4.0.1? #229

RafaelPlantard opened this issue Oct 15, 2015 · 4 comments

Comments

@RafaelPlantard
Copy link

Severity Code Description Project File Line
Error CS0012 The type 'IUnityContainer' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.Practices.Unity, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. MagicBox.TrackerIn D:\Dropbox\Center\Projects\MagicBox.TrackerIn\MagicBox.TrackerIn\App.xaml.cs 55

When I use the Unity 3.5.0.0 or pre-release, the following code works

Container.RegisterInstance<IResourceLoader>(new ResourceLoaderAdapter(new ResourceLoader()));

But when I upgrade my unity version does not works more.

@brianlagunas
Copy link
Member

Based on your error, I think you are talking about UWP. We had this same issues when testing. We had to delete our output bins, and our nugget cache to get this to work. It seems VS2015 and NuGet don't play well with UWP yet. The nuget cache will be under C;\Users\UserName.nugget.

Let me know if that works.

@RafaelPlantard
Copy link
Author

I realize this right now.
Thanks @brianlagunas
I will try out it.

@brianlagunas
Copy link
Member

I just created a new app, brought in the packages, and it worked. So yeah, it has to be related to how VS upgrades UWP apps. Let me know if you are still having issues.

@lock
Copy link

lock bot commented Feb 1, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants