The way we make sure the programmers check in code (even if it's not working) is to maintain to separate VSS databases: one for production code and the other for development. The VSS databases are maintained on an application server, physically separate from our file server. If your team is...
Are you checking in the associated .FRX too? If so, make sure they check out both the .FRM and .FRX.
Also, does each programmer keep their own .VBPs? If so, you might want to send an email to each of the programmers informing them of the addition of the control.
Hope this helps.
When I did a migration, I made sure everyone had either checked in their code, or undid their checkouts (use status search to ensure) and had everyone logout of VSS (use the VSS admin to determine this).
Next, turn off the VSS folder share so no one can access VSS. Copy that whole folder and...
You have two options, code your solution, or buy a 3rd party application.
Microsoft has information on how to do this at:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvss/html/vssauto.asp
The only application I've seen that will do this is SourceVizor...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.