June 7, 2011
Blog ArchivesWalkthrough: deploy a web application with SQL CE 4.0 database to IIS host with SQL Server.
With VS2010 sp1, we added SQL CE 4.0 support. You can view more information about SQL CE 4.0 from the following sites: http://weblogs.asp.net/scottgu/archive/2010/06/30/new-embedded-database-support-with-asp-net.aspx http://blogs.msdn.com/b/webd…
0
Hosting for ASP.NET 4.0 & Web Deploy from ORCS Web, DiscountASP, and MaximumASP
Visual Web Developer 2010 Express offers a great set of features for deploying web applications seamlessly. One of the key features is the ability to publish your web application from VS 2010 to a remote hosted web server along with its dependencies like SQL Server database using “Web One Click Publish”. VS 2010 integrates Microsoft Web Deployment Tool (MsDeploy.exe) to provide a fast, reliable and cohesive way of deploying web applications. Learn more about Visual Studio 2010 Web Deployment Features . And now that you have been introduced to Web Deployment, you may be looking for a hoster which is compatible with both the new framework (ASP.NET 4.0) and the Web Deployment features included in this release. The following web hosting providers…(read more)
Tip #104: Did you know … How to view text for the ‘hint’ buttons on the Publish Web Dialog?
After the Beta 2 release of Visual Studio 2010, the Publish Web Dialog was modified to include two information buttons associated with the Service URL and Site/application text boxes. (See Figure 1) Figure 1 – New information (‘hint’) buttons (see circled…(read more)
Web Deployment: Excluding Files and Folders via the Web Application’s Project File
Web Deployment (see this posting for an overview) offers a set of pre-determined options to allow users to include the most common sets of files for deployment. These options are as follows and can be found under the “Items to deploy” section on the Package / Publish Web property page. Only files needed to run this application: This will include only the files required to run the application. Specifically, files to be included will be those found in the bin folder and those files whose Build Action property = Content (such as .aspx, .ascx, and .master). All files in this project: This will include all files within the project file. All files in this project folder: This will include all files in the source project folder, including those not…(read more)
One-Click Publish – What’s New Since Beta 2
Publishing using MSDeploy In-Process Deployment or Remote Agent Through the Beta 2 release, VS 2010 had only supported publishing to servers using MSDeploy's IIS deployment handler technology integrated with the “Web Management Service”, a.k.a. WMSVC. As long as you had an account on a hosting server using WMSVC, you could use MSDeploy to update your web content. This is the msdeploy technology most people will use when publishing to a hosted site and, therefore, was released first. (In case you are interested in how the server should be configured, check out the link: http://technet.microsoft.com/en-us/library/dd722796(WS.10).aspx ) In the RC release of VS 2010, We added support for two more msdeploy technologies that target specific deployment…(read more)
Extending the Web Publishing Pipeline to package database project deployed SQL file
A Visual Studio solution file may contain both database project and a web application project. When deploying (not building) the database project, it can generate a .sql file containing the full sql file or an incremental upgrade file against a database. This blogs walkthrough one way to package database project generated sql file into the web application project’s package. This solution works for team build scenario as well. 1. Create a Web Application Project 2. Add 2 new “SQL Server 2008 Database Project” to the solution 3. In each of the database project, add a sample table and make sure build and deploy are successful. Check the deployed SQL directory %database project dir%\sql\%configuration%\ making sure…(read more)
How to package COM component
If we want to package and deploy COM component for a web application only, we can simply reference them and change their “Copy Local” property to “True”. For example, we can do the following to package a MVC project from VS2010. Create a MVC project In its references, change the following three assemblies “Copy Local” property value to True. System.Web.Mvc System.Web.Routing System.Web.Abstractions You can multi-select them and set the value together. Right click the project node and select “Build Deployment Package” Examine the package, you will see the above assemblies' corresponding dll files are included in the package’s bin directory. Deploy the above package to a 4.0 site, no matter if the corresponding MVC runtime is…(read more)
How to extend target file to include registry settings for web project package
Web project package and deployment targets files are written with extensibility in mind. User can easily extend a property to include more functionalities in their package by using msbuild targets and properties. If we check the Microsoft.Web.Publishing.targets file under “%Program Files%\MSBuild\Microsoft\VisualStudio\v10.0\Web\”, we can see the following, which means if file $(WebPublishPipelineProjectName).wpp.targets exists in the project directory, we’ll import it automatically when build package or publish. <!– *************************************************************** –> <!– To allow the Team build to have custom setting for the Web Application project without change the project file –> <!– by default…(read more)
