Hmmm. Is the name of your executable the same for both the 32 and the 64 bit targets?
Note that the run-time license key string depends on the executable name.
What kinds of executable are they? Is there a WPF System.Windows.Application class? What is the name of the assembly that defines your Application class? Did you use that name when you generated the run-time license key for each executable?
If you are building a Windows Forms app or are deploying a DLL into an unmanaged application, there might not be a value for the static/shared property System.Windows.Application.Current. If that is the case, you can just create an instance of a trivial class that inherits from System.Windows.Application; creating it will automatically set Application.Current.
I hadn’t know before that you were building a Windows Forms app. I just wanted to confirm that you had created a subclass of System.Windows.Application and created an instance of it.
Are you using the same GoXam DLL in both applications? And the name of the EXE or DLL that holds that Application class is the same for both applications?
I just created a new C# Windows Forms .NET Framework 4.8 application, added an ElementHost for WPF controls, copied the State Chart .xaml and .xaml.cs files into the project, and set the ElementHost’s Child to be an instance of the StateChart UserControl.
That sample code does have a couple dependencies on the GoWpfDemo sample framework, so I did have to make some trivial changes to the C# code. But it is basically unmodified from the GoXam kit.
No, changing the target should not require replacing the license key string, as long as the major/minor version number has not changed. As you have already seen with the sample that I gave you.