Is it possible to separate each model's migrations in to their own custom foldersIs it possible to get Entity Framework to recognize previous migrations if you change your project namespace?DbContext constructor with connString causes problems with EF Migrations and EF PowertoolsGetting multiple DbContexts to use Migrations with the same databaseEntity Framework 6.0: how to use edmx context when connection is configured in code?Entity Framework Change Assembly Model not recognisedEntity Framework and empty migrations classEntity Framework, Automatic apply MigrationsWhy does EF 6 ignore applied migrations if I move the Migrations folder?Microsoft.EntityFrameworkCore.Sqlite (2.0.0 peview1-final) migration is not creating tablesCreate DBContext outside of DependencyInjection

What do you call the action of "describing events as they happen" like sports anchors do?

How can powerful telekinesis avoid violating Newton's 3rd Law?

Was planting UN flag on Moon ever discussed?

In American Politics, why is the Justice Department under the President?

Realistic, logical way for men with medieval-era weaponry to compete with much larger and physically stronger foes

Why would a home insurer offer a discount based on credit score?

What is the proper event in Extended Events to track stored procedure executions?

Am I allowed to determine tenets of my contract as a warlock?

How (un)safe is it to ride barefoot?

What do I need to do, tax-wise, for a sudden windfall?

Why did Robert pick unworthy men for the White Cloaks?

If the pressure inside and outside a balloon balance, then why does air leave when it pops?

Is it true that "only photographers care about noise"?

When to use и or а as “and”?

Is Lambda Calculus purely syntactic?

Forgot passport for Alaska cruise (Anchorage to Vancouver)

How to handle when PCs taste a potion that is actually poison?

How do I avoid typing "git" at the begining of every Git command?

How can I find out about the game world without meta-influencing it?

What would the consequences be of a high number of solar systems being within close proximity to one another?

Can I use 220 V outlets on a 15 ampere breaker and wire it up as 110 V?

In Pandemic, why take the extra step of eradicating a disease after you've cured it?

Are the guests in Westworld forbidden to tell the hosts that they are robots?

Why did the World Bank set the global poverty line at $1.90?



Is it possible to separate each model's migrations in to their own custom folders


Is it possible to get Entity Framework to recognize previous migrations if you change your project namespace?DbContext constructor with connString causes problems with EF Migrations and EF PowertoolsGetting multiple DbContexts to use Migrations with the same databaseEntity Framework 6.0: how to use edmx context when connection is configured in code?Entity Framework Change Assembly Model not recognisedEntity Framework and empty migrations classEntity Framework, Automatic apply MigrationsWhy does EF 6 ignore applied migrations if I move the Migrations folder?Microsoft.EntityFrameworkCore.Sqlite (2.0.0 peview1-final) migration is not creating tablesCreate DBContext outside of DependencyInjection






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I want to put each models migration files under their entity folder in their own directory, rather than the root folder (migrations)



Note > Entities > Migrations



Contacts > Entities > Migrations



So, I have a folder structure like so:



Notes
- Entities
- Note
- Http
- Handlers
- ShowNote.cs

Contacts
- Entities
- Contact
- Http
- Handlers
- ShowContact.cs


Now, both of my entities have relationships with eachother, hasOne, I have a db context like so:



using Microsoft.EntityFrameworkCore;
using software.Contacts.Entities;
using software.Notes.Entities;

namespace software.Core.Entities

public class SoftwareContext : DbContext

/// <inheritdoc />
/// <summary>
/// Constructor
/// </summary>
public SoftwareContext(DbContextOptions options)
: base(options)


/// <summary>
/// Contact model
/// </summary>
public DbSet<Contact> Contact get; set;

/// <summary>
/// Note model
/// </summary>
public DbSet<Note> Note get; set;





When I run migrations, it creates a folder n the root directory, but I am trying to make the migrations go to their respective folders like above, is this possible without creating seperate DB contexts for each model?



For example, is there any code like so, that would actually work:



using Microsoft.EntityFrameworkCore;
using software.Contacts.Entities;
using software.Notes.Entities;

namespace software.Core.Entities

public class SoftwareContext : DbContext

/// <inheritdoc />
/// <summary>
/// Constructor
/// </summary>
public SoftwareContext(DbContextOptions options)
: base(options)


