- Open multiple solutions in visual studio 2015 drivers#
- Open multiple solutions in visual studio 2015 update#
- Open multiple solutions in visual studio 2015 driver#
That means even if you choose to do your editing in VS 2015, you can choose which toolset VS will use for compiling and linking. If you do not let VS convert the projects to VS 2015, it will use the toolset that was previously defined for each project when you build your code.
Open multiple solutions in visual studio 2015 driver#
In this case, when you build your driver you’ll be using the new project configurations, the new compiler and the new linker. If you agree, the Platform Toolset will be changed to appropriate Win10 versions. When you first open a Windows 8.1 WDK project with VS 2015, it asks you if you want to convert the projects to the new toolset.
Open multiple solutions in visual studio 2015 drivers#
Figure 1-Using VS 2015…but building drivers with the VS 2013 tools The key to making this work is paying attention to the “Platform Toolset” setting in the Configuration Properties (General section) of each project (shown in Figure 1).
Open multiple solutions in visual studio 2015 update#
Even more interesting, after doing this we were able to open that same solution in VS 2013 and build it successfully using the Windows 8.1 Update WDK. Our Configurations (Win 7 Debug, for example) showed up and could be selected just as you would in VS 2013. In other words, we were able to open a (KMDF) driver project created in VS 2013 with the Win 8.1 Update WDK in VS 2015 with the Windows 10 WDK and build the Solution without any problems. In fact, if we were careful and got our settings right, we were even able to switch back and forth between tool sets for projects that were initially created in VS 2013. After installing the new versions of VS and the WDK, here at OSR we were able to build drivers successfully using either tool set. You’ll be happy to know that VS 2015 and the Windows 10 WDK and VS 2013 and the Windows 8.1 Update WDK can live happily side by side on your dev system. OK? You happy? Now we can go on and deal with one or two other details. Just go to Tools… Options… Environment… General… and UNcheck “Apply title case styling to menu bar” and you’ll be good to go. But, in case you find yourself pining away for those menu items THAT SHOUT AT YOU, you can change back to all uppercase easily. As far as I’m concerned, VS 2015 has me right there. Let’s get one absolutely critical point out of the way immediately: They changed the menu bar titles back to upper and lower case by default. So, there’s a lot more in the kit than was there by default previously.
![open multiple solutions in visual studio 2015 open multiple solutions in visual studio 2015](https://i.ytimg.com/vi/5q7C9x5-4PI/maxresdefault.jpg)
The WDK also includes built-in support for targeting 32-bit and 64-bit ARM processors, as well as Windows Mobile platforms. You can use it to build drivers for any desktop/server OS from Windows 7 onward.
![open multiple solutions in visual studio 2015 open multiple solutions in visual studio 2015](https://maciejgudanowicz.gallerycdn.vsassets.io/extensions/maciejgudanowicz/addmultipleprojectstosolution/1.2.0/1618441107964/AddProgressReviewResults.png)
Probably the biggest change is that WDK is now fully integrated. With at least one notable exception (that we dearly hope is fixed soon) the new versions of VS and the WDK are changes for the better.
![open multiple solutions in visual studio 2015 open multiple solutions in visual studio 2015](https://aspblogs.blob.core.windows.net/media/scottgu/Media/image_thumb_7807F968.png)
As Visual Studio (VS) and Windows itself continue to evolve, so does the WDK. A new version of Visual Studio brings along with it a new version of the Windows Driver Kit (WDK).