Based on the deployment vs runtime issues article, I went into Kudu Console, clicked edit on the .cshtml file and confirmed that it is updated correctly.
However viewing the page through the browser still showed the old version.
Tried restarting the web app in Azure Portal, no luck.
It seems as though just updating the view somehow does not "compile" the changed view.
So I googled about this method not working and some stackoverflow forum suggested to add the session.flush() method after update and then it actually worked.
My quesiton is if the update() call was really causing the update to be getting cached instead of directly getting updated to DB.
For more information, you could refer to this similar issue.Hi Folks, We are experiencing a problem with IIS 7.5 on Server 2008 R2. It just keeps showing the old unchanged web service. When published to other web servers all works as it should. Often you may find a need to delete these when you have a deployment.When we publish changes to a web service (C# in Visual Studio 2010), the changes aren’t showing up when the web service is run. Unfortunately it’s the production server that doesn’t update. It is found under the framework paths so something like "C:\WINDOWS\Microsoft.If zero is returned, and this wasn't expected, then it's easy to flag up to the calling application. Second, the SET clause specifies which column that you want to modify and the new values.Also, check out the AJAX Videos which discuss usage of not only the Update Panel but also the AJAX Control Toolkit. The scenario: only a .cshtml file changed in the MVC project.So our Update Panel will look like this: using System; using System. Web Controls; public partial class _Default : System. To update multiple columns, you use a list comma-separated assignments.You supply the value in each column’s assignment in the form of a literal value, an expression, or a subquery.