ASP. NET MVC Deployment

GAC Catalog:

In the Run window, enter: C:\WINDOWS\assembly\GAC

NET 2.0,3.0 GAC:
c:\windows\assembly(32bit and 64bit?)

. NET 4.0 GAC
c:\windows\Microsoft.NET\assembly\GAC_32(32bit only)
c:\windows\Microsoft.NET\assembly\GAC_64(64bit only)
c:\windows\Microsoft.NET\assembly\GAC_MSIL(Any CPU)

In a local development environment, you can run programs that are deployed to the server that may not run for what reason.

At the time of development, the VS2010 will be installed locally. When you install VS2010, the. NET 4 is installed. If you develop MVC3, you will also install MVC3. This way, a MVC3 program works locally.

There are a few things you need to do to deploy to the server:

1. Install the. net4.0. In the case of a Win7 machine, only. NET 2.0 is the default. Need to install. NET 4.

2. Install the ASPNETMVC3.

When you install MVC3, some DLLs are installed in the GAC. This allows the local application to function properly. However, if you deploy to a server, MVC3 is not installed on the server. The GAC on the server has no MVC3-related DLLs. This will cause an error that the assembly could not be found. The workarounds are:

1. Install MVC3 on the server.

2. Copy the relevant DLL for MC3 to the bin directory of the site we deployed

3. In the project, set the properties of those MVC-related references to: [Copy to local]. This way, when packaged, these MVC-related DLLs in the GAC are copied to the bin directory of the Web site. This is deployed to the server, although the GAC does not have these MVC DLLs, but there is one in the bin directory. The app will work as expected.