Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider multi-targeting your projects to support .NET 8 #382

Open
dlandi opened this issue Nov 27, 2024 · 4 comments
Open

Consider multi-targeting your projects to support .NET 8 #382

dlandi opened this issue Nov 27, 2024 · 4 comments

Comments

@dlandi
Copy link

dlandi commented Nov 27, 2024

Consider multi-targeting your projects to support .NET 8

@linkdotnet
Copy link
Owner

Hey @dlandi - Is there any specific need to use net8.0? I do understand that this is a LTS release.

Enabling multiple versions might increase maintainability costs.

@dlandi
Copy link
Author

dlandi commented Nov 27, 2024

Presumably, 99% of your code is written in .NET 8.
I can't install .NET 9 on my work machine at the moment (because it interferes with Project Nuget Package Management ).
So my only alternative is to use your last commit before upgrading to .NET 9.

@linkdotnet
Copy link
Owner

linkdotnet commented Nov 27, 2024

Hmm I see your point. While I make myself some thoughts about that, there might be an easy way out for the meantime.

The GitHub repo offers a codespace / devcontainer—basically a running docker-container in the cloud with VS Code.
Every GitHub user has 120 CPU hours a month for free - that should be enough to play around without downloading anything to your local machine.

You can easily create a devcontainer:
image

As you can see I am using this feature myself quite often

For playing around 4 CPU's should be good enough. There are predefined tasks like running the whole blog. You can also use the cmd or the UI:
image

In same cases (I am figuring out why) it can happen that you manually have to run:

dotnet dev-certs https --trust

Even though that should happen when the container is built. But the error message should indicate that. Anyway, once you are running the blog, it should open a popup / or you go to ports:
image

This will open a new tab with the blog running.

@dlandi
Copy link
Author

dlandi commented Nov 28, 2024

I'll look into it. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants