I have a problem with views not being found. Let me describe my setup. In my main mvc site, I load an external assembly using Activator.CreateInstance. I also have a virutal directory at /Views/CustomViews. In my main mvc site, I tell the external assembly to render itself, the path of the view it uses is such "~/Views/CustomViews/Index.aspx", however it is not found! If I switch it to use a view that is a physical file like "~/Views/PhysicalView.aspx", then it works.
I thought it was that mvc can't use virutal directories to find views, however I set up a test site where I reference a path to a view in a virutal directory BUT from assembly initialized from a referenced project and not activated dynamically and it works.
Could this be a security permission or some kind of app path of the loaded assembly that it can't find the virutal directory? Anybody have similar issues or something like this? Any help is appreciated...
View Complete Post