Closed xevilmaxx closed 2 weeks ago
There are some pitfalls with MMI.
Please see the following: https://github.com/MatthewKing/DeviceId/issues/36#issuecomment-901846204
Hi, did you end up resolving this or are you still having issues?
Simply removed MMI dependency and used only core options
On Tue, Nov 7, 2023, 04:52 Matthew King @.***> wrote:
Hi, did you end up resolving this or are you still having issues?
— Reply to this email directly, view it on GitHub https://github.com/MatthewKing/DeviceId/issues/76#issuecomment-1797702711, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEGVOYRAAZFQHGA6UWQLHWTYDGWBTAVCNFSM6AAAAAA6FDOLWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOJXG4YDENZRGE . You are receiving this because you authored the thread.Message ID: @.***>
Hi, Recently i was migrating one of my projects to NET8 RC2. Noted that DeviceId.Windows.Mmi throws an error.
the package which throws the error is included inside DeviceId.Windows.Mmi
by removing MMI reference, at least for windows (11) all seems to work.
The error occurs only on runtime, but compiles fine. Inside build folder there are files like: *DeviceId..dll but no explicitly the dll that throws the error althought i assume its included in DeviceId.Windows.Mmi.dll**
here is my configuration:
Thanks in advance.