Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Foxbin2prg problem - maybe
Message
De
22/01/2015 17:56:07
 
 
À
20/01/2015 15:52:32
Information générale
Forum:
Visual FoxPro
Catégorie:
Source Safe Control
Versions des environnements
Visual FoxPro:
VFP 9 SP2
OS:
Windows Server 2012
Network:
Windows 2008 Server
Database:
MS SQL Server
Application:
Web
Divers
Thread ID:
01613983
Message ID:
01614140
Vues:
40
J'aime (1)
>After using foxbin2prg, I have been very happy with it. However we have one issue which started when we installed foxbin2prg, but I am not sure where the problem actually is. We use SourceOffSite around VSS and never had even a hiccup. Now whenwe checkin anything, if the checkin comments are more than 50 or so characters, the checkin crashes and foxbin2prg does not update the .sc? (or vc, etc) file, and changes can be temporarily lost.
>
>The foxbin2prg error screen is attached.

Hi Tuvia:

I'm doing some testing with SourceSafe, and I'm getting a different error than yours that happen when opening a test project:
Error 11, Function argument value, type, or count is invalid.
evaluarconfiguracion, 1389
lo_Configuration.Add( lo_CFG, lc_CFG_Path )
lcConfigFile = [foxbin2prg.cfg]
lc_CFG_Path = []
lcValue = [.F.]
FoxBin2Prg: [C:\DESA\FOXBIN2PRG\FOXBIN2PRG.FXP] (EXE Version: v1.19.41)
tc_InputFile = [K]

Source file: K
I've fixed this error (only SourceSafe compatibility affected), and uploaded as v1.19.42 Preview 1 in VFPx:

Could you test with this version?

https://vfpx.codeplex.com/downloads/get/1422428

This is what I've tested in SourceSafe:

1) User 1: I've created a new form and a classlib with a custom class and a form class, and checked in all (VSS automatically generated all sca/vca texts)

2) User 1: I've modified the form class in the class library, and added a button (cmd2) but didn't checked in to simulate a conflict later

3) User 2: Then I simulated a second VSS user that join the project in a different directory, modify the same form in the same library, add a second button (cmd3) to the form and checked in

4) User 1: Switched to session 1 with the pending change of the form of step 2, tried checking in and VSS detected the conflict so showed the conflict resolution window on which I manually merged with the changes of User 2, so I now have existing cmd2 and the new cmd3

5) User 1: Once changes have saved, VSS have automatically regenerated the binary of the class according to the modified vca in previous step 4, and I have added a 215 characters comment before checking in, without errors

6) Finally, I opened the form of the classlib with the VFP IDE and all changes are there. Successful merge.

So, apparently in VSS it is working ok now.

Regards.-
Fernando D. Bozzo
Madrid / Spain
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform