Do not use Visual Studio 16.10.0 or 16.10.1 or 16.10.2 with DMF due to link regressions

[samtertzakian]

We have received many reports of various linker errors when people use Visual Studio 16.10.0 or 16.10.1.

The Visual Studio Team has been correcting the issues. Please try 16.10.2 and above to see if it corrects the issues. If not, please use Visual Studio 16.9.x.

These are not DMF specific issues...even people not using DMF have reported these issues.

To get older Visual Studio, please visit:
https://docs.microsoft.com/en-us/visualstudio/releases/2019/history

To see more information about this issue, please visit:
#166

This week, I have been addressing various versions of these issues and 100% of the issues have been resolved by people installing Visual Studio 16.9.8.

One of the issues is that when people have received these errors, they have tried to "fix" them by adding libraries and making other changes. But, these changes have made things worse...drivers link but then during runtime weird errors happen which prevent driver images from loading.

DMF makes heavy use of the C runtime library in the DDK. That is why it is so sensitive the regression. Drivers that do not use the runtime library may not see the issue.

[samtertzakian]

16.10.3 has been released already which corrects some issues. But, a new release is coming to fix remaining issues. Please see this link for details:

https://developercommunity.visualstudio.com/t/compile-errors-for-external-headers/1433124?from=email

[samtertzakian]

Closing issue for now as it appears to be resolved.

[samtertzakian]

One more update for this issue:

There is a new update (out today) which corrects the last known issues related to linker.

https://developercommunity.visualstudio.com/t/compile-errors-for-external-headers/1433124?from=email&viewtype=all#T-ND1474634

[samtertzakian]

Closing issue as it seems to be have been resolved.