Time to update Visual Studio?

[d.healey]

It's becoming hard to find VS2017, I can no longer see the community edition at Microsoft's website, only a pro version trial.

@Christoph-Hart Is it possible to bring HISE into the new decade and add a VS 2022 export option?

I know we can already use VS 2022 with a bit of fiddling around, but it's not straightforward and requires additional steps for every export.

[Christoph Hart]

Alright. This post (or Davids above) gets 10 upvotes and we all hold hands and jump into 2022 together…

[d.healey]

[A Former User]

@d-healey With my vote, Now it is 10 :) I hope the transition won't be painful :)

[Lindon]

@Christoph-Hart please make it backwards compatible...ha ha ha

[Christoph Hart]

I just installed it and it's super broken, LOL. Autocomplete doesn't work, shows red compile errors where there are none, etc.

I think I'll wait a little bit more...

[d.healey]

@Christoph-Hart What about 2019? We can still get the community version of that.

[A Former User]

@d-healey said in Time to update Visual Studio?:

We can still get the community version of that.

For now ;)

[Christoph Hart]

I‘ll add an exporter using VS2022 so people can export with it just fine, I was just a bit disappointed because it got so much worse as an IDE but I‘m sure they‘ll fix some of these issues (technically VS2022 is still in Preview mode).

Also all new functions that made me curious (clang compilation, hot reload) don‘t work reliably for me so I guess I‘ll stick around VS2017 for some time…

[d.healey]

Something else I'd suggest is disabling IPP by default on all operating systems. Those who want it can enable it but it will make it easier for beginners who are always finding it a stumbling block.