Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Understanding and identifying the physical architecture of the environment your deploying into will help make sure of your deployment success. Planning is key. </p> <p>Like @Kirk mentioned, practice makes perfect. If you have access to a virtual environment of any sort, create a virtual image with similar characteristics of your deployment environment to help you out. Install the same OS, IIS and .NET framework versions and practice deploying to it.</p> <p><a href="http://msdn.microsoft.com/en-us/library/ms998297.aspx" rel="nofollow noreferrer">How To: Create a Service Account for ASP.NET 2.0 Applications</a> will walk you through creating a custom service account (if required) to run your app pool under. I don't remember if aspnet_regiis.exe grants the account 'logon as a service right'. Check out the NTRights.exe utility to determine how to do this.</p> <p><a href="http://msdn.microsoft.com/en-us/library/ms998258.aspx" rel="nofollow noreferrer">Security Guidance: ASP.NET 2.0</a> contains some best practices around securing your deployments.</p> <p><a href="http://msdn.microsoft.com/en-us/library/cc949034.aspx?rssCatalog" rel="nofollow noreferrer">Improving Web Services Security: Scenarios and Implementation Guidance for WCF</a> "light reading" </p> <p><a href="http://msdn.microsoft.com/en-us/magazine/cc163357.aspx" rel="nofollow noreferrer">Extend Your Services Beyond HTTP with WAS</a> will walk you through configuring non-http bindings for IIS 7.</p> <p>MSDN <a href="http://msdn.microsoft.com/en-us/practices/bb985515.aspx" rel="nofollow noreferrer">Patterns and Practices Catalog</a> </p> <p>Once you've figured out how to successfully deploy into your environment, automating the deployment process will make sure that it is repeatable.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload