Welcome to MSDN Blogs Sign in | Join | Help

Visual Web Developer Team Blog

Your official information source from the Visual Web Developer team.

News

  • These postings are provided "AS IS" with no warranties, and confer no rights. Use of included code samples are subject to the terms specified Terms of Use
Web Deployment Projects (WDP) for Visual Studio 2008 - December 2007 CTP Released

    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

Posted: Saturday, December 01, 2007 7:42 AM by WebDevTools

Comments

Anuj Pandey said:

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

# December 1, 2007 6:03 AM

Poor Man said:

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.

# December 1, 2007 10:07 AM

Jason Haley said:

# December 1, 2007 1:51 PM

ScottGu's Blog said:

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

# December 1, 2007 2:26 PM

BusinessRx Reading List said:

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

# December 1, 2007 2:45 PM

Mike said:

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?

# December 1, 2007 2:53 PM

Elan Hasson's Favorite Blogs said:

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

# December 1, 2007 3:01 PM

WebDevTools said:

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

# December 1, 2007 3:11 PM

WebDevTools said:

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

# December 1, 2007 3:19 PM

Poor Man said:

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).

# December 1, 2007 4:05 PM

Ash said:

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?

# December 1, 2007 4:26 PM

WebDevTools said:

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

# December 1, 2007 5:52 PM

Steven Smith said:

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

# December 1, 2007 7:09 PM

Ash said:

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

# December 2, 2007 10:29 AM

Mike said:

It's now clear that it was just an issue of time that the WDP was not included with Visual Studio 2008 and that it will be included with a next version of Visual Studio.

# December 2, 2007 10:54 AM

aboreham said:

I'm getting the error "missing section appSettings" when I build. It looks like its putting the output into a TempBuildDir folder instead of the one I specified in the WDP.

# December 2, 2007 8:05 PM

WebDevTools said:

Ash,

   You can send your project to me at vijoshi at microsoft... Will take a look...

-Vishal

# December 2, 2007 9:25 PM

WebDevTools said:

aboreham,

   Thanks for bring out the point, I can see such behavior for other config section replacements...     Investigating this issue...  Will it be possible for you to log a MS Connect bug as specified above that way you will get notified on the teams developments on this... We will also try to update the comments here...

-Vishal

# December 2, 2007 9:28 PM

Peter Mounce said:

There is a bug in the v2005 version that prevents a web-deployment-project being used to build a web-application-project (as opposed to a filesystem-based, no-project-file one) from the command-line using MSBuild.

That prevents us from using WAPs with WDPs in our continuous integration.  Has that been addressed in this update, or is it a problem with WAPs?

Details:

http://blogs.vertigosoftware.com/teamsystem/archive/2006/08/22/Web_Application_Projects_in_Visual_Studio_2005.aspx

http://forums.asp.net/p/988775/1279716.aspx#1279716

# December 3, 2007 5:21 AM

Mark Rae said:

1) Will this install co-exist with the existing install of WDP for VS.NET 2005? I have VS.NET 2005 and VS.NET 2008 installed and working quite happily on the same box.

2) Will this CTP need to be uninstalled before installing the final version in January?

3) Does this version "understand" not to deploy files which have been excluded from the project? This is a major irritation with the current version.

# December 3, 2007 6:49 AM

Noticias externas said:

I know a lot of folks have used web deployment projects (WDP) with Team Build. The WDP release for VS

# December 3, 2007 9:26 AM

WebDevTools said:

Mark,

  Answers to your qustions inline:

1) Will this install co-exist with the existing install of WDP for VS.NET 2005? I have VS.NET 2005 and VS.NET 2008 installed and working quite happily on the same box.

A.) Yes...

2) Will this CTP need to be uninstalled before installing the final version in January?

A.) Yes, although your projects will work just fine with the RTW release...

3) Does this version "understand" not to deploy files which have been excluded from the project? This is a major irritation with the current version.

A.) We do not have the exact featue you are asking but an alternate feature to exclude the files that WDP should not consider...  Please visit http://msdn2.microsoft.com/en-us/library/aa479568.aspx and search for "ExcludeFromBuild", it explains how to use it...

-Vishal

# December 3, 2007 9:42 PM

WebDevTools said:

Hi Peter,

        WDP VS 2008 works both with Web Application Projects (WAPs) as well Web Sites...

-Vishal

