Loading the BAML file that goes with the application yields the result below. Even though it's badly broken it's still interesting to see how even a fax app got re-imagined in Avalon.
4039 Fax form
4039 Fax form
Originally this app should have been loaded through fxssendui.exe in the I386 folder, but it simply refuses to show anything.
Loading the BAML file that goes with the application yields the result below. Even though it's badly broken it's still interesting to see how even a fax app got re-imagined in Avalon.
Loading the BAML file that goes with the application yields the result below. Even though it's badly broken it's still interesting to see how even a fax app got re-imagined in Avalon.
Re: 4039 Fax form
Bow that's interesting! I never would have guessed the fax app of all things to be redone! Is it even usable at all?
Re: 4039 Fax form
Sadly, it isn't. It throws a NullPointer as soon as it starts. Somehow (and this might be because of the way I loaded this) it fails to register an element since it's not initialised.
-
Windows OS
- Posts: 455
- Joined: Tue Jul 08, 2014 9:43 pm
- Location: DLL Hell, United States
- Contact:
Re: 4039 Fax form
Is there a possibility for you to fix fxssendui.exe? Maybe that will make the app, at least, semi-functional.
Re: 4039 Fax form
I'm afraid not. Avalon throws an exception on loading the BAML. Maybe this is because the original Applications add a namespace map to external assemblies (i.e. assemblies that where somewhere in the company's network at the time) that probably have some additional features the build's assemblies do not have.