Godot

6015 readers

125 users here now

Welcome to the programming.dev Godot community!

This is a place where you can discuss about anything relating to the Godot game engine. Feel free to ask questions, post tutorials, show off your godot game, etc.

Make sure to follow the Godot CoC while chatting

We have a matrix room that can be used for chatting with other members of the community here

Other Communities

Rules

Posts need to be in english
Posts with explicit content must be tagged with nsfw
We do not condone harassment inside the community as well as trolling or equivalent behaviour
Do not post illegal materials or post things encouraging actions such as pirating games

We have a four strike system in this community where you get warned the first time you break a rule, then given a week ban, then given a year ban, then a permanent ban. Certain actions may bypass this and go straight to permanent ban if severe enough and done with malicious intent

Wormhole

[email protected]

Credits

The icon is a modified version of the official godot engine logo (changing the colors to a gradient and black background)
The banner is from Godot Design

founded 2 years ago

MODERATORS

Ategon

snowe

Feyter

The Future of C# in Godot – GameFromScratch.com (gamefromscratch.com)

submitted 1 year ago by mac to c/godot

39 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] -3 points 1 year ago (3 children)

What I don't like about C# has nothing to do with the language itself, which is pretty good. Is the fact that is made by Microsoft and their tooling SUCKS. I'm having to build .NET projects at work and the dotnet CLI is pure garbage. I wish we had something better instead of using C# but the gamedev industry is pretty invested on it.

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago) (1 children)

Hi. I am not a game dev, but a c# one. What is it that frustrates you about the dotnet CLI?

Edit: I use C# for work, not a Microsoft employee who works on c# dev lol

[–] [email protected] 1 points 1 year ago (2 children)

Documentation is the worst offender. I remember one time that running dotnet restore and later running another command with --no-restore flag wouldn't work, but running the last command without the --no-restore flag would. Creating a sane CI/CD pipeline for C# apps is a PITA.

[–] Lucky 7 points 1 year ago

I've never had an issue with the dotnet CLI, including the commands you're talking about. Their documentation is a bit scattered at times but for the most part they have examples on everything and walk through most scenarios.

I'm not a Microsoft employee either, just a c# dev of 10 years.

[–] Lmaydev 0 points 1 year ago* (last edited 1 year ago) (1 children)

I do a lot of work with c# CI/CD and doing what you said absolutely does work.

Most of my scripts are

dotnet restore
dotnet build --no-restore
dotnet test --no-build
dotnet publish --no-build

[–] [email protected] 1 points 1 year ago (1 children)

It works, until it doesn't

[–] Lmaydev -1 points 1 year ago* (last edited 1 year ago)

Like everything. They likely got their configurations wrong.

[–] [email protected] 3 points 1 year ago (1 children)

This is the major problem with c#. Godot project should target support of .net and mono runtime and THAT'S IT. If you want C# to run on iOS, Microsoft and Apple have to fix it. Let's not spend 1 billion dollars a year making sure whatever random iOS runtime is supported like unity did. That is the root cause of why they would like to charge I stall fees in the first place.

[–] Lmaydev 1 points 1 year ago* (last edited 1 year ago) (1 children)

.net (formally .net core) runs on all major OSs.

Mono and .net framework are super out of date and shouldn't be used anymore.

[–] [email protected] 2 points 1 year ago

Well whatever - going down the proprietary imementation route for c# the way unity did is a no go for Godot imo.