SampleDataInstallerClass -> cross-thread error...

Meanwhile I kicked off my old AMD equipment and own a brand new Intel machine now. BigGrin

I installed all completly new from the scratch, Windows XP Professional, VS 2008 and the newest StrataFrame-Beta.

Unfortunately the problem persists, even with the new machine. It seems not to have something to do with AMD or Intel.

So I took a look what MicroSoft does with the Backgroundworker, which should have something to do with the error. I saw, that the examples from MS avoid any access to the GUI, from inside the doWork-Method. I tried to modify the source code, but found that not a good idea, because I do not want to modify the code again and again with any new release of SF.

I decided to translate the DeployDialogs-MDDDeployMain to C# and to modify it to my needs, using as much of the framework as I could.

private void cboSQLServer_DropDown(object sender, EventArgs e)

{

if (!_ServersLoaded)

{

_ServersLoaded = true;

//-- Clear the combo

this.cboSQLServer.Items.Clear();

//-- Start the thread

this.sqlWorker.RunWorkerAsync();

}

private void sqlWorker_DoWork(object sender, DoWorkEventArgs e)

{

// Do not access the form's BackgroundWorker reference directly.

// Instead, use the reference provided by the sender parameter.

BackgroundWorker bw = sender as BackgroundWorker;

// Start the time-consuming operation.

// e.Result = TimeConsumingOperation(bw, arg);

this.LoadSQLServers(bw, e);

// If the operation was canceled by the user,

// set the DoWorkEventArgs.Cancel property to true.

if (bw.CancellationPending)

{

e.Cancel = true;

}

/// <summary>

/// Loads the available SQL servers into the combo box

/// </summary>

/// <remarks></remarks>

private void LoadSQLServers(BackgroundWorker bw, DoWorkEventArgs e)

{

//-- Show the wait window

bw.ReportProgress(1);

//-- Establish Locals

SQLServerSchema loSQL = new SQLServerSchema();

ArrayList list = new ArrayList();

//-- Cycle through all available servers

foreach (SQLServerInfo loSQLInfo in loSQL.LoadSQLServerList())

{

//-- Add the item

list.Add(loSQLInfo.Name);

}

e.Result = list;

}

private void sqlWorker_ProgressChanged(object sender, ProgressChangedEventArgs e)

{

if (e.ProgressPercentage == 1)

{

this.opgWindows.Enabled = false;

this.opgSQL.Enabled = false;

this.cmdBack.Enabled = false;

this.cmdNext.Enabled = false;

//-- this.cmdCancel.Enabled = false;

this.myWaitwindow.ShowWaitWindow(Localization.RetrieveTextValue("waitWindTxt030"), Localization.RetrieveTextValue("waitWindTxt040"));

}

private void sqlWorker_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e)

{

if (e.Cancelled)

{

this.myWaitwindow.HideWaitWindow();

// The user canceled the operation.

MessageBox.Show("Operation was canceled");

this._ServersLoaded = false;

this.opgWindows.Enabled = true;

this.opgSQL.Enabled = true;

this.cmdBack.Enabled = true;

this.cmdNext.Enabled = true;

this.cmdCancel.Enabled = true;

}

else if (e.Error != null)

{

// There was an error during the operation.

string msg = String.Format("An error occurred: {0}", e.Error.Message);

MessageBox.Show(msg);

}

else

{

// The operation completed normally.

ArrayList servers = (ArrayList)e.Result;

for (int i = 0; i < servers.Count; i++)

{

this.cboSQLServer.Items.Add(servers.ToArray().GetValue(i));

}

if (this.cboSQLServer.Items.Count > 0)

{

//-- Select the first item

this.cboSQLServer.SelectedIndex = 0;

}

this.myWaitwindow.HideWaitWindow();

this.opgWindows.Enabled = false;

this.opgSQL.Enabled = false;

this.cmdBack.Enabled = true;

this.cmdNext.Enabled = true;

//-- this.cmdCancel.Enabled = true;

}

private void cmdCancel_Click(object sender, EventArgs e)

{

if (this.sqlWorker.IsBusy)

{

// Cancel the asynchronous operation.

this.sqlWorker.CancelAsync();

this.cmdCancel.Enabled = false;

}

else

{

try

{

if (_Migrator != null)

{

_Migrator.CancelConversionThread();

_Migrator.Dispose();

}

catch (Exception)

{

throw;

}

finally

{

this.DialogResult = DialogResult.Abort;

this.Close();

}

Maybe you can have a look at it and use it for the framework? OK, you will have to translate it to VB.NET, but this will surely not be a problem for you and this way you can shift my code to a much better one. Smile

Note:

You must be careful not to manipulate any user-interface objects in your DoWork event handler.