I was trying to create a Node.js Mobile App service to connect Xamarin Forms to an Azure SQL db. But somehow that service is unresponsive once I have connected the SQL Db.
So I though: option B, skip Node.js and create a Visual Studio package for a ASP.NET solution. Now I struggle with (to me) completely unclear procedures: In 90% of the attempts I make nothing happens in the SQL Db.
I've tried many things but the next steps brought me the most:
1. I Created a Mobile App service
2. I connect the mobile app service to an Azure Sql Db
3. I started the quickstart tutorial, selected a C# solution and downloaded the visual studio package
4. I published the package with a new profile (so I created another Mobile app service)
5. I had to connect this service to the same Azure Sql Db again, as this was not done autometically.
6. I published the package again with the profile from step 4. Result: A 'todoitem' table was published in the Azure SQL Db
8. I added a new (my own) table format to the solution (DataObject and Controller)
9. I changed the 'CreateDatabaseIfNotExists' to a 'DropCreateDatabaseIfModelChanges' method and added my new table.
10. I published the Mobile App again. Result: The new table was available in the Azure SQL Db
11. Both tables are available through Postman tests: success!
So I though: hooray I've got a development package as a template and I can create a production Mobile App from here by publishing it with a new profile.
But when I publish this same project with a new profile and connect the new Mobile App to a new Azure SQL db: nothing happens in Azure SQL tables. It just remains an empty Db.
What can I do to publish this successful dev package with a new profile, without having walk trough all the steps again?