Application Compatibility and Startup Questions
-
Good people, I have designed an application that uses WPF and targets the .NET 3.5 library. Can I assume that, if the person downloads .NET 3.5 (full or client profile), my application can run on Windows XP, Vista and Windows 7? Also, sometimes during startup, while my application is showing the splash screen, if the user clicks around or attempts to do something else - like return to another application while mine is loading, my application will fail to load and throw an error of some sort. Any ideas on what's happening or what I should do? Thanks in advance for any insight or information you can provide.
-
Good people, I have designed an application that uses WPF and targets the .NET 3.5 library. Can I assume that, if the person downloads .NET 3.5 (full or client profile), my application can run on Windows XP, Vista and Windows 7? Also, sometimes during startup, while my application is showing the splash screen, if the user clicks around or attempts to do something else - like return to another application while mine is loading, my application will fail to load and throw an error of some sort. Any ideas on what's happening or what I should do? Thanks in advance for any insight or information you can provide.
BlitzPackage wrote:
Can I assume that, if the person downloads .NET 3.5 (full or client profile), my application can run on Windows XP, Vista and Windows 7?
Is it likely? Yes, assuming you haven't used any OS version specific functions, P/Invokes, etc. Though check up on the client profile/full version of the framework thing. Is it certain? No. Test, test, and test again on all three, and still be prepared for the odd one that doesn't work.
BlitzPackage wrote:
Also, sometimes during startup, while my application is showing the splash screen, if the user clicks around or attempts to do something else - like return to another application while mine is loading, my application will fail to load and throw an error of some sort. Any ideas on what's happening or what I should do?
Use the debugger. The name of the exception thrown may help. If you this doesn't help, post the exception details here, and a small, relevent amount of code from that location in your project, and we can all take a look.