Can't compile a DLL from the Export menu without getting an error message??? Can anyone help
-
@d-healey
The same error occurs for the Rhapsody project too -
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
Same again!
That's good. It means it is not a problem related to RNBO or scriptnode specifically.
Open a command prompt (cmd) and type msbuild and hit enter, tell me what happens.
-
Hello!
here is what has happened...
C:>msbuild
'msbuild' is not recognized as an internal or external command,
operable program or batch file. -
@GreekProgrammer Mystery solved, you need to install msbuild - this should be available from the Visual Studio installer if I recall correctly.
-
Hi! I hope so 100% believe you are on the case!
Is there any particular version to download...I'll take a screenshot in a moment.
Thank you -
Heres the shot...
-
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
Is there any particular version to download...I'll take a screenshot in a moment.
I'm not sure, I don't remember having to install it separately so I guess it was already checked along with whatever other options I selected at the time.
-
I've just installed it...
-
-
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
NOPE Still no joy :-(
Use the test project for now, I think you'll still hit the error
-
-
@GreekProgrammer either install vs2022 or set it to vs2017 in the Hise Settings. The best bet is to install Vs2022, it can live alongside other versions.
-
Hi Yes I have VS 2022 installed already and its set to 2022 in HISE too...
any suggestions?Thanks
-
@GreekProgrammer said in Can't compile a DLL from the Export menu without getting an error message??? Can anyone help:
yep still the same error!
Stick with the simple test project, the empty one. Because it's still possible there is some other scriptnode/RNBO - we need to do things one step at a time.
Libre Wave - Freedom respecting instruments and effects
My Patreon - HISE tutorials
YouTube Channel - Public HISE tutorials -
What happens if you open a cmd and type in msbuild?
Edit: saw it. You need to make the msbuild command accessible from anywhere. Try adding it to the path environment variables in Windows.
-
This post is deleted! -
-
NOPE!!!!
-
@GreekProgrammer until you cannot open a cmd ad type in msbuild you will not be able to run the export script.
Not sure what‘s wrong on your system because the default installation of VS will set the PATH environment variables correctly but you need to figure this out somehow, that‘s basic Windows stuff.
-
I am not sure if its Basic windows stuff !
The error message “MSBUILD : error MSB1003: Specify a project or solution file” occurs when you’re trying to build a .NET project, but the build process can’t find a valid project or solution file. Here are some steps to resolve this issue:
Specify the Project or Solution File Explicitly:
Make sure you’re in the correct directory that contains your project or solution file.
Explicitly specify the project or solution file as an argument in the dotnet publish command. For example:
dotnet publish <path_to_project_or_solution_file>Replace <path_to_project_or_solution_file> with the actual path to your .csproj or .sln file.
Check Your Project Structure:
Ensure that your project directory contains a valid .csproj or .sln file. If it doesn’t, create one.
If you’re working with a .NET Core project, you’ll need a .csproj file. You can create one manually or use the dotnet new command to scaffold a new project.
Package Versions and Dependencies:
If you’ve created a .csproj file, make sure it includes the necessary package references (dependencies) for your project. You can manage these using NuGet or by editing the .csproj file directly.
If you’re unsure about the correct package versions, consult the official documentation or search for the packages on NuGet.org.
