• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
ASP.NET Web Site Deployment Instruction
 

ASP.NET Web Site Deployment Instruction

on

  • 1,873 views

This document describes the configuration of the automated deployment. For the automated deployment script, please refer to http://goo.gl/IGgIr

This document describes the configuration of the automated deployment. For the automated deployment script, please refer to http://goo.gl/IGgIr

Statistics

Views

Total Views
1,873
Views on SlideShare
1,872
Embed Views
1

Actions

Likes
0
Downloads
15
Comments
0

1 Embed 1

http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via SlideShare as Microsoft Word

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    ASP.NET Web Site Deployment Instruction ASP.NET Web Site Deployment Instruction Document Transcript

    • Web Site Deployment Instruction<br />Scope<br />This document describes the process, tools and configurations of Federated Database Console deployment. But it is not restricted to this project only. For automated deployment script please refer to http://www.cnblogs.com/misaxi/archive/2011/03/18/automated-deployment-for-websites-and-web-services.html<br />Deployment Process Overview<br />Project Configuration<br />Create New Configuration<br />Create QA1 and QA2 for deploying package to two application server. And this is also applied to following configurations.<br />Add Config Transforms<br />Execute the same action on FederatedDBService project.<br />Then, we will get a Web.QA.config for QA configuration we created previously.<br />Change DB Connection Strings<br />Specify connectionStrings In Web.QA.config for both Home and FederatedDBService projects. The configuration set here will replace the configuration in Web.config if the project has been built because the attribute specified is xdt:Transform="Replace". Basically, the only change is the value of Data Source of each connection string (e.g. Data Source=CNSHN13DB02VI01).<br />Configure Package/Publish Web<br />
      • Open properties window of website project
      • Configure parameters in the Package/Publish Web section as following
      • Home should be Default Web Site/FDB
      • FederatedDBService should be Default Web Site/FDBService
      Deployment<br />Before Deployment<br />
      • Install PowerShell 2.0 on target servers
      • Enable PowerShell remoting on target servers
      • Install MSDeploy 1.0 on target servers ( HYPERLINK "file:///Cnshn13db04vshare_sdcMike%20HeWebDeploy_x86_en-US.msi" MSDeploy 1.0 Installer x86)
      • Create folder, "C: FDB_DEPLOY", on target servers and share "FDB_DEPLOY" with writing permission
      Deployment<br />
      • Copy a new version of FDBDeploy.ps1 under $FederatedDBConsoleDeployment and edit its variables according to the environment.
      • Execute PowerShell script
      After Deployment<br />
      • Ensure the runtime of FDB and FDBService is ASP.NET 4.0
      • Configure wildcard for FDB only to support ASP.NET MVC
      • Rename Application Name to FDB and FDBService accordingly
      • Configure Integrated Windows authentication for FDB and FDBService
      • Configure application pool for FDBService
      • Create a dedicated application pool.
      • Configure an account belonging to Administration Group.
      • Configure application pool for FDBService.
      Reference:<br />
      • http://leethams.wordpress.com/2010/06/12/modifying-directory-permissions-with-web-deployment/
      • http://vishaljoshi.blogspot.com/2009/02/web-packaging-creating-web-packages.html
      • http://vishaljoshi.blogspot.com/2010/11/team-build-web-deployment-web-deploy-vs.html
      • http://msdn.microsoft.com/query/dev10.query?appId=Dev10IDEF1&l=EN-US&k=k(WEBAPPLICATIONPROJECTS.PACKAGEPUBLISHOVERVIEW)&rd=true#thirdparty_hosting_scenarios
      • http://live.visitmix.com/Archive
      • http://blogs.technet.com/b/josebda/archive/2010/03/31/experimenting-with-powershell-v2-remoting.aspx