/// <summary>
/// Contact model
/// </summary>
[MigrationsDirectory("root/Contact/Entities/Migrations")]
public DbSet<Contact> Contact get; set;

/// <summary>
/// Note model
/// </summary>
[MigrationsDirectory("root/Note/Entities/Migrations")]
public DbSet<Note> Note get; set;











share|improve this question






























    0















    I want to put each models migration files under their entity folder in their own directory, rather than the root folder (migrations)



    Note > Entities > Migrations



    Contacts > Entities > Migrations



    So, I have a folder structure like so:



    Notes
    - Entities
    - Note
    - Http
    - Handlers
    - ShowNote.cs

    Contacts
    - Entities
    - Contact
    - Http
    - Handlers
    - ShowContact.cs


    Now, both of my entities have relationships with eachother, hasOne, I have a db context like so:



    using Microsoft.EntityFrameworkCore;
    using software.Contacts.Entities;
    using software.Notes.Entities;

    namespace software.Core.Entities

    public class SoftwareContext : DbContext

    /// <inheritdoc />
    /// <summary>
    /// Constructor
    /// </summary>
    public SoftwareContext(DbContextOptions options)
    : base(options)


    /// <summary>
    /// Contact model
    /// </summary>
    public DbSet<Contact> Contact get; set;

    /// <summary>
    /// Note model
    /// </summary>
    public DbSet<Note> Note get; set;





    When I run migrations, it creates a folder n the root directory, but I am trying to make the migrations go to their respective folders like above, is this possible without creating seperate DB contexts for each model?



    For example, is there any code like so, that would actually work:



    using Microsoft.EntityFrameworkCore;
    using software.Contacts.Entities;
    using software.Notes.Entities;

    namespace software.Core.Entities

    public class SoftwareContext : DbContext

    /// <inheritdoc />
    /// <summary>
    /// Constructor
    /// </summary>
    public SoftwareContext(DbContextOptions options)
    : base(options)


    /// <summary>
    /// Contact model
    /// </summary>
    [MigrationsDirectory("root/Contact/Entities/Migrations")]
    public DbSet<Contact> Contact get; set;

    /// <summary>
    /// Note model
    /// </summary>
    [MigrationsDirectory("root/Note/Entities/Migrations")]
    public DbSet<Note> Note get; set;











    share|improve this question


























      0












      0








      0








      I want to put each models migration files under their entity folder in their own directory, rather than the root folder (migrations)



      Note > Entities > Migrations



      Contacts > Entities > Migrations



      So, I have a folder structure like so:



      Notes
      - Entities
      - Note
      - Http
      - Handlers
      - ShowNote.cs

      Contacts
      - Entities
      - Contact
      - Http
      - Handlers
      - ShowContact.cs


      Now, both of my entities have relationships with eachother, hasOne, I have a db context like so:



      using Microsoft.EntityFrameworkCore;
      using software.Contacts.Entities;
      using software.Notes.Entities;

      namespace software.Core.Entities

      public class SoftwareContext : DbContext

      /// <inheritdoc />
      /// <summary>
      /// Constructor
      /// </summary>
      public SoftwareContext(DbContextOptions options)
      : base(options)


      /// <summary>
      /// Contact model
      /// </summary>
      public DbSet<Contact> Contact get; set;

      /// <summary>
      /// Note model
      /// </summary>
      public DbSet<Note> Note get; set;





      When I run migrations, it creates a folder n the root directory, but I am trying to make the migrations go to their respective folders like above, is this possible without creating seperate DB contexts for each model?



      For example, is there any code like so, that would actually work:



      using Microsoft.EntityFrameworkCore;
      using software.Contacts.Entities;
      using software.Notes.Entities;

      namespace software.Core.Entities

      public class SoftwareContext : DbContext

      /// <inheritdoc />
      /// <summary>
      /// Constructor
      /// </summary>
      public SoftwareContext(DbContextOptions options)
      : base(options)


      /// <summary>
      /// Contact model
      /// </summary>
      [MigrationsDirectory("root/Contact/Entities/Migrations")]
      public DbSet<Contact> Contact get; set;

      /// <summary>
      /// Note model
      /// </summary>
      [MigrationsDirectory("root/Note/Entities/Migrations")]
      public DbSet<Note> Note get; set;











      share|improve this question
















      I want to put each models migration files under their entity folder in their own directory, rather than the root folder (migrations)



      Note > Entities > Migrations



      Contacts > Entities > Migrations



      So, I have a folder structure like so:



      Notes
      - Entities
      - Note
      - Http
      - Handlers
      - ShowNote.cs

      Contacts
      - Entities
      - Contact
      - Http
      - Handlers
      - ShowContact.cs


      Now, both of my entities have relationships with eachother, hasOne, I have a db context like so:



      using Microsoft.EntityFrameworkCore;
      using software.Contacts.Entities;
      using software.Notes.Entities;

      namespace software.Core.Entities

      public class SoftwareContext : DbContext

      /// <inheritdoc />
      /// <summary>
      /// Constructor
      /// </summary>
      public SoftwareContext(DbContextOptions options)
      : base(options)


      /// <summary>
      /// Contact model
      /// </summary>
      public DbSet<Contact> Contact get; set;

      /// <summary>
      /// Note model
      /// </summary>
      public DbSet<Note> Note get; set;





      When I run migrations, it creates a folder n the root directory, but I am trying to make the migrations go to their respective folders like above, is this possible without creating seperate DB contexts for each model?



      For example, is there any code like so, that would actually work:



      using Microsoft.EntityFrameworkCore;
      using software.Contacts.Entities;
      using software.Notes.Entities;

      namespace software.Core.Entities

      public class SoftwareContext : DbContext

      /// <inheritdoc />
      /// <summary>
      /// Constructor
      /// </summary>
      public SoftwareContext(DbContextOptions options)
      : base(options)


      /// <summary>
      /// Contact model
      /// </summary>
      [MigrationsDirectory("root/Contact/Entities/Migrations")]
      public DbSet<Contact> Contact get; set;

      /// <summary>
      /// Note model
      /// </summary>
      [MigrationsDirectory("root/Note/Entities/Migrations")]
      public DbSet<Note> Note get; set;








      entity-framework






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Mar 24 at 23:07







      DumbAnswersForDumbQuestions

















      asked Mar 24 at 22:38









      DumbAnswersForDumbQuestionsDumbAnswersForDumbQuestions

      205




      205






















          1 Answer
          1






          active

          oldest

          votes


















          0














          One way of doing this is to just specify the path of the migration when adding a new migration as follows



          Add-Migration -o DataMigrations


          I believe you can set the path of the migrations with the following commands but this will effect all future migrations



          enable-migrations -EnableAutomaticMigration:$false -MigrationsDirectory yourdirectory





          share|improve this answer

























            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "1"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55329264%2fis-it-possible-to-separate-each-models-migrations-in-to-their-own-custom-folder%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            One way of doing this is to just specify the path of the migration when adding a new migration as follows



            Add-Migration -o DataMigrations


            I believe you can set the path of the migrations with the following commands but this will effect all future migrations



            enable-migrations -EnableAutomaticMigration:$false -MigrationsDirectory yourdirectory





            share|improve this answer





























              0














              One way of doing this is to just specify the path of the migration when adding a new migration as follows



              Add-Migration -o DataMigrations


              I believe you can set the path of the migrations with the following commands but this will effect all future migrations



              enable-migrations -EnableAutomaticMigration:$false -MigrationsDirectory yourdirectory





              share|improve this answer



























                0












                0








                0







                One way of doing this is to just specify the path of the migration when adding a new migration as follows



                Add-Migration -o DataMigrations


                I believe you can set the path of the migrations with the following commands but this will effect all future migrations



                enable-migrations -EnableAutomaticMigration:$false -MigrationsDirectory yourdirectory





                share|improve this answer















                One way of doing this is to just specify the path of the migration when adding a new migration as follows



                Add-Migration -o DataMigrations


                I believe you can set the path of the migrations with the following commands but this will effect all future migrations



                enable-migrations -EnableAutomaticMigration:$false -MigrationsDirectory yourdirectory






                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Mar 25 at 11:03

























                answered Mar 25 at 9:45









                RennnnRennnn

                756




                756





























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55329264%2fis-it-possible-to-separate-each-models-migrations-in-to-their-own-custom-folder%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

                    SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

                    은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현