Mixing
dbo.__MigrationHistory table not being updated when publishing from Visual Studio
I am having an issue with the dbo.__MigrationHistory table not being updated with new database migrations, BUT the actual database itself is correctly updated with relevant changes. This means the site won't load due to it spotting a change in the context - and I have to manually insert the new changes into the dbo.__MigrationHistory table to make it load.
When I publish to Azure from Visual Studio everything works fine in my PRODUCTION site. However, I have the issue only on my TEST site (which has a different publish profile).
I have checked the EXECUTE CODE FIRST MIGRATIONS box in the publish profile on both the TEST and PRODUCTION publish profiles. Indeed, both publish profiles appear to be identical except for pushing to a different site.
In case it helps - whenever this happens my localdb SqlServer database also becomes unattached during the publish. So on my local PC I have to then go back and reattach the .mdf database file in SQL server management studio.
Any help / advice you can offer would be amazing.
visual-studio entity-framework
azure entity-framework-6 asked Jan 1 at 16:28
Dan FaberDan Faber
86
add a comment |
I am having an issue with the dbo.__MigrationHistory table not being updated with new database migrations, BUT the actual database itself is correctly updated with relevant changes. This means the site won't load due to it spotting a change in the context - and I have to manually insert the new changes into the dbo.__MigrationHistory table to make it load.
When I publish to Azure from Visual Studio everything works fine in my PRODUCTION site. However, I have the issue only on my TEST site (which has a different publish profile).
I have checked the EXECUTE CODE FIRST MIGRATIONS box in the publish profile on both the TEST and PRODUCTION publish profiles. Indeed, both publish profiles appear to be identical except for pushing to a different site.
In case it helps - whenever this happens my localdb SqlServer database also becomes unattached during the publish. So on my local PC I have to then go back and reattach the .mdf database file in SQL server management studio.
Any help / advice you can offer would be amazing.
visual-studio entity-framework
azure entity-framework-6 asked Jan 1 at 16:28
Dan FaberDan Faber
86
add a comment |
I am having an issue with the dbo.__MigrationHistory table not being updated with new database migrations, BUT the actual database itself is correctly updated with relevant changes. This means the site won't load due to it spotting a change in the context - and I have to manually insert the new changes into the dbo.__MigrationHistory table to make it load.
When I publish to Azure from Visual Studio everything works fine in my PRODUCTION site. However, I have the issue only on my TEST site (which has a different publish profile).
I have checked the EXECUTE CODE FIRST MIGRATIONS box in the publish profile on both the TEST and PRODUCTION publish profiles. Indeed, both publish profiles appear to be identical except for pushing to a different site.
In case it helps - whenever this happens my localdb SqlServer database also becomes unattached during the publish. So on my local PC I have to then go back and reattach the .mdf database file in SQL server management studio.
Any help / advice you can offer would be amazing.
visual-studio entity-framework
azure entity-framework-6 asked Jan 1 at 16:28
Dan FaberDan Faber
86
I am having an issue with the dbo.__MigrationHistory table not being updated with new database migrations, BUT the actual database itself is correctly updated with relevant changes. This means the site won't load due to it spotting a change in the context - and I have to manually insert the new changes into the dbo.__MigrationHistory table to make it load.
When I publish to Azure from Visual Studio everything works fine in my PRODUCTION site. However, I have the issue only on my TEST site (which has a different publish profile).
I have checked the EXECUTE CODE FIRST MIGRATIONS box in the publish profile on both the TEST and PRODUCTION publish profiles. Indeed, both publish profiles appear to be identical except for pushing to a different site.
In case it helps - whenever this happens my localdb SqlServer database also becomes unattached during the publish. So on my local PC I have to then go back and reattach the .mdf database file in SQL server management studio.
Any help / advice you can offer would be amazing.
visual-studio entity-framework
azure entity-framework-6 visual-studio entity-framework
azure entity-framework-6 asked Jan 1 at 16:28
Dan FaberDan Faber
86
asked Jan 1 at 16:28
Dan FaberDan Faber
86
edited Jan 25 at 18:20
Dan Faber
asked Jan 1 at 16:28
Dan FaberDan Faber
86
asked Jan 1 at 16:28
Dan FaberDan Faber
86
asked Jan 1 at 16:28
Dan FaberDan Faber
86
86
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I've had a number of occasions where Entity Framework migrations have left the state of migrations in an unusable state. Usually this happens after a large number of migrations have been applied from different developers and get stuck to where we can't update a database with new migrations or roll back.
It's simply easier to delete the migrations and start with a clean state from the current schema.
If you go the Route of resetting your migrations, make sure you back up your code and make known good backups of your database.
In summary, the steps to do this are:
- Remove the _MigrationHistory table from the Database
- Remove the individual migration files in your project's Migrations folder
- Enable-Migrations in Package Manager Console
- Add-migration Initial in Package Manager Console
- Comment out the code inside of the Up method in the Initial Migration
- Update-database in Package Manager Console(does nothing but creates Migration Entry)
- Remove comments in the Initial method
This is not a ideal work around but this will resolve the your issue.
P.S.- This usually occurs when somebody update DB from local machine and it goes out of sync.
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997068%2fdbo-migrationhistory-table-not-being-updated-when-publishing-from-visual-studi%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
I've had a number of occasions where Entity Framework migrations have left the state of migrations in an unusable state. Usually this happens after a large number of migrations have been applied from different developers and get stuck to where we can't update a database with new migrations or roll back.
It's simply easier to delete the migrations and start with a clean state from the current schema.
If you go the Route of resetting your migrations, make sure you back up your code and make known good backups of your database.
In summary, the steps to do this are:
- Remove the _MigrationHistory table from the Database
- Remove the individual migration files in your project's Migrations folder
- Enable-Migrations in Package Manager Console
- Add-migration Initial in Package Manager Console
- Comment out the code inside of the Up method in the Initial Migration
- Update-database in Package Manager Console(does nothing but creates Migration Entry)
- Remove comments in the Initial method
This is not a ideal work around but this will resolve the your issue.
P.S.- This usually occurs when somebody update DB from local machine and it goes out of sync.
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
add a comment |
I've had a number of occasions where Entity Framework migrations have left the state of migrations in an unusable state. Usually this happens after a large number of migrations have been applied from different developers and get stuck to where we can't update a database with new migrations or roll back.
It's simply easier to delete the migrations and start with a clean state from the current schema.
If you go the Route of resetting your migrations, make sure you back up your code and make known good backups of your database.
In summary, the steps to do this are:
- Remove the _MigrationHistory table from the Database
- Remove the individual migration files in your project's Migrations folder
- Enable-Migrations in Package Manager Console
- Add-migration Initial in Package Manager Console
- Comment out the code inside of the Up method in the Initial Migration
- Update-database in Package Manager Console(does nothing but creates Migration Entry)
- Remove comments in the Initial method
This is not a ideal work around but this will resolve the your issue.
P.S.- This usually occurs when somebody update DB from local machine and it goes out of sync.
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
add a comment |
I've had a number of occasions where Entity Framework migrations have left the state of migrations in an unusable state. Usually this happens after a large number of migrations have been applied from different developers and get stuck to where we can't update a database with new migrations or roll back.
It's simply easier to delete the migrations and start with a clean state from the current schema.
If you go the Route of resetting your migrations, make sure you back up your code and make known good backups of your database.
In summary, the steps to do this are:
- Remove the _MigrationHistory table from the Database
- Remove the individual migration files in your project's Migrations folder
- Enable-Migrations in Package Manager Console
- Add-migration Initial in Package Manager Console
- Comment out the code inside of the Up method in the Initial Migration
- Update-database in Package Manager Console(does nothing but creates Migration Entry)
- Remove comments in the Initial method
This is not a ideal work around but this will resolve the your issue.
P.S.- This usually occurs when somebody update DB from local machine and it goes out of sync.
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
I've had a number of occasions where Entity Framework migrations have left the state of migrations in an unusable state. Usually this happens after a large number of migrations have been applied from different developers and get stuck to where we can't update a database with new migrations or roll back.
It's simply easier to delete the migrations and start with a clean state from the current schema.
If you go the Route of resetting your migrations, make sure you back up your code and make known good backups of your database.
In summary, the steps to do this are:
- Remove the _MigrationHistory table from the Database
- Remove the individual migration files in your project's Migrations folder
- Enable-Migrations in Package Manager Console
- Add-migration Initial in Package Manager Console
- Comment out the code inside of the Up method in the Initial Migration
- Update-database in Package Manager Console(does nothing but creates Migration Entry)
- Remove comments in the Initial method
This is not a ideal work around but this will resolve the your issue.
P.S.- This usually occurs when somebody update DB from local machine and it goes out of sync.
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
answered Jan 28 at 14:11
Mohit Verma - MSFTMohit Verma - MSFT
944617
944617
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53997068%2fdbo-migrationhistory-table-not-being-updated-when-publishing-from-visual-studi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
