Does anyone knows how to solve some problems with Interdev and VB6 projects with new TFS Source Control (RC1)?
I'm having problems with FRX files associated with FRM files when I check out the FRM it does not come with the proper FRX file.
In Interdev with webapplications the source control still points to old VSS projects in IIS.
Regards,
Alexandre
We are able to reproduce both of these issues. I am still actively investigating the FRX issue. The InterDev issue is explained below.
FRX ISSUE
-
A possible workaround for the FRX problem is:
After you have modified the form such that an FRX file is produced, checkin the project file first and then checkin the FRM as a separate operation. Doing so will cause the FRX to be added to source control. For some reason if you try to checkin the project and FRM at the same time, the IDE doesn’t always add the FRX to source control.
INTERDEV ISSUE
The fact that IIS is using VSS is as expected. InterDev uses the MSSCCI interface to handle items it is source controlling locally. However, when InterDev is using the FrontPage Server Extensions (FPSE) for a website it defers the source control operations to the IIS being published to. The FPSE within IIS do NOT use MSSCCI for source control. Instead they rely upon a direct OLE connection to the Visual SourceSafe installation that is local to the IIS server (see: http://www.codeproject.com/asp/VSS_and_VID.asp for more information). Therefore, the fact that InterDev is configured to use the TFS MSSCCI plugin has no effect on how the website is actually put under source control since this happens at the IIS server. Furthermore, it does not appear to be possible to have the IIS server utilize Team Foundation version control.
--Ben Ryan
Update on the FRX Issue:
The workaround does not work so well. If you close and reopen the Project, it will revert back to the behavior where it no longer checks out the FRX when you check out the FRM.
The good news is that we have discovered the bug that is causing this erroneous behavior and are close to having a fix ready. The problem stems from an inadequate implementation of the MSSCCI SccPopulateList interface.
--Ben Ryan
"...we are close to having a fix ready."
Is the fix ready/available?
Or, are you waiting to the next beta/release?
BMcK
Was this ever fixed? We are running MSSCCI provider version 1.2, and we isolated several issues relating to SccPopulateList (i.e., it doesn't return a list... just returns one member).
Any info would be greatly appreciated.
