That will create a console app in the current directory.
dotnet run
Should build and run the app
Nuget comes in to play when you want to add packages to expand the base functionality. You shouldn’t need to add any source or username if you are installing public packages from nuget.org. If you look on nuget.org, all packages list the commands to install the package, including the dotnet command line version.
For example, to add in the Newtonsoft.json package:
dotnet new console
The template "Console App" was created successfully.
Processing post-creation actions...
Restoring /boot/home/Documents/CSharp/CSharp.csproj:
/boot/home/Documents/CSharp/CSharp.csproj : error NU1102: Unable to find package Microsoft.NETCore.App.Ref with version (= 9.0.0-preview.3.24157.1) [/boot/home/Documents/CSharp/CSharp.csproj]
/boot/home/Documents/CSharp/CSharp.csproj : error NU1102: - Found 130 version(s) in nuget.org [ Nearest version: 9.0.0-preview.3.24172.9 ] [/boot/home/Documents/CSharp/CSharp.csproj]
Restore failed with errors in 2.6s
Restore failed.
Post action failed.
Manual instructions: Run 'dotnet restore'
dotnet --version
resolve symbol "pipe2" returned: -2147478780
Failed to load /boot/home/dotnet/shared/Microsoft.NETCore.App/9.0.1/libcoreclr.so, error: Symbol not found
Failed to bind to CoreCLR at '/boot/home/dotnet/shared/Microsoft.NETCore.App/9.0.1/'
Failed to create CoreCLR, HRESULT: 0x80008088
All code changes to the main dotnet/runtime repository for Haiku, as described in the final GSoC 2023 report, has been either merged or filed as pull requests. These PRs are being actively reviewed by the maintainers. You can find an overview of recent PRs here.
The .NET 10 release significantly complicated the build process, so I don’t think we will support .NET 10 release builds in the dotnet-builds repository.
Once all open PRs are merged, hopefully for .NET 11 because they aren’t that big and hard to review, I will try getting the builds running again. Right now, because of the maintainers’ request to split out the patches, there are too many patches on different branches that we have to stack on top of each other to get a successful build of the CoreCLR.
I think using ‘5038’ would be a great nod to the past, given some of the band members worked for Be and the song was on the BeOS CD’s. Funny, I’ve listened to that song many times and it never occurred to me that it was ‘BeOS’ upside down, and I remember making words like that with a calculator as a kid.
Thanks for all the work in bringing .NET to Haiku, it’ll be great to have it available.
“official-ish” as in endorsed by Be/Haiku or their prominent representatives, and “the wild” as in mainstream cross-platform frameworks and formats comparable to PE.
Given this fact and that both @waddlesplash and @PulkoMandy strongly suggests 0x5038, then I guess it is decided
I personally like 0xBE05, it is a bit more obvious reference to BeOS than 5038.
Another reason, there is no confusion it is a hex number, unlike 5038 which could be incorrectly assumed to be decimal