Unity unitybootstrapper issue

Question

0.00/5 (No votes)

See more:

I’ve upgraded my project today to Prism 7.0.0 and Unity 6.3. Before that, I had Prism 5 and Unity 4.

Now I’m running into problems with the Prism.Unity.UnityBootstrapper: it seems that the Container field is still a Microsoft.Practices.Unity.IUnityContainer instead of Unity.IUnityContainer.

I had hoped that the upgrade would cleanly cut all references to Microsoft.Practices.Unity off of my project, but it seems that I’m still forced to use the “old” Prism library, at least in parts.

Why does this situation arise, and what do I do to make it right? Am I missing something?

What I have tried:

Investigated the references and tried to rebuild after cleanup of the solution.

Posted 14-Aug-18 8:10am

bluecomb

Updated 14-Aug-18 21:08pm

Add a Solution

Comments

PureNsanity 15-Aug-18 10:52am

I understand this may not be possible; however, have you thought of upgrading the container? While I do still view Unity as valuable, it's a much older container implementation. Although I'm personally partial to MEF, Autofac is widely popular and also has Prism extensions. Autofac as a container also has many improvements and features over Unity... Just a thought....

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Answer 1 · 2018-08-14T21:08:00

Have you checked to make sure your using statements are not still referencing Microsoft.Practices.Unity? The upgrade process doesn't rewrite code for you so you're going to have to replace those entries yourself. It could be just as simple as doing a global search and replace to replace Microsoft.Practices.Unity with Unity.