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

Upgrade to .NET 6 #30

Open
agriffard opened this issue Jan 11, 2022 · 3 comments
Open

Upgrade to .NET 6 #30

agriffard opened this issue Jan 11, 2022 · 3 comments

Comments

@agriffard
Copy link
Member

Should we upgrade the projects to .NET 6 (use Program.cs, ...)?

@jeremycook
Copy link
Contributor

If the question is "should we upgrade from net5.0 to net6.0?" my answer would be yes. If the question is should we drop Startup.cs and move that configuration into Program.cs I'd defer to the opinions of others. I have mixed feelings about the new way.

@jeremycook
Copy link
Contributor

After thinking about this more I feel like conforming to the new .NET 6 way of having moving startup into Program.cs makes a lot of sense for Orchard Core framework applications. It actually clarifies what it is a module project vs. what is an application host since only module projects would have Startup.cs files after the change.

@herryG
Copy link

herryG commented Mar 11, 2022

I upgraded my application to .net 6, but when I try to use the .net 6 way of having single program.cs insead of both startup and program.cs it doesn't seems to work. but when I keep it splitted it is working.
Is the startup.cs required in modules for orcardcore to run perfectly?

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

3 participants