# December 3, 2007 9:45 PM

sjlauritsen said:

> Thanks for bring out the point, I can see such

> behavior for other config section replacements...    

> Investigating this issue...

Investigate no further. It is because WDP looks for the web.config file in whatever path you have as your output path. This will fail, since the build takes place in the "TempBuildDir" and the output dir is empty.

If you put a valid web.config file in your OutputPath, voila, web.config replacing works.

Except for the copying to the output path... but that is another issue.

- sjl

# December 5, 2007 9:39 AM

Scott said:

When using an any targets (specifically an AfterBuild in my case), the web deployment projects in VS 2008 don't copy files to the specified output directory.  There is no error, it just doesn't copy the files.

If you comment out the target, everything works fine.  Note that this worked perfectly in VS 2005.  Something in this new release wasn't tested and was broken.

# December 5, 2007 10:03 AM

Programming said:

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

# December 6, 2007 2:44 AM

WebDevTools said:

Hi Scott,

Thanks for bringing this to our attention, and we are currently investigating.  Just to make sure, we are seeing the same problem, are you just editing the WDP project file to perform an AfterBuild action?  Also, can you see if your files are being copied to ./TempBuildDir instead?

Thanks,

Alison

# December 6, 2007 3:02 PM

Juan Barrera said:

I'm experiencing the same issue as above.

The web.config replacement doesn't work because it's looking for the replacement xml file in the output directory, which hasn't been populated yet.

Also, I raised another issue in the forums, but it doesn't seem to be anybody else having it:

Even if I only get up the the "web config replacement" point and then it fails, I get a few GAC dlls copied to my bin folder:

System.Web

System.Data

System.Data.OracleClient

System.EnterpriseServices

System.EnterpriseServicesWrapper

and System.Transactions

Obvioulsy these shouldn't be in the bin folder, and I;m not even referencing some anywhere.

The same project it's been running perfectly under VS 2005 for months.

Any ideas?

Thanks!

# December 6, 2007 6:46 PM

MarkRae said:

Vishal,

>> 3) Does this version "understand" not to deploy

>> files which have been excluded from the project?

>> This is a major irritation with the current

>> version.

> A.) We do not have the exact featue you are asking

> but an alternate feature to exclude the files that

> WDP should not consider

> "ExcludeFromBuild"

I understand about ExcludeFromBuild, but that still involves doing things twice, and editing the WDP file manually...

E.g. if I have a folder of images, I might want to deploy only some of them today, and some different ones next week, and a combination of the two the week after that. Therefore, it's extremely useful to be able to right-click on the image file in Project Explorer and select Exclude From Project, and then when I want to include the image again, I just do the reverse. If WDP could be prevented from deploying those files which have been exluded from the project in this way, that would be incredibly useful. Would that really represent an enormous amount of development effort...?

Mark

# December 8, 2007 10:48 AM

Lars said:

Solution to the problems with:

Target Name="AfterBuild"

http://weblogs.asp.net/lkempe/archive/2007/12/02/web-deployment-projects-for-vs08-released-as-ctp-amp-migration-tips.aspx

Tested and it works

Thx Laurent.

# December 11, 2007 11:00 AM

Rasetti said:

Lars,

That's the same workaround that has been posted on the forums, but it doesn't work for everybody (not for me, at least).

Cheers,

# December 11, 2007 3:00 PM

小角色 said:

【原文地址】ASP.NET AJAX Control Toolkit and Web Deployment Project Releases for VS 2008

# December 12, 2007 4:57 AM

Alec said:

Just wanted to let you guys know I'm running the Devember 2007 CTP and I'm also having a problem with config section replacements in web.config. I've defined release-web.config and pointed my WDP config to use config sections from it. However, when building I'm getting the error that release-web.config cannot be found in the build directory. Looks like WDP is looking for the replacement file in the wrong folder.

-Alec.

# December 12, 2007 10:49 AM

WebDevTools said:

Hi Juan,

Yes, the web.config replacement problem you are seeing sounds like the same as above.  We will be fixing the issue for the final release.  I haven't run into your GAC dlls problem before.  Did you migrate your project?  Is there anything special about your solution that might help us repro?  If you prefer, we can continue on your forum post if you let us know the link.

-Alison

# December 12, 2007 7:23 PM

Rasetti said:

Hi Alison, thanks for your response.

