Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
tools
vsnet.act
vsnet.debugging
vsnet.documentation
vsnet.enterprise.tools
vsnet.general
vsnet.ide
vsnet.jlca
vsnet.servicepacks
vsnet.setup
vsnet.vsip
vsnet.vss
vsnet.vstools.office
vstudio.development
vstudio.extensibility
vstudio.general
vstudio.helpauthoring
vstudio.setup
vstudio.sourcesafe
  
 
date: Thu, 2 Feb 2006 11:11:57 -0800,    group: microsoft.public.vsnet.vss        back       


Problems with VSS 6.0d and VS 03   
We are using Visual Studio 2003 and Visual Source Safe 6.0d, WXP clients and 
W2K server to develop a database application.  Each developer is working on 
a different project under a single solution.  One developer has been having 
a problem with a form not compiling, if she changes something, or if we 
delete the dll from that project and rebuild, it will work for a while but 
eventually similar (but not the same) errors will crop up again.  The errors 
point to not being able to see a base form (she has a form which inherits 
from a form in a shared project, which then inherits from one of her forms 
that has some datagrid functions built into it), but each time the errors 
crop up they are different.

The problems we are having which I don't understand are that when her 
project breaks, I can't compile even though I haven't changed anything nor 
checked out her project.  After fixing it on her workstation (albeit 
temporarily) I did get latest, deleted the dll on my workstation and was up 
and running again.  But now I am having the problem where every two or three 
compiles it stops compiling and I get error messages from her project, again 
even though I haven't touched her project or checked anything out.

My questions are: how can it be that when her project has problems, my 
project starts having problems even though nothing has changed with my copy 
of her project?  Is VSS somehow updating the project without me doing 
anything?

I suspect that it has to do with versioning, in that deleting the old dll to 
force a rebuild sometimes make the problems go away.

The specific error messages have to do with things like buttons not being 
visible (not declared), what's odd about them is that the messages are 
different.  But they all point to a single form not being seen for some 
reason, sometimes if I go in, check out the form, change something trivial 
(even a comment) and then check it back in it will compile again.

I realize that this is sparse detail but has anyone seen anything like this 
before and have any idea what may be going on?

Thanks in advance;

DCraig
date: Thu, 2 Feb 2006 11:11:57 -0800   author:   DCraig

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us