FIX: Source Code Controlled VFP Project Compiles Slow
ID: Q186356
|
The information in this article applies to:
-
Microsoft Visual SourceSafe, 32-bit, for Windows 5.0
-
Microsoft Visual FoxPro for Windows, version 5.0
SYMPTOMS
When you compile a Visual FoxPro project that is under Source Code Control,
it can take a very long time (as compared to compiling the same project
when it is not under Source Code Control).
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article. This problem was corrected in Visual
FoxPro version 6.0 for Windows.
MORE INFORMATIONSteps to Reproduce Behavior
- Use a computer that has both Visual SourceSafe and Visual FoxPro
installed.
- Make sure that Visual FoxPro is set up correctly for SourceSafe
integration.
- Open the sample project, Tastrade.pjx, which ships with Visual FoxPro.
- In the Project Manager select the BUILD option.
- In the Build Options dialog box select "Build Executable" and then click
OK.
- In the "Save As" dialog box, specify the name and path for the
executable file, then select SAVE to build a Visual FoxPro executable
file.
Note how long it takes Visual FoxPro to complete the build process.
- Add the Project to Source Code Control.
- Repeat steps 3 through 6.
RESULT: Observe that it takes Visual FoxPro much longer to finish the build
process. The actual time depends on the specific computer configuration,
such as processor speed, amount of memory and so forth.
NOTE: The larger a project is the larger the difference between compile
time for when the Project is under SourceCode control as compared to when
the Project is not under SourceCode control.
Additional query words:
Keywords : kbinterop kbSSafe500bug kbVFp500bug kbVFp600fix
Version :
Platform :
Issue type : kbbug
|