Web Deployment Projects (WDP) for Visual Studio 2008 - December 2007 CTP Released

Web Deployment Projects (WDP) for Visual Studio 2008 - December 2007 CTP Released

  • Comments 77

    Based on the feedback from web development community we just released the Customer Technology Preview (CTP) of Web Deployment Projects for Visual Studio 2008... This release of Web Deployment Projects (WDP) has all the features that VS 2005 WDP release has and in addition has few other enhancements which I will call out later in this post...

    We will be releasing the final version of Web Deployment Projects for Visual Studio 2008 in January 2008 after incorporating all the feedback that we receive via this Dec 2007 CTP release… This CTP is a substantial milestone as it will unblock lot of Web Developers, who depended upon WDP to go ahead and use the latest and greatest features of Visual Studio 2008…

    Overview

    Visual Studio 2008 Web Deployment Projects is an add-in to Visual Studio 2008 which provides developers with advanced compilation and deployment options... A Web Deployment project is extensible, enabling web developers to create pre-build and post-build actions...

    Web Deployment Projects does not touch any shipping binaries within VS 2008… WDP neither changes the way Visual Studio 2008 Web Sites & Web Application Projects build nor does it changes the files in the source Web site project in any way... Instead, it takes an existing Web project as input and generate a precompiled Web as an output...

    Core WDP Features

    Visual Studio 2008 Web Deployment Projects preserves all the core functionalities that Visual Studio 2005 Web Deployment Projects had... You can read more about this core functionalities in the VS 2005 WDP white paper on MSDN... Also a tutorial on Web Deployment Projects VS 2005 can be found at Scottgu's blog...

    Prerequisites

    Before installing the WDP for VS 2008 CTP release ensure that .NET Framework 3.5 is installed on the machine… .NET Framework 3.5 can be downloaded from Microsoft Download Center

    Download Location

    WDP for Visual Studio 2008 - December 2007 CTP release can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=0FF6B63F-F79D-4590-B619-A2A4E06820F0&displaylang=en

    WDP for VS 2008 Enhancements

    Migration from WDP for VS 2005 to WDP for VS 2008

    We have ensured that your migration from WDP for VS 2005 to WDP for VS 2008 is as smooth as migration of your Web Site or Web Application itself… Below is a quick step by step tutorial of various scenarios that you might face while migrating…

    Scenario 1: You have installed VS 2008 and also this CTP release of WDP for VS 2008 and now want to migrate your VS 2005 Web + WDP to the latest version

    1.   When you try to open your VS 2005 Web Site with VS 2008 you will be prompted with the below dialog box to upgrade to .NET Framework version 3.5:

     

    2.   You can choose to upgrade to .NET Framework version 3.5, although it is not necessary… WDP internally uses .NET Framework 3.5 but it does not enforce your website to upgrade to 3.5 version… What this means is that you can still use great VS 2008 features even if your organization is not yet ready to move to .NET Framework 3.5… In my walkthrough I will stick with .NET 2.0 to illustrate that it still works :-)…

    3.   On clicking "No" your web site should open without WDP in it… Now you will have to go to File --> Add Existing Project option and navigate to the folder where your WDP project file is located (i.e. .wdproj file)… By default you will not see the .wdproj file as WDP is still not an intrinsic project type of VS… Although if you type "*.wdproj" in the "File Name" textbox and hit Open then you will be able to see your WDP project file from VS 2005… Select this file and hit Open…

    4.   You will now be presented with the Visual Studio conversion dialog as below:

     

    5.   Just keep cruising through this Conversion Wizard and you should have your WDP for VS 2005 project migrated to WDP for VS 2008 with all your settings and configurations preserved...

    Scenario 2: You have installed VS 2008 but not WDP for VS 2008 and have already attempt to open a VS 2005 Web which had WDP associated with it

    1.   If you try to open your VS 2005 Web + WDP in VS 2008 without installing WDP for VS 2008 then using steps 1, 2 & 3 described in the Scenario 1 will result in the following pop-up:

     

    This will block you from moving ahead from WDP standpoint, although if you download and install WDP, you should be able to proceed as described in Step 4 of Scenario 1 above…

    2.   Instead of opening a WAP or Web Site if you instead try to open your solution file (which will have reference to the WDP project already) then your solution explorer will look as below:

     

    3.   If you now install WDP for VS 2008 then you will have to close and reopen your IDE… After restarting your IDE, if you attempt to open the solution file you will be shown the same conversion wizard as described in Step 4 of Scenario 1 above…

    Although, if you have not yet opened your VS 2005 Web + WDP in VS 2008 then I will strongly encourage you to first download and install WDP for VS 2008 and then go ahead with your migration...

    Replacing WDP output only if Pre-Compilation succeeds

    Based on feedback from multiple users we have enhanced WDP so that it does not wipe out the precompiled web from previous WDP run until the current WDP does not build successfully… This is specifically useful if you have created IIS Virtual directory pointing to the output location...  Now even if your current WDP build does not succeed your web site in IIS will still continue to function… At the same time this also implies that it will be important to take a note of the WDP output in the VS output window before grabbing the deployed output for any further processing as your output folder might have the output from the previous build...

    Creating IIS Applications

    WDP for VS 2008 has an option to create IIS virtual directory for the output folder as shown in the WDP image below:

     

    This feature has been enhanced to work great with IIS7 as well… Although do note that you will need to manually set the appropriate folder permissions on the "Output Folder" you define in the "Compilation" section of WDP (e.g. Network Service for IIS6 or IIS_IUSRS for IIS7)… We will consider automating this in the future…

    Using aspnet_merge.exe version which is installed with Visual Studio 2008

    WDP uses aspnet_merge.exe to perform various merge options shown in WDP dialog below:

     

    In VS 2005 timeframe WDP for VS 2005 shipped aspnet_merge.exe in the box… With VS 2008 aspnet_merge.exe ships along with framework SDK, hence WDP for VS 2008 install does not contain aspnet_merge.exe… When you install Visual Studio 2008, aspnet_merge.exe should get automatically installed in "%Program Files%\Microsoft SDKs\Windows\v6.0A\bin" folder… WDP will require aspnet_merge.exe to be present at the above mentioned location to function correctly...

    Feedback

    We are hoping that WDP for VS 2008 will help you with your deployment needs and make you web development experience better with Visual Studio 2008...  We are eager to hear your feedback and suggestions for improvements hence we are enabling various below mentioned ways by which you can share your experiences...

    1.   MSConnect Feedback System

    1. Click here to submit feedback via MSConnect...
    2. Sign in using your Windows Live ID or Microsoft Passport Account...
    3. On the page, click “Submit Feedback.”...
    4. Search "Feedback" to see if the issue has already been submitted. If you find an issue similar to your own, you can validate and/or vote on the issue to increase its visibility. Otherwise, continue to the next step...
    5. Click the “Submit Feedback” button found beneath the search results table...
    6. You may submit either Bugs or Suggestions by selecting the proper feedback form...
    7. Make sure that you mention “Visual Studio 2008 Web Deployment Projects” in your Description field...
    8. Fill in the rest of the form to the best of your ability, and click the “Submit” button…
    9. We will contact you via your Windows Live ID / Passport email address once we have reviewed your issue...

    2.   Web Deployment Projects Forum on http://www.asp.net

    There is an active community of WDP users on the ASP.Net forums. WDP team also regularly visits the forums so please feel free to go http://forums.asp.net/1020/ShowForum.aspx to share your feedback or ask queries…

    3.   Blog Comments

    We will be monitoring this blog comments also fairly regularly so feel free to provide your feedback and comments here...

    Notes

    • Web Deployment Projects for Visual Studio 2008 are not supported for any pre-RTM versions of Visual Studio 2008 (Codename "Orcas")
    • Web Deployment Projects for Visual Studio 2008 are not supported in Visual Web Developer Express Edition...

    - Vishal R. Joshi | Program Manager | Visual Web Developer Team

