I am using Vault 5.03 and my application is using the MSSCCI interface of "VS2003 Compatible Client" which works fine on Windows XP.
Run the same function on Windows Vista and it just crashes completely in the VaultAPI DLL.
It doesnt seem to matter which function I am calling "SccGetProjPath" or "SccOpenProject", it just crashes. I have finally narrowed this down to just Vista (possibly Win7 as well). I have tried running in compatibility mode and admin but nothing helps; so it must be an issue within the Vault DLL itself.
Can you help, can you confirm that this works fine? Please!!
VS2003 Comp Client Crashing on Vista
Moderator: SourceGear
-
coderanger
- Posts: 35
- Joined: Mon Feb 15, 2010 6:11 pm
Re: VS2003 Comp Client Crashing on Vista
Well trying to create a simple test app to show you, i get a .net exception in vault after I have selected the login user and chosen the repositiory. This works fine with SourceSafe if you change the LoadLibrary to the VSS DLL.
This appears to be a different issue ... perhaps with that fixed it may highlight the original problem or perhaps it may fix it.
Really would love your help on this as we have to move our internal tools onto Vault which we are now using for Visual Studio (and love it!!!) ... its only our code we are having a problem with now
This appears to be a different issue ... perhaps with that fixed it may highlight the original problem or perhaps it may fix it.
Really would love your help on this as we have to move our internal tools onto Vault which we are now using for Visual Studio (and love it!!!) ... its only our code we are having a problem with now
- Attachments
-
- SccTest.zip
- VS2008 Test Solution
- (20.29 KiB) Downloaded 180 times
Re: VS2003 Comp Client Crashing on Vista
coderanger,
My guess is you're not properly seeding your binary with the correct .NET version for the Vault Classic Client to run correctly. In order to leverage the existing Vault libraries, the Classic client will load a CLR into its address space. The default is to run .NET 1.1 (to support older IDEs). Since Vista and Windows 7 will not be pre-loaded with .NET Framework 1.1, you will need to create a config file in order to load the correct runtime. Note, debug (from within an IDE) vs. release builds will require different config files.
See http://support.sourcegear.com/viewtopic ... t=0#p54615 and http://support.sourcegear.com/viewtopic ... =15#p54781 for some additional info.
My guess is you're not properly seeding your binary with the correct .NET version for the Vault Classic Client to run correctly. In order to leverage the existing Vault libraries, the Classic client will load a CLR into its address space. The default is to run .NET 1.1 (to support older IDEs). Since Vista and Windows 7 will not be pre-loaded with .NET Framework 1.1, you will need to create a config file in order to load the correct runtime. Note, debug (from within an IDE) vs. release builds will require different config files.
See http://support.sourcegear.com/viewtopic ... t=0#p54615 and http://support.sourcegear.com/viewtopic ... =15#p54781 for some additional info.
Jeff Clausius
SourceGear
SourceGear
-
coderanger
- Posts: 35
- Joined: Mon Feb 15, 2010 6:11 pm
Re: VS2003 Comp Client Crashing on Vista
Wow thanks. I am so glad you posted that as I never found it when searching, config file solution worked perfectly so am well happy now! Cheers 