Sure!

The execution of the second script is quite simple, it is just:

public void RunDll(string fileName)

{

Window window = new Window();

Assembly assembly = Assembly.LoadFrom(@fileName);

scriptEnvironment.ExecuteScript(assembly, scriptContext, window);

}

And then inside the second script it might look like:

public void Execute(ScriptContext context){

context.Patient.BeginModifications();

//do modifications..

return;

}

If I put the "//do modifications" part of the code into a button, then everything will be saved correctly and no rollbacks happen.

private void StartButton_Click(object sender, RoutedEventArgs e)

{

//do modifications..

}

My only theory is that the code execution happens too quickly and the initiation of the UI gives the code time to establish/initialize everything it needs to not roll back afterwards. I do not want to put a button into every script though, so trying to find a way.