Deploying a Web Application

Posted on
Like what you see? Share it.Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone

70-305 – Developing and Implementing Web Applications with Microsoft Visual Basic .NET and Microsoft Visual Studio .NET

 

Objective: Deploying a Web Application
SubObjective: Plan the deployment of a Web application.

 

Item Number: 70-305.5.1.2
Single Answer, Multiple Choice

 

You have completed an ASP.NET application for an automobile manufacturer. The application will be used to track work on various assembly lines throughout the plant. Your application uses a component that was previously developed and deployed as an .msm by another member of the development team and one new component that you have created. Both components are either used in other ASP.NET applications or will be in the future.

 

How should you create the deployment package?

 

 

  1. Create a Setup project for your application and add the merge modules for all needed components to the project.
  2. Create a merge module for your new component and a Setup project for your application. Include the .msm files for both components in your Setup project.
  3. Create a merge module for your new component and a Web Setup project for your application. Include the .msm files for both components in your Web Setup project.
  4. Create two merge modules, one for your new component and one for your application. Create a Web Setup project. Include the .msm files for both components and your application in your Web Setup project.

 

Answer:
C. Create a merge module for your new component and a Web Setup project for your application. Include the .msm files for both components in your Web Setup project.

 

Tutorial:
You should create a merge module for your new component and a Web Setup project for your application. Then, include the .msm files for both components in your Web Setup project. A Merge Module project is a project that is used for components that will be shared among different applications. The Merge Module has an .msm file extension. This .msm file can be included in other deployment projects. In this scenario, you already have a merge module created for one of the components. You only need to create an additional merge module for your new component. Then, you can create a Web Setup project for your application and include both of the merge module files.

 

You should not create a Setup project for your application and add the merge modules for all needed components to the project. First, a Setup project is used to create a deployment for a Windows-based application. In addition, you only have one merge module created, so even if the option had specified the correct deployment project type, this solution still would not be complete.

 

You should not create a merge module for your new component and a Setup project for your application and then include the .msm files for both components in your Setup project. Again, a Setup project is used for Windows-based applications. You should use a Web Setup project instead.

 

You should not create two merge modules, one for your new component and one for your application, create a Web Setup project, and include the .msm files for both components and your application in your Web Setup project. You should not create a merge module for the application. Merge Module projects are used for components that need to be shared between applications.

 

Reference:
1. MSDN Library Visual Studio .NET – Search
– Visual Studio – Adding Merge Modules to a Deployment Project

Like what you see? Share it.Share on Google+Share on LinkedInShare on FacebookShare on RedditTweet about this on TwitterEmail this to someone
cmadmin

ABOUT THE AUTHOR

Posted in Archive|

Comment: