
 Rank: Guest Groups: Guest
Joined: 9/17/2007 Posts: 11,670 Points: -1,200
|
Date parsed: 28/08/2007 22:36:47 Date: Tue, 28 Aug 2007 14:36:47 +0800
This is a multi-part message in MIME format.
------=_NextPart_000_0056_01C7E980.DCD6F870 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi All,=20
Can anyone tell me where can I find the specification of .NET sln file, = as we're about to change our sourc control from Perforce to ClearCase, = which the source control information seems embedded in the solution file = but I don't know how to modify it.=20 Thanks in advance. ------=_NextPart_000_0056_01C7E980.DCD6F870 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.6000.16481" name=3DGENERATOR> <STYLE></STYLE> </HEAD><FONT size=3D2> <BODY> <DIV>Hi All, </DIV> <DIV> </DIV> <DIV>Can anyone tell me where can I find the specification of .NET = sln=20 file, as we're about to change our sourc control from Perforce to = ClearCase,=20 which the source control information seems embedded in the solution file = but I=20 don't know how to modify it. </DIV> <DIV>Thanks in advance.</DIV></BODY></HTML></FONT>
------=_NextPart_000_0056_01C7E980.DCD6F870--
|

 Rank: Guest Groups: Guest
Joined: 9/17/2007 Posts: 11,670 Points: -1,200
|
Date parsed: 31/08/2007 12:32:13 Date: Fri, 31 Aug 2007 16:32:13 -0400
Jeremy,
I haven't seen a case where you would need to manually edit the SLN file. The source control bindings are controlled by Visual Studio.
To change the source control bindings for your project(s)/solution, go to File > Source Control > Change Source Control.
The other option is to remove all the bindings, then right-click on the solution and choose "Add Solution to Source Control...", specifying your new source control.
I'm sorry to hear about ClearCase <g>. As an aside, have you looked at Team Foundation Server?
Hope this helps,
Steve - dotneticated.com
"Jeremy" <arcjeremy@gmail.com> wrote in message news:O2kOQ3T6HHA.2380@TK2MSFTNGP02.phx.gbl... Hi All,
Can anyone tell me where can I find the specification of .NET sln file, as we're about to change our sourc control from Perforce to ClearCase, which the source control information seems embedded in the solution file but I don't know how to modify it. Thanks in advance.
|

 Rank: Guest Groups: Guest
Joined: 9/17/2007 Posts: 11,670 Points: -1,200
|
Date parsed: 06/09/2007 22:25:36 Date: Thu, 6 Sep 2007 14:25:36 +0800
Thanks Steve.
Chosing ClearCase is a company decision, personally I'd prefer the Microsoft's solution. It's fine for a single solution to change source control by Visual Studion but it's terrible when there're hundreds of projects. This is why I need to maually edit these SLN files, thinking a batch file to change them all might be better.
Jeremy
"Stevanich" <dotneticated@community.nospam> wrote in message news:%23RA7N4A7HHA.1148@TK2MSFTNGP05.phx.gbl... > Jeremy, > > I haven't seen a case where you would need to manually edit the SLN file. > The source control bindings are controlled by Visual Studio. > > To change the source control bindings for your project(s)/solution, go to > File > Source Control > Change Source Control. > > The other option is to remove all the bindings, then right-click on the > solution and choose "Add Solution to Source Control...", specifying your > new source control. > > I'm sorry to hear about ClearCase <g>. As an aside, have you looked at > Team Foundation Server? > > Hope this helps, > > Steve - dotneticated.com > > "Jeremy" <arcjeremy@gmail.com> wrote in message > news:O2kOQ3T6HHA.2380@TK2MSFTNGP02.phx.gbl... > Hi All, > > Can anyone tell me where can I find the specification of .NET sln file, as > we're about to change our sourc control from Perforce to ClearCase, which > the source control information seems embedded in the solution file but I > don't know how to modify it. > Thanks in advance. >
|