VB (not our plugin or any other Source Control System) have several
limitations. One of them is that it can create (open) from source
control only project (vbp), not vbw, or something similal.
Please see part of some discussions about this:
===================================================================
Note1: as you see vbg and vbw files are not added by VB, as it not want
to handle them, and work with SourceControl on project basis. As I
know vbg and vbw files does not have anything useful, and can be
easily recreated. However, if you need them use WinCVS to add them.
Note2: important, opening vbg project never enable option to get
project when project opened, since after that only one project will
appear as controlled. Look at this:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;174650Note3: VB does not vbg files to source control, but not work if vbg
file readonly. If you add vbg to CVS (outside IDE) you should always
checkout it (cvs edit) before opening. Look at:
http://support.microsoft.com/?kbid=183728Also, take look at
http://www.kbalertz.com/technology.aspx?tec=219&pNo=14This things are about SourceSafe, but some problems that appears there
can happen with CVS and our plug-in too.