Showing posts from December, 2011

Deploying Databases with Object-Level Permissions

As I mentioned in my last post , we’re currently creating some guidance on deploying enterprise-scale applications. As we go along, I plan to blog about a few of the things that I find particularly tricky to figure out. This time I want to look at database deployment. When you build a web application project in Visual Studio 2010, the Web Publishing Pipeline features allow you to hook into the IIS Web Deployment Tool (commonly known as “Web Deploy”) to package and optionally deploy your web application. As part of this process you can also deploy local databases to a target server environment. This is all nice and easy to configure through the project property pages in Visual Studio 2010, as shown below. I don’t want to describe this process in any detail, you can find that elsewhere on the web (for example here ). Deploying databases in this way has advantages and disadvantages. On the plus side: It’s easy. It’s UI-driven. It figures out most of the sett

Deploying Web Packages as a Non-Administrator User

Regular readers (all six of you ;-)) will have noticed that I haven’t posted about SharePoint for a while. For the last couple of months I’ve been working with the Developer Guidance team at Microsoft to write some MSDN content on enterprise-scale web deployment and application lifecycle management. I’ll let you know when the content is available, and I don’t plan to duplicate it here. What I want to do is just to draw attention to a couple of areas that I found particularly tricky to figure out. The first area involves the IIS Web Deployment Tool (commonly known as “Web Deploy”), and a gotcha around deploying web packages as a non-administrator user. For brevity I’ll have to assume that you’re broadly familiar with: Creating web packages for web application projects in Visual Studio 2010 (for example, see ASP.NET Web Application Project Deployment Overview ). The various different approaches you can use to deploy web packages (for example, see Using Web Deploy Remotely )