Our Recommendation

Monday, December 13, 2010

Deployable dependencies in Visual Studio 2010 beta SP1 (Weblogs @ ASP.NET)

A new feature that comes with Visual Studio 2010 beta SP1 is supported for deployment references. Reference deployment means that you can include all DLL - s to a deployment package to ensure that your application has all the assemblies that it must operate with it in the deployment package. In this posting I'll show you how to use the dependencies of deployment.

When I open my ASP.NET web application I have new option for reference when I right click on my web project: Add deployment Dependencies…

Visual Studio 2010 SP1 Beta: Add deployable dependencies

If you select it you'll see dialog where you can select the dependencies you want to add to your package project.

Visual Studio 2010 SP1 Beta: Select deployable dependencies

When the packets you need are selected click OK. Visual Studio adds the new folder to your project called _bin_DeployableAssemblies.

Visual Studio 2010 SP1 Beta: Deployable references for RazorScreenshot on the right shows the list assemblies added to the ASP.net pages and knife. All DLL - s required to run ASP.NET MVC 3 knife view engine are here. I don't know if NuGet.Core.dll is required in the production, but it is added, then let it be.

I tried to deploy my ASP.NET MVC project that uses the Windows azure knife after the addition of deployable references to my project.

Deployment went fine and the web role instance started without any problems. The only reference DLLs, that as local was the System.Web.mvc. All knife tricks came with deployable dependencies.

Visual Studio support deployable dependencies is great, because this way component providers can build definitions also components assemblies that are loaded dynamically executing will be in the deployment package.

No comments:

Post a Comment