<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: MAHMOUD BU SALEH</title>
    <description>The latest articles on DEV Community by MAHMOUD BU SALEH (@mahmoud_busaleh_cebde16f).</description>
    <link>https://dev.to/mahmoud_busaleh_cebde16f</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4240229%2F039b126c-220f-45be-bfd1-1a9caebe97fa.png</url>
      <title>DEV Community: MAHMOUD BU SALEH</title>
      <link>https://dev.to/mahmoud_busaleh_cebde16f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mahmoud_busaleh_cebde16f"/>
    <language>en</language>
    <item>
      <title>One CLI command to handle EF Core entities and migrations? Let's discuss</title>
      <dc:creator>MAHMOUD BU SALEH</dc:creator>
      <pubDate>Thu, 12 Nov 2026 04:52:36 +0000</pubDate>
      <link>https://dev.to/mahmoud_busaleh_cebde16f/one-cli-command-to-handle-ef-core-entities-and-migrations-lets-discuss-29mo</link>
      <guid>https://dev.to/mahmoud_busaleh_cebde16f/one-cli-command-to-handle-ef-core-entities-and-migrations-lets-discuss-29mo</guid>
      <description>&lt;p&gt;Honestly, whenever I add a new model to an EF Core project, I feel like I'm stuck in the same repetitive loop: create the class file, jump into &lt;code&gt;DbContext&lt;/code&gt; to add the &lt;code&gt;DbSet&lt;/code&gt;, run &lt;code&gt;migrations add&lt;/code&gt;, and then run &lt;code&gt;database update&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Having worked with frameworks like Laravel, I really miss the speed of having &lt;strong&gt;one single CLI command that does it all&lt;/strong&gt;. &lt;/p&gt;

&lt;p&gt;I opened a proposal on the official EF Core repo (&lt;code&gt;#39569&lt;/code&gt;) to bring that kind of workflow to &lt;code&gt;dotnet-ef&lt;/code&gt;—letting us scaffold the entity, wire up the &lt;code&gt;DbSet&lt;/code&gt;, and sync the database in one go (via &lt;code&gt;dotnet ef entity create&lt;/code&gt; and &lt;code&gt;dotnet ef database sync&lt;/code&gt;).&lt;/p&gt;

&lt;p&gt;Good news is, one of the EF Core team members looked at it and moved it into their &lt;strong&gt;Backlog&lt;/strong&gt; rather than closing it. They mentioned that community upvotes (&lt;code&gt;👍&lt;/code&gt;) are what actually help push these kinds of quality-of-life features up the priority list for future releases.&lt;/p&gt;

&lt;p&gt;If you're also tired of the manual boilerplate and think a single-command workflow would save you time, feel free to check out the discussion and drop a 👍 on the GitHub issue so it gets on their radar:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/dotnet/efcore/issues/39569" rel="noopener noreferrer"&gt;https://github.com/dotnet/efcore/issues/39569&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would love to hear how you guys usually handle this in your projects!&lt;/p&gt;

</description>
      <category>dotnet</category>
      <category>dotnetcore</category>
      <category>efcore</category>
      <category>csharp</category>
    </item>
  </channel>
</rss>
