We are running into lots of issues migrating our solution from VS2003 --> VS2005. We have about 30 projects, 3 of them are web sites. In VSS, we have this structure:

            $\Version_1

                        \Web1\

                                    ...

                                    Web1.csproj

\Web2\

                                    Web2..csproj

\Web3\

                                    Web3..csproj

                        .....

                       \ClassLibrary1\

                        \ClassLibrary2\

                        \ClassLibrary3\                           

                        \Microsoft.ApplicationBlocks.ExceptionManagement\

                        Version_1.sln

This worked fine because we could have class library references and virtual directory information was not stored with the project/solution file but was kept in .suo file instead.

I installed the May 8 version of WAP and migrated the solution. It migrates without errors but we are having issues after adding the solution to source control (Team Foundation Server). We are not using ?Open from Source Control? with WAP because it is broken, as noted in postings on this board.

The problem is that project references are stored in the project file (.csproj) as absolute file paths. For example:

<ProjectReference Include="E:\Data\VSS\Version_1\Development\Microsoft.ApplicationBlocks.ExceptionManagement\Microsoft.ApplicationBlocks.ExceptionManagement.csproj">

      <Name>Microsoft.ApplicationBlocks.ExceptionManagement</Name>

      <Project>{386CBF50-F4A9-4F05-98CB-B387D2D8F357}</Project>

      <Package>{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</Package>

    </ProjectReference>

I tried setting references to something like this, without success:

<ProjectReference Include="..\Microsoft.ApplicationBlocks.ExceptionManagement\Microsoft.ApplicationBlocks.ExceptionManagement.csproj">

      <Name>Microsoft.ApplicationBlocks.ExceptionManagement</Name>

      <Project>{386CBF50-F4A9-4F05-98CB-B387D2D8F357}</Project>

      <Package>{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}</Package>

    </ProjectReference>

How can one use relative URLs?

Also, looking at the WAP .csproj file in notepad, I notice that IIS information is stored in the project file:

<IISUrl>http://localhost/Web2</IISUrl>

Local path/IIS v-root information used and should be stored in the .suo file. How can I achieve the same result with WAP and VS2005?

thank you

This must be a migration specific problem.  If you create a new WAP project and add references to other projects the you get relative paths.  Try removing the referneces and re-adding them.   That should result is relative paths being added to the project file.

As far as the IISUrl propery, it is a shared property for team scenarios and is not overrided by the .suo. We're evaluating this for a future release.

Hope this helps,
Brad.

BradleyB:

This must be a migration specific problem.  If you create a new WAP project and add references to other projects the you get relative paths.  Try removing the referneces and re-adding them.   That should result is relative paths being added to the project file.

As far as the IISUrl propery, it is a shared property for team scenarios and is not overrided by the .suo. We're evaluating this for a future release.

Hope this helps,
Brad.

Brad, thanks for your response. I could not get paths to be relative no matter what I did to the migrated project. I ended up creating new Web Application Projects, and adding project references to the rest of the projects. That produced relative paths (verified by opening on different machines and inspecting .csproj in notepad). Of course, I had to manually re-add all pages from the migrated WAPs to the WAPs I created from scratch. Does this sound like a bug to you or could this be specific to our VS.NET 2003 projects?

IISUrl is not a deal breaker, but it would be nice to allow each developer to be in control of their own v-roots, just the way it worked in VS.NET 2003. Our currents steps for configuring a dev machine are:

1) get latest from TFS (not Open from source control)

2) after getting latest, open solution file from local folder

3) for each WAP, go to project properties, Web, and click Create Virual Directory without changing anything (because this will affect the shared .csproj file).

Would the fix for Open From Source Control functionality (I know it is coming in VS.NET 2005 SP1) eventually replace steps 1-3 above? In other words, is it supposed to eliminate the need to manually configure IIS Virtual Directory?

thanks

Andrew

Yes, when Open from SCC is fixed in VS05 SP1 it will create the VDir for you. 

btw: I've entered a bug on the migrtion issue.

Brad.