When I add ApplicationInsights in my ASP.NET Core's startup.cs, Azure Portal still suggest connecting my AppService to Application Insights. Does it make any difference? Won't be some traces duplicated then?
SSDT look great, but unfortunately it isn't very useful in real world CI/CD, because it fail to update existing database if there are data. Unless I'm missing something.
Without ability to write custom migration scripts for specific changes, like changing column datatype, or adding non-nullable column without default value, I have to update the existing database manually anyway.
Do you have some tips how to deal with such changes?
@rogreen: Excellent idea. I will spread the series in our local community. There are tons of resources that talks about the principles in general, but I would love to see it as close as possible to C#, .NET (Core), ASP.NET MVC or UWP.