VS2005 Project Files in Source Control

ladonnas · Post by **ladonnas** » Tue Aug 21, 2007 1:35 pm

We have a team of developers using VS2005 with project in SourceGear VAult for Source Control. We each use our own local IIS project for testing. We are running into problems with this because whenever one of us tries to edit the settings in the project file to point to our local IIS project, it checks out the .vbproj file and updates it. When the next person refreshes, their settings get overwritten.

Can you point me to the fix to allow us to each maintain our own local setting for the IIS path link but to use source control for the project file so that we are all getting the same project releases as we should?

Thanks,
LaDonna

Beth · Post by **Beth** » Tue Aug 21, 2007 2:09 pm

You can go into your Visual Studio options and change the option for Check Out on Edit, so that it won't automatically check out something when you edit it.

One thing to note is that if you ever add, rename, or delete files, the project file would need to be update for that change.

ladonnas · Post by **ladonnas** » Tue Aug 21, 2007 2:16 pm

That is the problem. I can't just change it locally because I still need to get the latest project file from Vault every time a new file is added to the project, etc. Doing that overwrites any local changes anyone has made. I need to figure out how we can just control this setting locally outside of the project file so that we can continue to use Vault but have our own IIS paths.

Thanks,
LaDonna

Terence · Post by **Terence** » Tue Aug 21, 2007 2:30 pm

The easiest way for you to do this would be to have everyone use the same IIS path.

For example, if the project name is foo, Everyone should use http://localhost/foo . If there is a port number, everyone should use the same port number as well (http://localhost:portNum/foo).

I'm not sure if Microsoft provides the functionality that you're seeking.

ladonnas · Post by **ladonnas** » Tue Aug 21, 2007 2:33 pm

It is not an option to use the same IIS path. We are a team of developers with several working on a shared server via Terminal Services. We each need our own local copy of the app, so we have to make each name unique to work with a team.

LaDonna

Terence · Post by **Terence** » Tue Aug 21, 2007 2:39 pm

I'm not sure I follow.

If developer A has his/her own machine and it's running IIS, the default Web path would be http://localhost/something. When they get the project from version control, can't they name their local copy the same as it is in the source tree? For example http://localhost/projectNameFromTree ?

Can you give me a more detailed example so that I can understand where, in the process, this breaks down for you?

ladonnas · Post by **ladonnas** » Tue Aug 21, 2007 2:44 pm

We have 3 developers that all work on one shared server using Terminal Services. Therefore, if the project default Web path would be http://localhost/something, then developerA calls his local version http://localhost/somethingA, developerB calls his local version http://localhost/somethingB, and developerC calls his localversion http://localhost/somethingC. This is the only way to allow 3 developers to work on this machine at the same time. IIS requires unique names for each web application.

Our problem is that now this web path is stored in the vbproj file. This didn't happen this way with previous versions.

Thanks,
LaDonna

Terence · Post by **Terence** » Tue Aug 21, 2007 3:18 pm

Ahhh. Well I've been googling and I haven't found a way to strip the path information out. I'll keep looking for you, now that I better understand your problem.

ladonnas · Post by **ladonnas** » Mon Aug 27, 2007 7:41 am

It has been nearly a week without any reply here. This is a critical issue for us. We opened a trouble ticket with Microsoft, and they say it is a SourceGear Vault issue since your tool should learn to adequately handle multiple users using this file. What do I need to do to get further support here?

Thanks,
LaDonna

Terence · Post by **Terence** » Mon Aug 27, 2007 8:34 am

We're not ignoring you.

I've been toying with different scenarios, none of which have worked yet. Would it be a problem for you to change the project's Web setting from IIS to Visual Studio Development Server?