Last best commit for VS2022....?
-
OK so I'm stuck back on an April 2025 commit because of the "global modulators breaking presets" bug... as I have a reasonably imminent product update to support...
But I'm at that stage where its all demo videos, marketing materials, distributor release scheduling etc. etc. Which Im sure many of you know involves a fair amount of "waiting around"....
I also have a Horizen update looming over me, so I thought I'd get a start on some of the functionality changes, which I've started to do, but now (or soon) it will require a version of HISE that supports the compiled "Hardcoded synths" functionality - which is not in my current commit.
So as may be clear by this long winded explanation I'm very reluctant to go to the latest set of commits that require V2026, so......
Can any one tell me the most recent working commit that I can build using my current set up of VS2022???
Which as a general question makes me think it would be a good idea to have some documentation that includes the required/advised 3rd-party products and versions in each commit, perhaps Claude can help?
-
@Lindon you can still use VS2022 with the latest commits, you just need to set the compiler settings to use that version - the new default is VS2026, but I didn't want to be too aggressive with the migration so the old toolset is still usable.
-
@Christoph-Hart said in Last best commit for VS2022....?:
@Lindon you can still use VS2022 with the latest commits, you just need to set the compiler settings to use that version - the new default is VS2026, but I didn't want to be too aggressive with the migration so the old toolset is still usable.
Ok great, which compiler settings?
-
@Lindon the one in the HISE settings (either under compiler or development I'm currently to lazy to load up HISE lol). You can choose between VS2026 and VS2022 there and it should create the projucer file for exporting this accordingly. It will complain if you build HISE with a different VS version though, so if you compiled HISE with VS2022 and then try to export a VS2026 project, you'll be screamed at rightfully so.