Description of problem: Builds are produced with Visual Studio 2008 and 2010. This limits client applications to building with those versions. Customers may like to build with Visual Studio 2012, 2013, or even "14" which is in tech preview. At issue with using older WinSDK kits with newer Visual Studio development systems is the underlying MSVC runtime library use. Visual Studio Run time ------------- -------- 2008 msvc 9 2010 msvc 10 2012 msvc 11 2013 msvc 12 For example, a WinSDK linked with VS2010 uses MSVC 10 run time libraries. If this WinSDK is linked into a customer project built with VS2012 then the WinSDK still uses MSVC 10 run time while the rest of the project will use MSVC 11. Running two MSVC run time libraries in the same executable is a bad practice. Version-Release number of selected component (if applicable): 3.0 How reproducible: 100% Steps to Reproduce: 1. None required. The WinSDK kits do not exist. 2. 3. Actual results: No WinSDK for Visual Studio 2012, 2013 Expected results: WinSDK kits for Visual Studio 2012, 2013 Additional info: Support for this work has been committed upstream.
Verified. qpid-winsdk supports Microsoft Visual Studio 2012.
Fine by me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-1879.html