Absolute VSS path for WebApplication project in solution file

Question

I have a VS2005 solution containing both windows projects (Windows application and class libraries) as well as a .NET web service application

In the solution file, all the windows projects are neatly listed with no absolute VSS path information, like this:

Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Director.Client.WebService.Code", "Source\Director.Client.WebService\Source\Director.Client.WebService.Code\Director.Client.WebService.Code.csproj", "{792F713A-C194-48B9-AD3B-03B3FDD76C32}"
    ProjectSection(WebsiteProperties) = preProject
        Debug.AspNetCompiler.Debug = "True"
        Release.AspNetCompiler.Debug = "False"
    EndProjectSection
EndProject

But for the .NET WebService Application project the solution file contains absolute path information linking this project to my personal share in VSS, like this:

Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "Director.Client.WebService", "Source\Director.Client.WebService\Source\Director.Client.WebService\Director.Client.WebService.csproj", "{51B044DD-A722-4FF7-96F2-A120135403C0}"
    ProjectSection(WebsiteProperties) = preProject
        SccProjectName = ""$/XdataCon/Development/Lars/Director/Director.Client", HYWBAAAA"
        SccAuxPath = ""
        SccLocalPath = "..\..\..\.."
        SccProvider = "MSSCCI:Microsoft Visual SourceSafe"
        Debug.AspNetCompiler.Debug = "True"
        Release.AspNetCompiler.Debug = "False"
        VWDPort = "2926"
    EndProjectSection
EndProject

If I delete the absolute path information from the solution file it automatically comes back when I do a save-all in VS2005. In the VS2005 source control bindings (the 'Change Source Control' dialog) the solution and all projects are bound to the same root in VSS as one block.

How can I get rid of the absolute path information in the solution file??

Thank you
Lars Kjaersgaard

Answer 1

Hi Lars,

 

I highly suggest you don’t delete source control integration related code, you will risk breaking the source control integration or other source control related features.

 

As the document: Files used by source control integration in VSS and VS .NET says:

 

In VisualStudio 2005 web projects don't have an associated project file, so VisualStudio 2005 had to store project-specific settings like the source control bindings in a different location. While bindings are stored in the solution file, a copy of the project bindings is also stored in this WebSites.xml file. This allows opening web projects without a solution; web projects will still be able to connect to the correct source control location. The source control information stored in this file is equivalent with the information stored in the project file by the projects that track their files using a project file (vbproj, vcproj, etc).

 

So if you delete these code in .sln file, there is still another copy of the project bindings stored in .xml file.

 

If I misunderstood you, or you have any questions, please let me know.

 

Hope this helps,

Nancy

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Answer 2

Hello Nancy

Thanks for your reply.

I am not using the VS 2005 Web Site but rather the VS 2005 Web Application Project (from Scott Gu's blog ). This type of project does have an associated project file, so I do not understand why the old limitations and grievances of the VS 2005 Web Site that you refers to are still there.

The project file concerned refers to the solution file:

    <SccProjectName>SAK</SccProjectName>
    <SccLocalPath>SAK</SccLocalPath>
    <SccAuxPath>SAK</SccAuxPath>
    <SccProvider>SAK</SccProvider>

But - as decribed in my first post - the solution file has absolute and not relative VSS path information.

Inspired by your reply I went looking for the Websites.xml in %USERPROFILE%\Local Settings\Application Data\Microsoft\WebsiteCache. But this folder does not exist on my machine.

As I am working in a team with several other developers in a VSS structure where each team member has a personal project in VSS and in this projects is sharing items with the other developers as they are tested and ready for integration. This structure works for all projects except the Web Application projects because absolute path information to my personal VSS project is persisted in the sln file. This renders it unusable for other team members.

I hope this clarifies my question

Thanks
Lars

PS: I agree to your remarks on editing the sln file. But in some instances - especially in source control bindings - VS2005 makes mistakes that makes manual edits necessary. I am sure other VS2005 developers will tell you the same story.

Answer 3

Hi Lars,

I have write a Web Project  for test in my side, and I found the name of associated project file is mssccprj.scc which locates in the root folder of your solution directory. Please check it, it contains SCC_Aux_Path and SCC_Project_Name.

And I also find a article about Web projects and Source Control Integration in our MSDN, please see the following link:

Web Projects and Source Control Integration in Visual Studio .NET

Best Regards,
Nancy

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.