You're right Edhy.

I'm still straddling the world of VFP/.NET.... Our VFP application just underwent a SQL database backend replacement and this SF app is being used to maintain/update the SQL database. So, I'm still pretty green as far as .NET application runtime knowledge.

Thanks for your help.

Bill

Hi William,

You have to understand how dot net will look for the assemblies when loading, you can search the MSDN for more complete answer, but basically, your .EXE will do this:

1. Look for required assemblies in the same folder as the .EXE
2. If not found, then it will look in the GAC.

Using GAC has some tricky issues based on the version of the assemblies, so I have been using my .EXE folder instead and never had issues when releasing updates to my applications.

Glad it is working for you now.

Edhy Rijo

> Try copying the SF dlls to the same directory

Bingo, that did it.

Is there anyway to make the DLL's visible to the EXE regardless? Is there a project reference/setting that can be added to the EXE that will tell it to find the DLL's in a particular local folder?

Thanks!

This is part of the code to run my version of this class, in my case DataProgress.vb

Dim DDTPackageName As String = "InsuranceBrokerSystemDDT.pkg"
Dim DDTPackagePassword As String = "MyPassword"
Dim loDataUpdateProgress As New DataProgress(MicroFour.StrataFrame.Data.DataLayer.DataSources("").ConnectionString(), DDTPackageName, DDTPackagePassword, DataDeploymentOptions)
loDataUpdateProgress.TopMost = True
UpdateDatabase = loDataUpdateProgress.ShowDialog()
loDataUpdateProgress.Close()
loDataUpdateProgress.Dispose()

Please post the code you are using show the form?

Edhy Rijo

Try copying the SF dlls to the same directory location where you have your exe files on a local non-development system.

-Larry

When I copy the application EXE to the local desktop, I'm getting the same results, the process shows up in task manager for a few seconds, then goes away.

Hi William,

I build the SampleDataInstallerClass into my application's main assembly (.exe), and I don't run anything from a network patch since some .NET programs may need custom security settings to be able to run from a network path.

I install my application locally in each workstation and my logic is that any workstation can update the database structure from the main application which I control access to it via the RBS.

Edhy Rijo

One more thing, the application EXE does run on a workstation with the SF development environment.

This Setup.exe doesn't have an "application" folder, it's just being used to install the SF DLL's and SMO's needed to run the SampleDataInstallerClass EXE on the workstation.

The application EXE will be run from a network location.

My mistake, the MicroFour StrataFrame UI.dll is actually what's being installed.