SosScc.dll is linked to missing export SHGetFolderPathA...

[CoderX2]

On Windows NT 4.0, the Visual Studio 6 IDE integration is broken because LoadLibrary fails to load SosScc.dll due to the fact that it is [incorrectly] trying to import SHGetFolderPathA from shell32.dll when it should be using shfolder.dll (just as sos.exe does).

I would really appreciate a fix for this as soon as possible, thanks.

[lbauer]

What version of SourceOffSite client are you using?

Are you using VB 6?

[CoderX2]

I'm trying to use SourceOffSite version 4.02 with Visual Basic 6.

[CoderX2]

Any update on the status of this issue?

It prevents any SOS integration from working within Visual Basic 6 on NT 4.

[CoderX2]

I guess I'm really confused because I don't understand the hold-up of fixing this issue.

The DLL was not compiled properly to be sufficiently cross-platform to run on NT 4, which is supposed to be a supported platform.

Additionally, Microsoft recommends linking against "shfolder.lib" and NOT "shell32.lib" for the "SHGetFolderPath" function regardless of target operating system.

[corey]

We're looking into this issue now since we've not had any reports of a problem before. I'll post a followup as soon as we have more information.

[lbauer]

We did have a previous report of integration problems with Visual Basic 6 on Windows NT. We were able to reproduce the problem -- in this case, VB was crashing. We're not sure why, because we didn't make any changes to the IDE integration, but obviously something broke.

SOS 3.5.3 seems to work, though, so we'd suggest you downgrade your client. SOS 3.5.3 clients can communicate with SOS 4.0.2 servers.

You can download SOS 3.5.3 from our website at this URL (scroll to the bottom of the page):

http://www.sourcegear.com/sos/downloads.asp

Sorry for the inconvenience. We've got this logged as a bug and will add it to the list of things to consider for SOS 4.1, due out this fall.

[CoderX2]

So, in conclusion, I did help you reproduce this bug?

The fix is to recompile "SosScc.dll" with the proper import library for "SHGetFolderPathA" (try upgrading your version of the Platform SDK header and library files).

[lbauer]

We knew there was bug, but didn't know why. You've given us a some helpful clues on what to look for when we fix this.

[CoderX2]

The bug is still present (SosScc.dll links against the wrong library) in the latest version (4.1) of the SourceOffSite client.

When is this going to be fixed?

[lbauer]

This didn't make it into 4.1. We don't have a timeframe for our next release, but this bug is still logged in our bugs database.