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

Microsoft.EntityFrameworkCore.Design missing? #16278

Closed
TRexStark opened this issue May 13, 2024 · 3 comments
Closed

Microsoft.EntityFrameworkCore.Design missing? #16278

TRexStark opened this issue May 13, 2024 · 3 comments
Labels

Comments

@TRexStark
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.3.0

Bug summary

I wanted to take the leap and try out v13 as most of our sites are still on v10.
It's a fresh install with nothing in it at all, literally just the initial installation of Umbraco.
I published the site to Folder and tried to run in in a live production server but kept getting a 500.30 error.
The logs didn't provide any details besides the application shutting down.
Then I thought I'll just review the publish setting and found an error stating that the startup project doesn't reference the Microsoft.EntityFrameworkCore.Design.

I'm not sure if I'm missing something or if this is a bug.

Specifics

No response

Steps to reproduce

Just initiate a clean install of Umbraco v13.3.0 and publish it to a production site.

Expected result / actual result

Shouldn't all base Microsoft dependencies required be as part of the installation?

Copy link

Hi there @TRexStark!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@ronaldbarendse
Copy link
Contributor

The Microsoft.EntityFrameworkCore.Design dependency is a design-time service and shouldn't be deployed with your application, see: https://learn.microsoft.com/en-us/ef/core/cli/services.

Umbraco only references it in the Umbraco.Web.UI project (the example/test site used for local CMS development), but that project is not packaged/published:

<ItemGroup>
<!-- Add design/build time support for EF Core migrations -->
<PackageReference Include="Microsoft.EntityFrameworkCore.Design" PrivateAssets="all" />
</ItemGroup>

If you add a custom EF Core context and have added this dependency to create your own initial migrations, make sure to add the PrivateAssets="all" to the package reference as well!

@TRexStark
Copy link
Author

Thanks @ronaldbarendse I literally just finished troubleshooting the issue and found the info you provided and realised that I had something messing around with my local setup after all.

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

No branches or pull requests

2 participants