Skip to main content
Up and Coming
March 12, 2017

Visual Studio 2017 support ETA

Just wanted to see if you guys had an ETA for adding in Visual Studio 2017 projects/libs, etc., since it officially released a few days ago?  I'm looking to plan out / schedule my own migration to 2017 (from 2010), which of course depends on the 3rd party SDKs I'm working with adding support.

    2 replies

    Inspiring
    March 13, 2017
    I could convert my VS 2015 project without any issue. No actual conversion was necessary, it seems to be valid to open the solution files with either VS 2015 or VS 2017. Due to the many bugs in VS 2017 I decided to have both versions side-by-side for the time being. I did not encounter any problem with that approach yet.

    My project uses the Oculus Core SDK plus Avatar and Platform SDK.
    sbdykesAuthor
    Up and Coming
    March 14, 2017
    Yep, and as I understand it VS2015-built libraries are actually compatible with 2017 as well, so one could just link against those and be good-to-go for now.  But I suppose my question was more along the lines of "when will Visual Studio 2017 be officially supported?", "officially" meaning they have built, tested and verified against 2017 by the Oculus folks.