I'm glad that you identified the replacement issue and fix it in the release version.

About the .dlls issue, there is probably no too much I can add, I just have a Solution composed by one local IIS WebSite and one Web Deployment Project.

In Visual Studio 2005 it's been working flawlessly since almost WDP for VS2005 was released.

Then, I converted the whole solution in VS2008, with WDP already installed, and every time I try to deploy it, the mentioned dlls are added to the bin folder,

but there is nothing special I can mention about it to help you reproduce.

As a note, I can assure you that the Project file has ToolsVersion set to 3.5 and it's pointing to the right MsBuild version (9.0).

Here is the link to my post in the forums, I've just seen that another user is having the same problem.

http://forums.asp.net/t/1189535.aspx

Thanks,

# December 12, 2007 9:20 PM

WebDevTools said:

Hi Juan,

I've been using File System websites.  I'll see if I can repro with an IIS web. I'll follow up with you in more detail on the forums.

Thanks!

Alison

# December 12, 2007 9:42 PM

Sambo said:

Hi,

I love WDP. Does it will be support with Visual Web Developer 2008 Express Edition?

Thank

# December 14, 2007 10:06 PM

WebDevTools said:

Hi Sambo,

WDP is not supported on VWD2008 Express Edition.  The supported editions are:

Microsoft Visual Studio 2008 Standard Edition

Microsoft Visual Studio 2008 Professional Edition

Microsoft Visual Studio Team System 2008 Team Suite

Microsoft Visual Studio Team System 2008 Architecture Edition

Microsoft Visual Studio Team System 2008 Developer Edition

Microsoft Visual Studio Team System 2008 Test Edition

Thanks,

Alison

# December 17, 2007 9:48 PM

gOODiDEA said:

Web:手把手教你开发Facebook应用VisualStudio:WebDeploymentProjects(WDP)forVisualStudio200815 Fre...

# December 17, 2007 10:36 PM

Ryan Williams said:

It's important to note I think that in WDP 2005, the AfterBuild target was not implemented by MS.  In 2008, the change of using the TempBuilDir, and then cleaning it up in the AfterBuild target has caused many an upgrader problems.

I'm no MSBUILD expert, but it seems like the MS provided AfterBuild target shoud be chained to what is in the project's AftetBuild target, or just implement that cleanup internally in Microsoft.WebDeployment.targets.  To have everybody copy from the MS version to the local project file seems like a hack.

# December 18, 2007 6:54 PM

WebDevTools said:

Ryan,

    You are correct in identifying the problem area and we will be taking care of the AfterBuild issue in the RTW of WDP in Jan 2008 timeframe, till that time the work around that you suggested should work...

-Vishal

# December 18, 2007 7:03 PM

Frenz said:

Hi

I've been using aspnet_compiler.exe for quite a while to precompile a website. The project has grown quite large and as a consequence it is now taking a very long time to precompile. We are currently at 10+ minutes and the site will only grow bigger in the future. If we need to sync a quick bug-fix, 10+ minutes is actually becomming an issue.

I have not tested the 2008 version, so I don't know if you have made any performance improvements.

With the 2005 version we have tried upgrading the compile server (which is now a dual dual-core xeon, 4 GB memory and 15K rpm Raptor disks), but with no considerable performance improvement.

Actually we have gone so far as to look at the classes in System.Web.Compilation and are considering writing a multithreaded version (I believe this is possible, if we accept some compilation overhead - CPU usage does not seem to be the issue, so this may be worth it), however before we take it thus far, I would like to hear if you are considering serious performance improvements yourself?

# December 19, 2007 3:54 AM

WebDevTools said:

Hi Frenz,

   What are the command line options that you are providing to the aspnet_compiler.exe...  Are you trying to compile the entire site everytime?

   Are you changing something in your app_code folder as that may cause the entire site to get compiled every time...

   Also multi-threaded option might not always work great due to the fact that compilation needs to follow a specific order to work correctly...  

   Feel free to send me an email at Vishal dot Joshi at microsoft dot com and we can discuss this further...  I can perhaps put you in touch with the right folks...

-Vishal R. Joshi

# December 19, 2007 9:16 PM

Brad Abrams said:

As I mentioned last month , VS 2008 fully supports building applications for .NET Framework 2.0... This

# December 19, 2007 10:34 PM

Noticias externas said:

