Wishing to use UWP instead of MFC for an app with a legacy DLL driver (Industrial PC)
Back to developing on Windows after a few years, for a simple app (motion control in a manufacturing environment), I would like to move on from MFC I was using back then, and adopt UWP (also because I'll need to interface with databases, and wanted to adopt modern tools).
But I'm stuck with the following basic issue: I need to use a legacy DLL - a good old one with __declspec(dllimport) __stdcall C-style functions to access a dedicated hardware.
When I create a new MFC project, all is easy and smooth...
But when I start from a C++ UWP platform, my test program cannot start:
- I am able to add the (x64) .h, .lib and .dll files to the project, and everything links ok.
- but when I try to run (debug) the app, the app won't start, and I get the following error message:
"Unable to activate Windows Store app '.......' The SAMPLE.exe process started, but the activation request failed with error 'The target process aborted before activation completed.
Is there an easy solution? Or is it not possible to use a legacy DLL in this way? (I have no access to the DLL's source code)
I would like to move on from MFC I was using back then, and adopt UWP (also because I'll need to interface with databases, and wanted to adopt modern tools).
UWP has been replaced by WinUI 3
(or you can also use WPF for modern UI)
You may find the following discussion of Microsoft UI choices to be of interest.
Sign in to comment