Hi Stefan,Thank you for you answer. Yes, I tested 2018.04 on VS2015 and VS2017 and it does compile and work on both versions. In fact, this is exactly why I ask: I would prefer keeping only one version of VS.
I'm aware that there's some problems if we use a unsupported version of VS, but isn't it the point of a toolchain? TBH, it's the first time I hear about VS toolchains so it's not entirely clear to me what they can do. I thought that I could use a single VS version (2017) to build:
* 2016.11 using VS2015 toolchain * 2018.04 using the latest VS2017 toolchain Are you telling me I can't? Nil Le 2018-05-09 à 06:00, Dinkelacker, Stefan a écrit :
Hi, support for VS2017 was introduced after the 2016.11 release and AFAIR we had to upgrade some external dependencies and adapt our code. So this will not work out of box with 2016.11. However, we're working with VS 2017 over a year now and it works well even with the upgrades of VS 2017, tested up to v15.6. The upcoming 2018.04 release will fully support VS 2015 and 2017. Best, Stefan -----Original Message----- From: Nil Goyette [mailto:[email protected]] Sent: Dienstag, 8. Mai 2018 18:04 To: [email protected] Subject: [mitk-users] VS2015 toolchain Hi all, Last year I installed VS2017 to test compiliing MITK 2016.11; it failed (as it should) and it broke my VS2015 for some reasons. I want to test again but I don't want the same problem to happen. Did someone test compiling MITK 2016.11 on VS2017 with the 2015 toolchain? Did it work? Did you need to change a config/property somewhere? Nil
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