As I mentioned last month , VS 2008 fully supports building applications for .NET Framework 2.0... This

# December 19, 2007 11:04 PM

Pure Krome said:

Three questions :)

1) How can WDP using multi-processor support, please?

2) Is WDP using .NET Framework 2.0 for the merging?

3) I cannot replace any web.config sections that are with custom dll's. For example, we purchased a 3rd party File Uploaded (called SlickUpload, info here: http://assistedsolutions.com/components/SlickUpload/  and web.config info for the component found here: http://krystalware.com/Products/SlickUpload/Documentation/InstallingSlickUpload.aspx).

How can I tell the WDP that the location of the dll is at XXXXX (eg. c:\temp\My.dll)?

# December 21, 2007 1:41 AM

Developer Blogs said:

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

# December 21, 2007 10:42 AM

Liwoj said:

Is the bug with compiling resources described here (http://forums.asp.net/p/1125813/1770481.aspx#1770481) resolved pls ?

Thx

# December 23, 2007 3:32 PM

Jessica said:

Hello!

  I too am getting the web.config replacement section problems like Pure Chrome is getting, three posts above. It's sooo frustrating :(

Could someone please help us by post some solutions, please?

-J-

# December 24, 2007 7:13 PM

WebDevTools said:

Hi -J-,

   I apologise for the inconvinience that this bug has caused...    We will be fixing it in the RTW release next month...  There is work around discussed in the forums http://forums.asp.net/t/1189373.aspx and http://forums.asp.net/t/1189079.aspx...  Could you look into it and let me know if you need any assistance at Vishal dot Joshi at Microsoft dot com

wishes

Vishal

# December 24, 2007 7:27 PM

WebDevTools said:

Hi Pure,

Answers to your questions inline:

>>>>>1) How can WDP using multi-processor support, please?

WDP cannot support multi-processor yet so there is no setting available to enable it...

>>>>>2) Is WDP using .NET Framework 2.0 for the merging?

WDP is using aspnet_merge.exe from .Net Framework 3.5...

>>>>>3) I cannot replace any web.config sections that are with custom dll's. For example, we purchased a 3rd party File Uploaded (called SlickUpload, info here: http://assistedsolutions.com/components/SlickUpload/  and web.config info for the component found here: http://krystalware.com/Products/SlickUpload/Documentation/InstallingSlickUpload.aspx).

There is a bug in Dec 2007 CTP of WDP which is not allowing the web.config replacement correctly... This issue will be fixed in RTW release of WDP...

>>>>How can I tell the WDP that the location of the dll is at XXXXX (eg. c:\temp\My.dll)?

WDP is tied to your WAP or WebSite... It picks up the referenced assemblies for WAP and WebSite automatically so you not need to tell WDP about your dll location directly.  If you want to copy specific files to your WDP output directory you can create an afterbuild MSBuild task for your WDP (chaning the WDP project file) which can do the required copy work...

Hope this helps

-Vishal

# January 2, 2008 2:28 PM

Pure Krome said:

Thanks Vishal for the reply :)

The work around you mentioned for Jessica above, worked for me too, but still didn't help with my third issue, as stated above.

When you answered my third issue above, I don't understand what you mean by this :

>>WDP is tied to your WAP or WebSite... It picks up the referenced assemblies for WAP and WebSite automatically so you not need to tell WDP about your dll location directly.

I have my custom dll in my websites BIN directory. At least it's there in my solution. eg. Website\Bin\3rdParty.dll

Therefore, it's like the WDP can't find my custom 3rd party dll.

Is there a way i can confirm this?

# January 2, 2008 7:40 PM

WebDevTools said:

Hi Pure,

   Is the 3rd party dll referenced in your website project or are you just copying it into your bin directory manually?

-Vishal

# January 2, 2008 10:12 PM

Pure Krome said:

Hi Vishal,

 yep, it's definitely referenced in the website. I right-clicked the website-properties -> References -> Krystalware.SlickUpload   /  BIN   / 3.5.6.31939

# January 3, 2008 1:47 AM

幸福 said:

【原文地址】ASP.NETAJAXControlToolkitandWebDeploymentProjectReleasesforVS2008

【原文发表日期】Saturd...

# January 4, 2008 7:48 PM

Patrick said:

is it correct the the output directory now is always the TempBuildDir and not the "debug" folder as in visual studio 2005?