Leave a Comment
  • Please add 7 and 2 and type the answer here:
  • Post
  • PingBack from http://www.absolutely-people-search.info/?p=1813

  • Hi

    ---------------------------

    Microsoft Visual Studio

    ---------------------------

    Package Load Failure

    Package 'Web Deployment Projects Package' has failed to load properly ( GUID = {CBA82673-3810-4290-BC4F-06BE9BF845A1} ). Please contact package vendor for assistance. Application restart is recommended, due to possible environment corruption. Would you like to disable loading this package in the future? You may use 'devenv /resetskippkgs' to re-enable package loading.

    ---------------------------

    Yes   No  

    ---------------------------

    This is error i get trying to Add a Web Deployment Project

    Please help

  • I appreciate that Web Deployment Projects is not available with Visual Web Developer Express Edition. However, it was possible to enjoy “poor man’s support” for Web Deployment Projects with Visual Web Developer Express 2005 by running aspnet_compiler.exe and aspnet_merge.exe manually.

    If Web Deployment Projects for Visual Studio 2008 no longer includes aspnet_merge.exe then that “poor man’s support” is no longer available. Would it be possible to re-instate “poor man’s support” for Web Deployment Projects with Visual Web Developer Express 2008 using one of the following scenarios?:

    - Include aspnet_merge.exe with the final version of Web Deployment Projects for Visual Studio 2008 in January 2008.

    - Confirm that the aspnet_merge.exe provided with Web Deployment Projects for Visual Studio 2005 is the most up-to-date version and therefore can be used as a source of aspnet_merge.exe.

    - Provide the most up-to-date aspnet_merge.exe as a separate download for those people who don’t wish to download and install Visual Studio 2008.

  • This week my team released updates of the ASP.NET AJAX Control Toolkit as well as the Visual Studio Web

  • This week my team released updates of the ASP.NET AJAX Control Toolkit as well as the Visual Studio Web

  • I have asked this on Scott Gu's blog and have not received an answer, so I'll try here:

    Why is this not a built in project for Visual Studio?

  • This week my team released updates of the ASP.NET AJAX Control Toolkit as well as the Visual Studio Web

  • Anuj,

       Can you let us know the version of Visual Studio you are using... Is it pre-RTM?  You can find the exact version by clicking Help--> About Microsoft Visual Studio...  If you are using VS 2008 then the version should start with something like 9.0.2XXX

    -Vishal

  • Mike,

        To answer your question honestly "Why is this not a built in project for Visual Studio?" I would say that we could not get to it with tons on other things in VS 2008 and with the kind of design we would had liked...  We are considering it as a very high priority in next version of VS... I will be more than happy to discuss this in detail with you... You can drop me a line at my MS id (vijoshi)and we can discuss...

    -Vishal

  • I see two distinct scenarios for using Web Deployment Projects:

    1) The web developer wants to setup and deploy a web site from within Visual Studio.

    2) The web developer wants to deploy a web site using a dedicated build computer that does not necessarily have Visual Studio installed. Scenario 2 is a superset of the scenario I defined above as “poor man’s support” for Web Deployment Projects, where the web developer only has Visual Web Developer Express Edition available on her dedicated build computer.

    I believe Web Deployment Projects for Visual Studio 2005 supports both scenarios. In particular, this article (http://msdn2.microsoft.com/en-us/library/aa479568.aspx) outlines the validity of Scenario 2, where it says “You can install Web Deployment projects on a computer that does not have Visual Studio 2005 installed. This is useful if you want to use MSBuild features on a dedicated build computer. MSBuild is part of the Microsoft .NET Framework version 2.0 and does not require installation of Visual Studio 2005.”

    Unfortunately, Web Deployment Projects for Visual Studio 2008 doesn’t seem to support Scenario 2 in that:

    - The technical makeup of the distribution (it does not include aspnet_merge.exe) precludes Scenario 2.

    - The wording of the licence agreement (only installable on a computer that has Visual Studio 2008 installed) preludes Scenario 2.

    Therefore my feedback is that the final Web Deployment Projects for Visual Studio 2008 should be changed to cater for Scenario 2 by:

    - Including aspnet_merge.exe in the distribution.

    - Relaxing the wording of the licence agreement so that the aspnet_merge.exe/MSBuild features can be used on any computer. Obviously the interactive setup of a Web Deployment Project within Visual Studio would continue to only be useable and supported on computers with Visual Studio 2008 Standard Edition and higher installed (i.e. the interactive setup feature would not be available with the Visual Web Developer Express Edition).

  • Did you guys test it before releasing?

    I created a sample website and added web deployment project 2008 in the solution. Everything compiled fine.

    Then I created a class called PageBase which inherits from System.Web.UI.Page. This is a usual practice I do to have a base class for all the pages in my project.

    Anyway, then I changed my default.aspx to inherit from PageBase. I re-compiled the solution and now I am getting this error from Web Deployment Project.

    Error 1 An error occurred when merging assemblies: Access to the path 'C:\Inetpub\wwwroot\Learning\Learning_deploy\TempBuildDir\bin\App_Code.dll' is denied. aspnet_merge 1 1 Learning_deploy

    ???

    Any ideas?

  • Ash,

    I just followed the exact same steps as you mention above couple of times but I am not able to reproduce...  Is there any specific settings in WDP that you configured?...  

    -Vishal

  • Yesterday, Microsoft released a CTP for Web Deployment Projects for Visual Studio 2008 . I don't use

  • There are no specific settings. Is there a way I could send my project to you so you can take a look?

Page 1 of 6 (77 items) 12345»