Module path and environment variable

Jun 3, 2010 at 7:30 PM
It looks like when you put environment variable in the module path Unity fails to load the module. e.g %systemroot%\module\testmodule.dll Also if you specify a relative path and run the application in restricted user account, unity fail to find the module unless you specify full path for the dll. Any suggestions?
Jun 3, 2010 at 10:19 PM

Umm, put the environment variable where exactly? Where is this module path? In the config file?

Unity doesn't load anything - it just calls Type.GetType(). It's the CLR's responsibility to actually find the assembly and load it, and I know it doesn't expand environment variables. Also, there's rules that the CLR enforces for where it will look for assemblies (look for "probing path" on MSDN).

Hope this helps,



Jun 4, 2010 at 8:25 PM

Thanks for clearing that out. I was under impression that unity was responsible for it.

I'll look in to "probing path".