Error in visual studio when building hise

[d.healey]

@pcs800 said in Error in visual studio when building hise:

It just switches that fast without downloading anything?

Yep, you already have everything when you download the repo, it's just moving between different states when you change commit/branch.

When Christoph pushes some new changes you'll need to download those, for that you use git pull

[pcs800]

@d-healey

E:\Documents\HISE>git log
commit a20873ea7a8c00b251ddae7df8d6e3007f8c5f71 (HEAD)
Author: Christoph Hart <>
Date: Fri May 30 20:59:05 2025 +0200

- fix typo

commit bdf8df7f5e5daa087e6119b121863d723c40bb21
Author: Christoph Hart <>
Date: Fri May 30 20:54:07 2025 +0200

- fix network compilation without C++ nodes

commit f3b784818f93ce3c83f30a1c2b2ed9e4e1617856
Author: Christoph Hart <>
Date: Thu May 29 18:33:58 2025 +0200

- added custom font support for the CSS renderer

commit ac80af3bf3d785d50944cd4624c175e534d6c960
Author: Christoph Hart <>
Date: Wed May 28 19:19:59 2025 +0200

- CSS: added ::before2 and ::after2 pseudo elements due to popular demand

commit 372a9e682cff2f3b52ee432ae50977fc95d9173c
Author: Christoph Hart christoph-hart@gmx.de
Date: Thu May 15 11:10:52 2025 +0200

- JUCE: clip repainting of MIDI keyboard to pressed notes

:

[d.healey]

@pcs800 Did you clean the build?

What's is D:\Development\Project? Is that a folder on your system?

[pcs800]

@d-healey said in Error in visual studio when building hise:

Did you clean the build?

Yes

@d-healey said in Error in visual studio when building hise:

What's is D:\Development\Project? Is that a folder on your system?

No it is not

[d.healey]

@pcs800 After switching commits did you open the projucer project again and resave and open in IDE?

[pcs800]

@d-healey said in Error in visual studio when building hise:

After switching commits did you open the projucer project again and resave and open in IDE?

Yes

[d.healey]

@pcs800 said in Error in visual studio when building hise:

Did you clean the build?

Yes

And this was after you reopened visual studio after changing commits?

[pcs800]

@d-healey said in Error in visual studio when building hise:

And this was after you reopened visual studio after changing commits?

Yes, but i can do it all again on video and show you if you'd like

[d.healey]

I'm looking at the HISE source code and that line about the NKS thing was actually added 4 months ago, so it's possible it's not a problem with the version of the source code you have but something entirely different.

What is the exact path to Visual Studio on your system?

[pcs800]

@d-healey said in Error in visual studio when building hise:

What is the exact path to Visual Studio on your system?

C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE

[d.healey]

Do you have this in the extra definitions in Projucer HISE_INCLUDE_NKS_SDK=1?

[pcs800]

@d-healey said in Error in visual studio when building hise:

Do you have this in the extra definitions in Projucer HISE_INCLUDE_NKS_SDK=1?

Where is that located in projucer?

[d.healey]

@pcs800

The box labelled "Extra Preprocessor Definitions"

[pcs800]

@d-healey

[d.healey]

@pcs800 Strange, for some reason it's trying to include the nks wrapper...

Try adding HISE_INCLUDE_NKS_SDK=0 in that section.

[pcs800]

@d-healey
I added it, and did a debug build after cleaning.
It succeeded! I am trying a release build now.

[d.healey]

@pcs800 said in Error in visual studio when building hise:

I added it, and did a debug build after cleaning.

That's good. No idea why it's trying to include that file though, very strange.

[pcs800]

@d-healey Well now you know, for the next guy who gets stuck in this loop.
So does this mean I can switch to the latest commit?

[d.healey]

@pcs800 said in Error in visual studio when building hise:

So does this mean I can switch to the latest commit?

You can try it, github says it's not building though. But if it doesn't work, just switch back to the commit that works.

[pcs800]

@d-healey Nah, I will stay with this one. It works, and I need to get to work on why I came in here today in the first place.
I appreciate you sticking with me on this David. You're a saint ;-)
Release build successful, BTW