Geek asks and answers

Deploy MVC 3 When MVC3 is not installed - avoid deploying bin for each new site

I am using a hosting provider that does not have asp.net mvc3 installed. When deploying my applications, I always do bin deployments for the required dll library:

Microsoft.Web.Infrastructure
System.Web.Helpers
System.Web.Mvc
System.Web.Razor
System.Web.WebPages
System.Web.WebPages.Deployment
System.Web.WebPages.Razor

My question is: can I place these dlls somewhere in my shared hosting space, so that my deployed applications look for them there? So I could avoid finding them and ftp'ing them every time I deploy a new MVC3 application?

Just add a little more description. My general provider allowed me to configure applications in my root directory. So I thought I had the following structure:

root / bin / (here would be a dll above)

root/MyApp - - dll bin . ?

+3
1

ILMerge DLL.

http://research.microsoft.com/en-us/people/mbarnett/ILMerge.aspx

DLL , .

http://blogs.msdn.com/b/microsoft_press/archive/2010/02/03/jeffrey-richter-excerpt-2-from-clr-via-c-third-edition.aspx

dll , .

:

AppDomain.CurrentDomain.AssemblyResolve += (sender, args) => {

      String pathname = "Your path/" + new AssemblyName(args.Name).Name + ".dll";
      var assemblyData = System.IO.File.ReadAllBytes(pathname);
      return Assembly.Load(assemblyData);
   }

};
+1

More articles:


All Articles