Can not Export: The system cannot find the file specified
-
@Dlukas7 Does the same thing happen when you try to export a VST?
-
@d-healey yep
-
Did you open or create a HISE project before you pasted the snippet? You need to do this so HISE has the correct folder structure to put all the files.
-
What happens if you open cmd.exe and put
msbuildin there? My guess is that you haven't installed VS2017 correctly because that error message tries to find the command line compiler that should be included with a proper install. -
@Christoph-Hart He built HISE from source earlier so VS must be installed correctly, no?
-
@d-healey So what should I do? :D
I start to feel kinda desperate :D -
well, maybe he didn't install
msbuild. The VS installer procedure is a bit flaky so I have seen weirder things happen. -
@Dlukas7 said in Can not Export: The system cannot find the file specified:
So what should I do?
Ctrl+R, then type in cmd, then
msbuild. If it shows a error message ("this path can't be found"), then something went wrong with your VS install. -
@Christoph-Hart where ctrl + r? (sorry, I am really new to coding and those things)
-
In Windows :) It opens the Run command window that you can use to execute stuff.
-
@Christoph-Hart doesnt work for me, isnt typing cmd enough or is that another kind of this thing?
-
Try something else. HISE looks for msbuild at this location:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\MsBuild.exe\Please check if you have that directory and if the file exists there. If not, please make sure that you've ticked the msbuild box in the VS installer.
-
@Christoph-Hart I have, the only thing is that its in:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin
don't know if it makes difference so I ll just let you know
-
Lol why do you have VS Professional? You need the Community Edition ;)
-
@Christoph-Hart You ve got to be kidding me... :DDD
-
@Christoph-Hart can you please give me a link to that version please? (and I guess I must uninstall vs I have right now?) :D
-
Actually we should get this to work without reinstalling VS2017.you've come so far, it would be unfair :)
So let's start with the most stupid solution, maybe we get off this one the most laziest way. Just go into
C:\Program Files (x86)\Microsoft Visual Studio\2017\where you should have aProfessionalfolder. Now just duplicate it and rename it toCommunity, then retry the export process. However it is extremely important that you tell no one I actually gave that advice :) -
@Christoph-Hart Why? :DD Will my pc start burning? :DDD
-
@Christoph-Hart Ok I did it but I still have the same problem
-
@Christoph-Hart
ok, so I did reinstal the VS 2017 Professional to the Community version, but I still can not export. Is there anything else I could do? (I have like a week for the whole plugin to be made, so I really need it done) thanks
-
D d.healey referenced this topic on
