I was able to use Asp.net MVC
with MySql
using Entity Framework code first, like the one explained here http://www.asp.net/identity/overview/getting-started/aspnet-identity-using-mysql-storage-with-an-entityframework-mysql-provider ... Here a couple the things I notice:
- The generated migration contains the schema
dbo.
that won't work onMySql
so I went to the migration file and remove all schema references. (there are better solutions, like configuration/setup wise) - The unique key length problem, such as UserName (defined in the asp.net Identity) has a maximum length of 256 and that is over the limitations of mysql unique field, so I changed the length to 128. that solved this error
Specified key was too long; max key length is 767 bytes
- I did have some troubles using the publishing wizard, since didn't show me any of my MySql Drivers to test my connection to my db, so I just change the Connection string in the config file and apply my migration changes to the new/testing DB from the Package Manager Console
> Update-Database
(this could be your temporary solution until you find a automatized solution)