What are the tradeoffs for the different merge settings for Azure publish?

Viewed 1526

When you publish through Visual Studio to Azure, you have the option to precompile your pages. There are quite some options that explain what it does, but nothing about the trade-offs.

  • Why wouldn't I check 'Allow [...] to be updatable'?
  • Why merge into one file? Is this faster? Does it load faster or compile faster?

There is some information on the Microsoft site, but on above points they are not diving really into it.

https://msdn.microsoft.com/en-us/library/hh475319(v=vs.110).aspx

enter image description here

2 Answers

I just wanted to post here, because it might be relevant to other people. I had a large legacy project in ASP.NET Framework 4.7 running in Azure.

I had a lot of problems with the "live" compilation of pages on Azure. With a lot I mean really a lot. I.e. this. Sometimes I hit a page that wasn't precompiled and Azure seemed to exhaust all resources just on the compilation, bringing the whole application down. After a restart it took 8 (!!) minutes before it could handle the first hit. Local it was only like 30 seconds.

During Corona I finally had time to move to .NET Core - and all these problems instantly went away.

Despite that Microsoft says they will continue supporting .NET Framework for a long time, it is clear to me that Microsoft doesn't have any passion for that project anymore. The issues I had in combination with Azure were ridiculous.

I strongly recommend to migrate as soon as possible. Even for a large project it was less painful than I imagined beforehand.

Related