Webdeploymentsetup vs 2010

Combining them makes database joins between them easier. If you're deploying to a third-party hosting provider, your hosting plan might also give you a reason to combine them. For example, the provider might charge more for multiple databases or might not even allow more than one database. In this tutorial, you'll deploy to two databases in the test environment and to one database in the staging and production environments.

When the application runs in IIS on your development computer, the application uses the default application pool's credentials to access the database. However, by default, the application pool doesn't have permission to open the databases.

This means you need to run a script to grant that permission. In this section, you'll create that script and run it later to make sure that the application can open the databases when it runs in IIS.

In a text editor, copy the following SQL commands into a new file and save it as Grant. In Visual Studio, open the Contoso University solution. Right-click the solution not one of the projects , and select Add. Select Existing Item , browse to Grant. If you're using a different version of SQL Server or Windows, or if you set up IIS on your computer differently, changes to this script might be required.

In some scenarios, you might want to specify a user that has full database schema update permissions only for deployment and specify for run time a different user that has permissions only to read and write data.

For more information, see Reviewing the Automatic Web. You can configure the publish profile to run the grant script in the membership database during deployment because that database deployment uses the dbDacFx provider. You can't run scripts during Code First Migrations deployment, which is how you're deploying the application database. This means you have to manually run the script before deployment in the application database. In the Connect to Server dialog box, enter. Select Connect.

In the database drop-down list select ContosoUniversity. Select Execute. The default application pool identity now has sufficient permissions in the application database for Code First Migrations to create the database tables when the application runs.

The process you went through in the previous tutorials to set up Visual Studio to automate deployment tasks applies to all of these methods. In these tutorials, you'll use the first two methods. For information about using deployment packages, see Deploying a web application by creating and installing a web deployment package in the Web Deployment Content Map for Visual Studio and ASP. Before publishing, make sure that you're running Visual Studio in administrator mode.

If you don't see Administrator in the title bar, close Visual Studio. Administrator mode is only required for publishing when you're publishing to IIS on the local computer. DAL project. Select Publish. The Publish page appears. Select New Profile. The Pick a publish target dialog box appears. Select Create Profile.

The Publish wizard appears. The Destination URL setting isn't required. When Visual Studio finishes deploying the application, it automatically opens your default browser to this URL. If you don't want the browser to open automatically after deployment, leave this box blank. Select Validate Connection to verify that the settings are correct and you can connect to IIS on the local computer.

The Configuration drop-down box specifies the build configuration to deploy. Leave it set to the default value of Release. You won't be deploying Debug builds in this tutorial. Expand File Publish Options.

In the test environment, the application accesses the databases that you created in the local SQL Server Express instance, not the. Leave the Precompile during publishing and Remove additional files at destination check boxes cleared. Precompiling is an option that is useful mainly for large sites.

It can reduce startup time the first time a page is requested after the site is published. You don't need to remove additional files since this is your first deployment and there won't be any files in the destination folder yet.

If you select Remove additional files at destination for a subsequent deployment to the same site, make sure that you use the preview feature so that you see in advance which files will be deleted before you deploy. The expected behavior is that Web Deploy will delete files on the destination server that you have deleted in your project. However, the entire folder structure under the source and destination folders is compared; and in some scenarios, Web Deploy might delete files you don't want to delete.

For example if you have a web application in a subfolder on the server when you deploy a project to the root folder, the subfolder will be deleted. You might have one project for the main site at contoso. The blog application is in a subfolder. If you select Remove additional files at destination when you deploy the main site, the blog application will be deleted.

Updates In this window, you should define how your application should be updated. Check 'The application should check for updates' and choose whether it should be updated before or after the application starts. If you choose to update it after running the application then you can mention whether you want to check each time it runs or can mention a time period, that it should check.

But it is always advisable to check before application starts, so users will get the latest updates each time they run the application. And specify a minimum required version, so that the end user will get the specified version of the application, if they have an older version installed on their PC. If the updating location is other than the publish location then please provide the path.

Save the settings and go to the form designer and add a label to the form. Save and go to "Build"??? If you wish make any changes to the publish settings that you completed earlier then click "Next" or click on the "Finish" button. Click "Next". And the deployment setup will be created in the published path. Run the setup.

And click on the "Install" button. Now close the application and change the label to 'Version 1. And go to publish settings and on the update window, change the minimum required version to 1. Click "Ok" and save the settings and publish the application.

There will be a start menu shortcut from the first installation. After you configure the Settings tab, click Publish to create the package at the path you specified on the Connection tab.

The wizard advances to the Preview tab if you click Next on the Settings tab, but previews are not provided for deployment packages. In addition to the. This is a helper command-line batch file that invokes Web Deploy in order to install the application on the destination server locally or remotely. This file contains parameters that are passed to Web Deploy on the destination server.

By default, this file contains the values that are specified during the packaging process. If you want to install the application on multiple servers with different settings for each server, you can modify the parameter values in this file each time that you install the package by using the projectname.

This file contains settings that Visual Studio used to create the deployment package. This file is only used to create the package. It is not used when the package is installed on the destination server. In order to install a package, Web Deploy must be installed on the destination server. In addition, the version of Web Deploy on the destination server must be compatible with the version on the development computer.

By default, Web Deploy is installed on the development computer when you install Visual Studio. IIS 7 must be installed on the destination server, and the package must be created as a.