By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,750 Members | 1,367 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,750 IT Pros & Developers. It's quick & easy.

set web project under source control

P: n/a
Hi, there
we need help concerning setting project under source control.
We want to have a project on the server, and developers in the local network working on this project. We decided to use strategy officialy called "Isolated Development". We studied help in Visual Studio .NET called "Web Projects and Source Control Integration in Visual Studio ..NET". First we created solution on machine: A (server), then added a web project to this solution. Then on machine B (developer) we want to create a working copy of the project on the server.

In help we found this method:

To add the Web project to source control
1.In Solution Explorer, right-click the solution node, and then click Add Solution to Source Control.
2.If a message box appears, click Continue.
3.Provide database location and user logon information as required by your source control provider.
4.Create a root solution directory on the source control server by specifying the server location for the solution file.
5.Under the root solution directory, type a name for the project folder that will contain the master copy of your Web project's files.

Our problem is in the 1.step : we don't have "Add Solution to Source Control" in menu. Where we made a mistake?
Thanks for all your hints.
Nov 18 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Here is my take on using Source Control (focused on SourceSafe, as that is
what we use):

1. Create the project on one developer's machine.
2. Check into SourceSafe.
3. Get the Solution File from SourceSafe on machine B and open it.

Most of the times, this will sync up with SourceControl and create the web
folder on the new machine, as well as getting latest checked in bits. If you
have problems, you can create the web project in IIS manager and get latest
into this folder. You may end up having to delete the .csproj/.vbproj file
from the web directory, however, as SourceSafe will not overwrite it if it
is not checked out and you will get an error opening it.

Once you have it on box 2, write down any issues you had and repeat on all
developer's boxes. Now, everyone can check out and develop.

You then run regular builds to a "dev test" server, where you can test
interim builds. It is up to each developer to make sure that his build works
with all code that is currently checked in before checking in his code. You
can make it a game when someone breaks the build (I have seen a dunce award
that circled around one place, as a game -- the dev held it until someone
else broke the build).

As for your issue, I am not sure why you do not have this, but would venture
you do not have the SourceSafe client bits installed on the machine in
question. SourceSafe has to be installed to get this functionality.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
"Vladimír Kolesnik" <ko******@seznam.cz> wrote in message
news:OL**************@TK2MSFTNGP12.phx.gbl...
Hi, there
we need help concerning setting project under source control.
We want to have a project on the server, and developers in the local network
working on this project. We decided to use strategy officialy called
"Isolated Development". We studied help in Visual Studio .NET called "Web
Projects and Source Control Integration in Visual Studio .NET". First we
created solution on machine: A (server), then added a web project to this
solution. Then on machine B (developer) we want to create a working copy of
the project on the server.

In help we found this method:

To add the Web project to source control
1.In Solution Explorer, right-click the solution node, and then click Add
Solution to Source Control.
2.If a message box appears, click Continue.
3.Provide database location and user logon information as required by your
source control provider.
4.Create a root solution directory on the source control server by
specifying the server location for the solution file.
5.Under the root solution directory, type a name for the project folder that
will contain the master copy of your Web project's files.

Our problem is in the 1.step : we don't have "Add Solution to Source
Control" in menu. Where we made a mistake?
Thanks for all your hints.
Nov 18 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.