Updates to allow building with Visual Studio 2022

[MrDavid949]

Please accept this pull request which updates all project and solutions to enable building with Visual Studio 2022. Also fix CQ depth issues and correct a problem where QP creation will fail on adapters where maxSQ and maxRQ depths are not equal.

[MrDavid949]

@microsoft-github-policy-service agree

[MrDavid949]

Is anyone going to review this?

[weypro]

First of all, thank you for adding VS2022 support! I'm just trying to use Network Direct with VS2022.
When I tried to build the project, I noticed it's configured to 'Use MFC in a Static Library', but the library actually works fine with just 'Use Standard Windows Libraries'. Could you update the project settings to remove the unnecessary MFC dependency?
This would help other users who want to try Network Direct with VS2022 without pulling in unneeded MFC dependencies.

[MrDavid949]

First of all, thank you for adding VS2022 support! I'm just trying to use Network Direct with VS2022. When I tried to build the project, I noticed it's configured to 'Use MFC in a Static Library', but the library actually works fine with just 'Use Standard Windows Libraries'. Could you update the project settings to remove the unnecessary MFC dependency? This would help other users who want to try Network Direct with VS2022 without pulling in unneeded MFC dependencies.

Hi, without the static MFC linking, the executables created will work on the system on which they were built, but if you take them to another machine they will not work because they will have a dependency on VisualC runtime. Using static MFC linking allows the .exe files to run on any machine with no dependencies on a runtime package.

[weypro]

Thanks for the explanation. However, I suppose there's a misunderstanding here. Static MFC linking is completely different from MSVC Runtime dependencies. If you want the exe to run without dependencies, you should use the /MT compiler flag to statically link the Runtime.

[MrDavid949]

Thanks for the explanation. However, I suppose there's a misunderstanding here. Static MFC linking is completely different from MSVC Runtime dependencies. If you want the exe to run without dependencies, you should use the /MT compiler flag to statically link the Runtime.

Oh yes, you are right. The dependency was in fact on the runtime and not MFC. I will remove MFC and set the code generation runtime option to not use DLL as you suggested.