0

I have an application that downloads a project from Visual SourceSafe, checks out the last executable, compiles the app and checks in the executable. The application works fine on Windows 7 64-bit OS with a 32-bit version of Excel installed but must be run on Windows Server 2008 R2 to actually build the code in question.

My problems is that the application uses a spreadsheet as a database and the server has the 64-bit access database engine installed.

This leads to a big problem in that the Microsoft.VisualStudio.SourceSafe.Interop is only a 32 bit process and the spreadsheet can only be opened using a 64-bit driver.

I am looking to shim the 32-bit Visual Studio processes but cannot find an example of how to do this within a .NET assembly.

I even tried to create a separate class library in the hope that the 64 bit application could call a 32 bit class library but it cannot.

Any tips and examples would be greatly appreciated.

Lee Z
  • 802
  • 2
  • 13
  • 39
  • 64 bit application cannot call 32 bit dll. You may consider calling a 32 bit exe in your 64 bit app to get sourcesafe projects. – Rachel Mar 24 '14 at 06:04
  • Yes, that is why I am asking this question on how to shim/convert the Microsoft.VisualStudio.SourceSafe.Interop dll to be a 64 bit process. An executable will not work since the original source is a dll. I attempted to use ILSpy to reverse code the dll but there were too many errors and events missing. Wondering if a WCF service might work or if anyone has done this before and can offer pointers. – Lee Z Mar 24 '14 at 10:52

1 Answers1

0

The only way that we could get around this limitation was to setup a 32-bit OS and make everything run as 32-bit.

Lee Z
  • 802
  • 2
  • 13
  • 39