Last best commit for VS2022....?

[Lindon]

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?

[Christoph Hart]

@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.

[Lindon]

@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?

[Christoph Hart]

@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.

[Lindon]

@Christoph-Hart well this actually doesnt make any sense to me... you mean this setting right?

So, in order to select this I would need to build HISE .....which is what I need this setting for...its a lovely Catch-22 position....I need ot build the thing in order to set the setting so I can build the thing...

[David Healey]

@Lindon That's just for exporting from HISE. For building HISE I think you can use the 2026 exporter in Projucer and when it opens in VS it will give you some prompt about converting the project for VS22 - I haven't tried it so could be wrong.

[Christoph Hart]

If it says 2017 then you‘re living in the past. It now says 2022 / 2026

[Lindon]

@Christoph-Hart said in Last best commit for VS2022....?:

If it says 2017 then you‘re living in the past. It now says 2022 / 2026

..if you recall........... and maybe take a look at the post that started this thread....... I cant currently get on anything "current" because of the "global modulators breaking presets" bug, so what you are seeing is my current set up - as I said Im looking at getting on something more up-to-date if and when I can.

[Christoph Hart]

@Lindon still don't understand it. If you're stuck with a past state in HISE what does VS have anything to do? Either you can upgrade or not because of your projects requirements or not?