I've been surrounded with coronavirus here in Malaysia, but here I am watching you explaining how to deploy to Azure SQL DB.. must learn at all cost..🔥👍
Nicely done Tim! I was able to catch up to this point in a week, it has been absolutely insightful. Thanks for taking the time and effort to put up a great content!
11:51 If you get a warning text “To browse Azure Sql Database, install a full version of Visual Studio” in VS2022, it means you should add "Azure Data Lake and Stream Analytics Tools" component to your VS. (Tools > Get Tools and Features > Individual Components). Then you need manually add server address, admin name and password from Azure. It works, but quite a bit more different steps than Tim has.
Thanks Tim! Finally I'm up to date on TimCo Retail Manager. Suggestion Show an example that uses tab control in TimCoRetail or in another futur project. Reason With time applications become complex to navigate. Navigating using a menu becomes difficult when there are many Views. To ease navigation it would be good to have views open inside a tab and let users close the tabs they no longer use.
FYI I did an example that works with the help of StackOverflow member. The example is on my GitHub repos. I think it's not perfect but it works. It's up to you to see and remove my suggestion from your list. Best Regards. Ref :github.com/JeanMarcFlamand/C.M-Basic-Examples
Hi Tim, I am learning a lot from your videos. I have a problem I have been struggling to solve, I am trying to build an Azure SQL server Database on SSDT and push it to DevOps but my project is giving me because of the database is referencing another Database through External tables. The external tables and client users are not building with the project.
I believe there is an option when you publish your API to RunEF migrations. So you wouldn't have had to do it manually. Of course, you would need your SQL Server db set up with the connection string info in place in the app service.
I believe you are correct. It is a setting in the publish. When we set it up to be automatic with Azure DevOps, we will definitely check that it is configured to do so.
I do miss some way to configure Azure to always pick the cheapest option, to avoid accidental bills, while I am just trying out stuff. Can't really blame you for that though. Nice video (as usual).
Hi Tim, Always love your videos. Keep doing an awesome job!. I recently started learning about Azure and started working on some personal projects to get some practice. I have created both a SQL DB and a Web API (.Net framework) and migrated both to my Azure account. I followed the steps you mentioned in the video in relation to adding the connection strings in the Azure App services however I'm getting "Message": "An error has occurred." each time I invoke the API using Postman. I believe that the Web API is unable to reach the Database. I also updated the firewall rule in the Sql Database server in Azure.
Not sure what the issue is. It does sound like you have checked all of the usual suspects. I would put a breakpoint in before where you think the problem is and step through the code. See if you can identify the error.
@@IAmTimCorey Thats the thing. The web API works fine when I am debugging it in visual Studio however when I deploy it to Azure its throwing the error (500 Internal Server Error) in Postman. Is there any other way to troubleshoot the database connectivity between the API and the SQL Database?
Very helpful video as always, thanks a lot for what you're doing Tim ! I have one question though : can I manage my Azure database with the developer licence of SQL Server? If yes, in which case is it useful to buy a standard or entreprise licence of SQL Server?
SQL management does not require a license. The license is for the server itself. You can install SSMS on any machine. Managing an Azure database does not require any additional SQL license. Except in specific cases, the Azure SQL database is fully licensed already, which means you don't need to pay anything beyond the fee for hosting SQL.
Hello Tim, In am creating an app that utilizes Postgre not Microsoft SQL Server. Was wondering if this Azure DevOps allows a smooth transition for Postgre just like with MSSS?
I haven't used the deployment process with Postgres, but Microsoft doesn't have a database project type for it, so the process would be a bit different.
Hi Tim, I deployed my project the same steps with you, but am facing issue which reading the DB but not the tables that i created , what is your advise, Thanks
Anybody else getting this location is not available for subscription when trying to create their database in Azure? No matter what I chose I cant create a database due to the location.
It may be a current issue for some people: social.technet.microsoft.com/Forums/en-US/5aabe21e-9617-4c8a-8a88-ec1989d4c155/this-location-is-not-available-for-subscription?forum=ssdsgetstarted
For that reason, I published my Database to Google Cloud Platform, until azure is back online, then i'll migrate it to azure. I suggest doing the same, it is not that hard. You just have to follow the (not so good) instructions very carefully. You can sign up for a free account, and you get something like 300 dollars in credit for 12 months so yeah.. its worth it until Azure SQL is back online..
I just wanted to let everyone who's watching this issue know that as of today (4/12/2020) I was able to create my SQL database in my preferred region. so you may want to check again.
"Secure" connection string is a mis-labeling when it comes to Docker. It is only really secure if you control the Docker host. Otherwise, it is not much different than deploying a desktop app unless you really secure the operating system.
I cannot find the database in visual studio. when i go to publish the DB, go to browse, click on azure and it says "no connection to display" has anyone else had this happen? @11:56
The SQL database shouldn't be changing its IP address frequently (or at all), but you would store it in a configuration file so you could quickly change it.
I've been having a heck of a time trying to solve this error. When I'm running the EF commands "Update-database" after replacing my localDB connnection strings with the ones from azure (yes, I replaced the password too), I'm getting this error: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No such host is known.) This has been plauging me for a few days now and I can't seem to figure it out. I can connect to my database just fine in SSMS.
Hi @IAmTimCorey, I have typed Updated-database- Project TRM api in the Package Manager Console but it doesn't update the data like what happens at 22:42. It just says exactly: PM> Update-database -Project TRMApi Multiple startup projects set. Using project 'API\TRMApi' as the startup project. Build started... Build succeeded. Done. I'm am unsure of the problem as I have doubled checked the ConnectionStrings, and the tables in my database in MSSMS are null.
That looks like it ran. Are you sure that the connection string is pointing to the same location as where you are checking? Maybe change it to a different database name and see if it works then.
They can act as a single-endpoint API, yes, although that isn't what they are designed for. In my opinion, a full API is almost always the right choice. You can expand it over time and you can add authentication. Neither is true of an Azure Function.
I know you are showing real world examples here, but just to save the costs of an extra basic database, even though it's only 5 dollars, you could put your auth and data in the same database as this is only a dev application.
The only problem with that is that then dev is different than production. I get what you are saying about not paying for two databases for dev but if your dev servers are in Azure, you should pay for a mirror environment of production (just scaled down).
@@IAmTimCorey What is the reason why we should not have the auth and app data tables in the same database in production environment? This answer does not have any comments regarding concerns about doing it: stackoverflow.com/questions/25651342/how-to-add-asp-net-mvc5-identity-authentication-to-existing-database/25651908#25651908
@@IAmTimCorey literally just figured out the problem. I had walked away from the project and just saw on my phone that you replied 2 hours ago so I decided to take another crack at it. Turns out I still had the DataManager project in my solution. Since I'm working on a new pc when I downloaded from Azure I guess it brought it back in and I had forgotten what it, I just figured it was necessary since it had it's own library. That naming scheme got me lol. Thanks for your reply
To get swagger working similar to before the upgrade here is a link. The 2nd answer is the easiest to follow => stackoverflow.com/questions/58179180/jwt-authentication-and-swagger-with-net-core-3-0