# January 8, 2008 9:54 AM

Topher said:

Juan Barrera, I'm having the same issue you are. When I build using the WDP, it's adding the following GAC DLL's to my bin folder:

* System.Data.dll

* System.Data.OracleClient.dll

* System.EnterpriseServices.dll

* System.EnterpriseServices.Wrapper.dll

* System.Transactions.dll

* System.Web.dll

Is there a solution for this?

# January 8, 2008 4:14 PM

Rasetti said:

Topher,

It's related with AjaxControlToolkit, it's a known issue, and they are looking for a solution.

In the meantime, my workaround is adding the following to the AfterBuild target:

<Delete Files="$(OutputPath)\Bin\System.Web.dll" />

<Delete Files="$(OutputPath)\Bin\System.EnterpriseServices.dll" />

<Delete Files="$(OutputPath)\Bin\System.EnterpriseServices.Wrapper.dll" />

<Delete Files="$(OutputPath)\Bin\System.Data.dll" />

<Delete Files="$(OutputPath)\Bin\System.Data.OracleClient.dll" />

<Delete Files="$(OutputPath)\Bin\System.Transactions.dll" />

<Delete Files="$(SourceWebPhysicalPath)\Bin\System.Web.dll" />

<Delete Files="$(SourceWebPhysicalPath)\Bin\System.EnterpriseServices.dll" />

<Delete Files="$(SourceWebPhysicalPath)\Bin\System.EnterpriseServices.Wrapper.dll" />

<Delete Files="$(SourceWebPhysicalPath)\Bin\System.Data.dll" />

<Delete Files="$(SourceWebPhysicalPath)\Bin\System.Data.OracleClient.dll" />

<Delete Files="$(SourceWebPhysicalPath)\Bin\System.Transactions.dll" />

# January 8, 2008 4:45 PM

Topher said:

Thank you Rasetti, your suggestion will work great until they have a chance to fix the problem!

# January 8, 2008 7:11 PM

WebDevTools said:

Hi Patrick,

You asked

>>>>>> is it correct the the output directory now is always the TempBuildDir and not the "debug" folder as in visual studio 2005?

Based on various requests we will be first building the output to tempbuilddir and then only if the compilation was successful we will copy it to the output directory...  This is to ensure that previous prestine drop does not get spoild....

Currently there are some problems with the AfterBuild copy task of WDP but in RTW this will be fixed...

-Vishal

# January 8, 2008 9:33 PM

WebDevTools said:

Hi Pure,

I wasn't able to repro your problem of WDP not finding your third party dll.  I downloaded the assembly from krystalware and I followed the instructions of how to install it by adding a reference and making web.config edits.  I also added the SlickUpload.ashx file into the project.  When I built the WDP and looked in the output folder, I saw that the 3rd party dll was copied.  I did use a newer SlickUpload version than yours (ver3.6) as it was the only one available to download.

-Alison

# January 9, 2008 4:23 PM

Stephane said:

BUG: I'm using the web config section replamcent feature of web deployment projects, but I'm experiencing the following problem.

I'm deploying to .\Testing\. My config files for section replacement are located in <<root web site>>\config\. When the project is done building the site, it looks for section replacement files in .\Testing\config (output directory). However, the current build execution path is .\TempBuildDir\, so the build process should be looking for .\TempBuildDir\config and not .\Testing\config. On "AfterBuild" the config folder gets deleted from the output directory, so .\Testing\config doesn't exist and therefore deplyment fails.

Long story short: update the config section replacement code to use the temp output folder rather than the final output folder as its execution path.

Thanks

# January 9, 2008 5:48 PM

Pure Krome said:

Hi Alison,

  thanks heaps for looking at my problem -- but my problem is not with the dll being copied to the BIN directory, which u tested.

My problem is with trying to use the web config SECTION REPLACEMENT for a 3rd party ... like the slick upload. If i try to replace the section in the web.config, I get the the following error:-

Error 9 An error occurred creating the configuration section handler for slickUpload/uploadStreamProvider: Could not load file or assembly 'Krystalware.SlickUpload' or one of its dependencies. The system cannot find the file specified. (R:\Visual Studio Projects\My Project\Deployment\Web Deployment Project\Web Deployment Project\Debug\web.config line 27) 1 1 Web Deployment Project

This is what i've added to the WDP project file...

