Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

re: Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

David Williams — Fri, 28 Sep 2007 00:53:54 GMT

It appears this solution causes the Build to not populate the _PublishedWebSites folder under the Build Directory. We used this directory previously to manually copy the files to the target server.

<Copy SourceFiles="@(FilesToCopy)" DestinationFiles="@(FilesToCopy ->'\\server\integration\webapp\%(RecursiveDir)%(Filename)%(Extension)')"

ContinueOnError="true" />

It appears the _PublishedWebsites directory is no longer populated. We are getting the following error:

Could not find a part of the path 'c:\build\{Workspace}\{BuildType}\Binaries\Debug\_PublishedWebsites\adminweb\web.config

re: Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

David Williams — Fri, 28 Sep 2007 01:07:44 GMT

I also tried using the DropBuild folder like below, however the _PublishedWebsites directory is never populated, and hence the source code (aspx, config files etc) are never copied to the drop location.

<SkipDropBuild>false</SkipDropBuild>

re: Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

tblack — Fri, 28 Sep 2007 15:04:27 GMT

Yep, I see this too. I'm hoping that this will be fixed for RTM.

re: Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

David Williams — Tue, 02 Oct 2007 16:45:54 GMT

As a workaround, would there be a way to modify the project file in the .vbproj after the latest files have been retrieved, but before compiling starts? I am thinking about creating a target that uses xml transformation to change the 'Import Project...' property? I have used XML modification to modify the web.config files after the .sln is build (Target 'AfterDropBuild'), but not to change (the .vbproj) file before the compile. Is this possible?

re: Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

tblack — Wed, 03 Oct 2007 19:26:11 GMT

Sadly I've moved onto another project recently so don't have time to investigate this fully. If you're looking for a workaround I'd be inclined to look at the functionality contained in:

"$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v9.0\WebApplications\Microsoft.WebApplication.targets"

and see if you can factor any of that out into your own pre-build event. I think that would be preferable to further modifying the .proj files.

re: Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

Kevin Zink — Sun, 27 Jan 2008 03:00:31 GMT

Hey guys, I had this same problem where the _PublishedWebsites directory was not showing up in your deploy location. I'm actually using full-on VS2008, too, so it wasn't fixed.

Rather than adding an additional <import> into my project's .csproj file, I left the v9.0 import (I did not add a second import for the v8.0 directory), created the v9.0 directory on my build server, and then copied the v8.0 targets file into the newly created v9.0 directory.

This might help solve your problems. Here's a blog post that goes into more detail: http://zinknation.net/Using+Visual+Studio+2008+With+Team+Foundation+2005+Build+Server.aspx

re: Converting VS2005 solutions to VS2008 Beta 2 (Orcas)

Colin Nash — Tue, 10 Jun 2008 17:07:47 GMT

I have just been doing this on our servers. The problems you guys are getting seem to be due to the

'$(Solutions.VSVersion)' == '8.0' not evaluating properly. From what i've seen this is because Solutions.VSVersion in VS 2005 evaluates to nothing.

Change the condition to '$(Solutions.VSVersion)' != '9.0' and it works fine.