I’m encountering issues while migrating and building our CFU Firmware Update Simulation project from Visual Studio 2019 to Visual Studio 2022. Could you please help with the following?
Issues Encountered:
Linker Error: LNK1181: cannot open input file 'DmfUModules.Library.Tests.lib'
Compiler Warning: C4013: 'DMF_Utility_EventLogEntryWriteUserMode' undefined; assuming extern returning int
Missing/Incompatible Header: Cannot locate wdf.h in VS2022.
Steps Taken:
Installed Visual Studio 2022: With the "Desktop development with C++" workload.
Installed WDK and SDK: Installed the Windows Driver Kit (WDK) and Windows Software Development Kit (SDK) compatible with Visual Studio 2022.
Retargeted Solution: Retargeted the solution to the latest Windows SDK and toolset.
Updated Include and Library Paths:
Include Directories:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\umdf;C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\shared
Could you please provide guidance on resolving the above issues? Additionally, is it possible to update the project repository on Git with the necessary changes if need.
Hi,
I’m encountering issues while migrating and building our CFU Firmware Update Simulation project from Visual Studio 2019 to Visual Studio 2022. Could you please help with the following?
Issues Encountered:
Steps Taken: Installed Visual Studio 2022: With the "Desktop development with C++" workload. Installed WDK and SDK: Installed the Windows Driver Kit (WDK) and Windows Software Development Kit (SDK) compatible with Visual Studio 2022. Retargeted Solution: Retargeted the solution to the latest Windows SDK and toolset.
Updated Include and Library Paths:
Include Directories:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\umdf;C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\shared
Library Directories
C:\Program Files (x86)\Windows Kits\10\Lib\10.0.26100.0\um\x64
Could you please provide guidance on resolving the above issues? Additionally, is it possible to update the project repository on Git with the necessary changes if need.
Thank you for your support.
Kind Regards
Chandra Shekar C