|
|
|
date: Wed, 11 Jun 2008 07:01:31 -0700 (PDT),
group: microsoft.public.vstudio.sourcesafe
back
Re: Source safe does not check out all items
On Jun 11, 8:51 pm, "Mark Tolonen" wrote:
> "Inictus" wrote in message
>
> news:b246e177-de65-4b56-a74c-b7bed6519079@s33g2000pri.googlegroups.com...
>
>
>
>
>
> > Greetings all. Me and another developer have been using source safe
> > (6.0c) with Visual Studio 2005 for some time now - with no problems.
> > Recently however a problem has arisen. Here's an example of what
> > happens now:
>
> > 1) I open a solution, and check it out and add a new class to the
> > solution, compile and re-check the soultion back into Source Safe.
>
> > 2) The other developer opens up the project, checks it out - HOWEVER -
> > it does not automatically check out the new class that I recently
> > added. It shows up - however it is still checked in. He doesn't notice
> > this however (lets say) and makes some changes, compiles and re-checks
> > in the solution.
>
> > Now we have the DLL after compiling MISSING the new class that I added
> > - and obviously any code referencing this class now has errors.
>
> > When I reload this solution, the class that I added is shown as being
> > deleted. I can reinclude it in the solution and recompile - but why is
> > this happening?
>
> > I've done an Analyze on the database, but no problems were found.
> > What's boggling is that SS has worked just fine for years and this
> > problem has only cropped up within the last few weeks.
>
> > Any ideas?
>
> After you add the new class and check it in, does the other developer every
> do a Get Latest Version on the entire solution before compiling? This
> doesn't happen automatically.
>
> -Mark- Hide quoted text -
>
> - Show quoted text -
I guess I always assumed that it did do a Get Lastest Version when
checking out - I guess we have to get in the habit now of doing this
before checking out. It's just odd that we haven't run into this
problem until 2 weeks ago (or so).
Another question however: I noticed in the Options window of Visual
Studio 2005, under the Source Control/Environment section theres an
option "Get everything when opening a solution or project". Would this
then do a get latest version automatically?
date: Thu, 12 Jun 2008 06:08:30 -0700 (PDT)
author: Inictus
Re: Source safe does not check out all items
"Inictus" wrote in message
news:726560fa-b1fd-4648-afba-0eaf75b6e6c0@d19g2000prm.googlegroups.com...
On Jun 11, 8:51 pm, "Mark Tolonen" wrote:
> "Inictus" wrote in message
>
> news:b246e177-de65-4b56-a74c-b7bed6519079@s33g2000pri.googlegroups.com...
>
>
>
>
>
> > Greetings all. Me and another developer have been using source safe
> > (6.0c) with Visual Studio 2005 for some time now - with no problems.
> > Recently however a problem has arisen. Here's an example of what
> > happens now:
>
> > 1) I open a solution, and check it out and add a new class to the
> > solution, compile and re-check the soultion back into Source Safe.
>
> > 2) The other developer opens up the project, checks it out - HOWEVER -
> > it does not automatically check out the new class that I recently
> > added. It shows up - however it is still checked in. He doesn't notice
> > this however (lets say) and makes some changes, compiles and re-checks
> > in the solution.
>
> > Now we have the DLL after compiling MISSING the new class that I added
> > - and obviously any code referencing this class now has errors.
>
> > When I reload this solution, the class that I added is shown as being
> > deleted. I can reinclude it in the solution and recompile - but why is
> > this happening?
>
> > I've done an Analyze on the database, but no problems were found.
> > What's boggling is that SS has worked just fine for years and this
> > problem has only cropped up within the last few weeks.
>
> > Any ideas?
>
> After you add the new class and check it in, does the other developer
> every
> do a Get Latest Version on the entire solution before compiling? This
> doesn't happen automatically.
>
> -Mark- Hide quoted text -
>
> - Show quoted text -
I guess I always assumed that it did do a Get Lastest Version when
checking out - I guess we have to get in the habit now of doing this
before checking out. It's just odd that we haven't run into this
problem until 2 weeks ago (or so).
Another question however: I noticed in the Options window of Visual
Studio 2005, under the Source Control/Environment section theres an
option "Get everything when opening a solution or project". Would this
then do a get latest version automatically?
--------
It will do a get latest version on the files you specifically check out, but
not across the whole solution.
I've seen but haven't turned on that option, but I believe it will do a get
latest version when you open the project. However, if you have the project
open already and someone else checks in some new changes, you won't see
those changes unless you explicitly perform the get lastest version on the
solution or close and open the solution again.
--Mark
date: Thu, 12 Jun 2008 16:03:43 -0700
author: Mark Tolonen
|
|
