I updated to VS 2017, converting from project.json to .csproj methodology - seems to have fixed the issue. Not sure what the root cause was for publishing in VS 2015 still but I'm happy with the outcome.
Thanks,
Mike
Quick update - it looks like it had something to do with the seed data instead of the migration it self. I removed the seed data (the data that was provided in the development step-by-step guide) and it ran the migration flawlessly. I'm not sure why the seed data would be trying to insert 0 into the PbPersons.TenantId column but it was. I'll investigate further.
That's exactly what I needed, thank you!
