> > Looking to the future, this may change. For Crypto++ 5.7 or 6.0 may switch > to VS2010 or VS2012. We have to be careful how far we leap forward because > those tools are expensive, and I don't want to create barrier for entry as > a Crypto++ user. That is, if an average developer has VS2010 (but not > VS2012 or VS2015), I want them to be able to download a run with it. > > >> I also think that VS 2010, VS 2012, VS 2013 and VS 2015 need to be >> supported (-> no warnings during compilation at standard W3, 5.6.2 did this >> on all supported versions (up to 2012)). >> > So, stumbling across http://blogs.msdn.com/b/vcblog/archive/2010/03/02/visual-studio-2010-c-project-upgrade-guide.aspx and looking through past user group posts on "Visual Studio upgrade", it looks like Visual Studio 2010 will likely be the upgrade target.
Searching for "Visual Studio upgrade" shows there's a lot of problems (relatively speaking) when the VS target version lands at or crosses the VS2010 boundary. My thinking is we can iron out the wrinkles caused by the Microsoft changes to the underlying tools that occurred in 2010. Those who want to upgrade further, like to VS2012 or VS2015 are free to do so. And by only taking a baby step (VS2008 to VS2010), we are not raising the barrier for entry (or raising it too drastically). I *think* there are some related unanswered questions, like what to do with the DLL related projects. We'll get to them in a separate thread. (I don't oppose the DLLs; but the way its set up now for the FIPS/non-FIPS gear creates too many damn problems for users). The change won't occur until Crypto++ 6.0, however. Any thoughts or comments? Jeff -- -- You received this message because you are subscribed to the "Crypto++ Users" Google Group. To unsubscribe, send an email to [email protected]. More information about Crypto++ and this group is available at http://www.cryptopp.com. --- You received this message because you are subscribed to the Google Groups "Crypto++ Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
