Seems like an annoyance as MSFT is sort of moving toward nuget based WDKs as the default.
- investigate how visual studio determines that it should use the nuget WDK.
- based on that investigation, determine the feasibility of wdkenv doing something similar,
One of the obvious problems is that a user (the dev) could call wdkenv from any place in the filesystem hierarchy, while nuget WDK installs are specific to a particular visual studio project or solution.
Seems like an annoyance as MSFT is sort of moving toward nuget based WDKs as the default.
One of the obvious problems is that a user (the dev) could call wdkenv from any place in the filesystem hierarchy, while nuget WDK installs are specific to a particular visual studio project or solution.