<WebConfigReplacementFiles Include="ConfigurationSettings\SlickUpload.UploadStreamProvider.Development.config">

     <Section>slickUpload/uploadStreamProvider</Section>

   </WebConfigReplacementFiles>

Of course, i have the following section in my web.cofig file...

<slickUpload>

   <uploadStreamProvider location=".." fileNameMethod="Guid" existingAction="Overwrite"/>

   <statusManager provider="ApplicationState" />

   <uploadParser requestFilter="" attachEvent="BeginRequest"/>

 </slickUpload>

Does that make more sence?

Cheers :)

-PK-

# January 9, 2008 11:47 PM

Swiss DPE Team Blog said:

Hier finden Sie eine Liste der häufigsten Kunden-Fragen. 1. Das neue ASP.NET LINQDataSource Control bietet

# January 14, 2008 7:42 AM

Noticias externas said:

Hier finden Sie eine Liste der häufigsten Kunden-Fragen. 1. Das neue ASP.NET LINQDataSource Control bietet

# January 14, 2008 8:07 AM

Stephane said:

I deployed my site, and a whole bunch of image files are missing. It seems completely random. Under my App_Themes folder, some subfolders contain a 3 out of 20 image files.

If I check the temporary folder ("TempBuildDir"), everything seems to be there - no missing file. So the problem seemed to occur while copying the files over to the output directory. But I didn't receive any warning/error during build or deployment.

Overall, this new deployment process using a temp folder has been really unreliable (see my previous post about config section replacement), and is not solving anything for me - my current delpoyment setup works around broken builds by not deplying directly to the target server. It'd be great if I could have an option to have this work exactly the way it used to.

I'm deploying every 2 weeks. We upgraded to VS 2008 10 days ago, not realizing WDP 2008 were not released yet, converted all our projects, and now that we're about to release - deployment isn't working anymore. It's a real headache.

# January 15, 2008 1:37 PM

WebDevTools said:

Hi Stephane,

    Can you send me an email at Vishal dot Joshi at microsoft dot com... I would love to discuss a work around with you...

wishes

Vishal

# January 15, 2008 2:30 PM

Robert W. Anderson said:

Any update on when the RTW will be available?  We are about to do the upgrade to VS2008 and I'll wait a few days if this is about to RTW.

# January 16, 2008 12:28 PM

WebDevTools said:

Hi Robert,

   The test pass is still going on and we are not anticipating any major issues...

   In the event of any unforseen issue comes up we might have trouble otherwise we are still on track to RTW before the end of this month...

-Vishal

# January 16, 2008 5:47 PM

WebDevTools said:

Hi Poor man,

You said

>>>> 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.

aspnet_merge.exe should be now part of the following SDK install...  

http://www.microsoft.com/downloads/details.aspx?FamilyID=74dd6e2d-89c6-4e1e-af00-fc7d70f15439&DisplayLang=en

Hope this helps...

-Vishal  

# January 17, 2008 5:39 PM

WebDevTools said:

H All,

    We are still on track to release WDP before the end of this month...  Currently we have a very close to final build which is undergoing a test pass...  If anyone of you would like to receive this build for a test run then please send me an email at Vishal dot Joshi at Microsoft dot com...

    Although please do note that we probably may not have a lot of time so you may have to rush to bring up issues in case you would like us to fix them before RTW...

wishes

-Vishal

# January 17, 2008 5:52 PM

Your Websites, Our Passion! said:

In December 2007, we had released Community Technology Preview (CTP) version of&#160; VS 2008 Web Deployment

# January 26, 2008 12:29 AM

Buck Hodges said:

[UPDATE 2/3/08] The final version is now available . I know a lot of folks have used web deployment projects

# February 3, 2008 4:48 PM

Brendon said:

The download location mentioned at the beginning of the article is for the CTP release and is no longer valid. The replacement - the RTW release - is available at http://www.microsoft.com/downloads/details.aspx?FamilyId=0AA30AE8-C73B-4BDD-BB1B-FE697256C459&displaylang=en

# February 9, 2008 10:50 PM

rox19840702 said:

VS 2008版的ASP.NET AJAX控件工具包和Web部署项目

# February 27, 2008 12:38 PM

BlogDot10 said:

ASP,net Compiled DLLs and simplifying builds

# October 8, 2008 9:05 AM
New Comments to this post are disabled
Page view tracker