How to reference to assembly in mvc at runtime?

Question

1.00/5 (1 vote)

See more:

In my Asp.Net MVC application, i have some view file (.cshtml) which has reference to an external library which it will be loaded at runtime. so after app started, i load the assembly by Assembly.Load and i register the controllers by my own custom ControllerFactory and every thing is ok.

But, in some views which has references to the dynamically loaded assembly, throws the :

Compiler Error Message: CS0234: The type or namespace name 'MyDynamicNamespace' does not exist in the namespace 'MyApp' (are you missing an assembly reference?)
exception that tells the razor compiler cannot resolve the related assembly.

My question is that, is there a way to register the assembly at runtime, to able the razor compiler can access to it and resolve it?

Notice that i can't use BuildManager.AddReferencedAssembly method because my assembly have to be loaded after app start, and the BuildManager does not support it.

Posted 3-Jul-15 10:52am

farhad.bagherlo

Add a Solution

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-07-03T16:42:00

It's not that there is no a "way"; there is no such concept as "register the assembly at runtime". The assembly is not "registered", it is referenced, and the result of referencing goes to compilation.

I have no idea why did you decide "assembly have to be loaded after app start". Most likely, this is just you fantasy, but if you explain it, I'm ready to discuss it. Again, "the BuildManager does not support it" is a totally wrong idea. There is nothing to "support"; the whole concept does not exist, or, more exactly, this is a misconception.

During runtime, you can load any compatible assembly. To understand how it works, please read the documentation on System.Reflection.Assembly:
https://msdn.microsoft.com/en-us/library/system.reflection.assembly%28v=vs.110%29.aspx[^].

Pay attention for all the Assembly.*Load* methods.

However, when you load the assembly, what you are going to do with it? In all cases, you would need to further use reflection. I could explain it if I knew your purpose. To get basic idea, you can see my past answers:
Dynamically Load User Controls[^],
C# Reflection InvokeMember on existing instance[^],
Gathering types from assemblies by it's string representation[^],
Access a custom object that resides in plug in dll[^].

—SA