When published to Azure the first time is the old code, is it possible?

Good day!

I can not understand, whether my eyes are deceiving me, is this a bug in Azure.

There's an app for ASP.NET MVC publish it to the web service to Azure. For example there is a form to save images on the server.

Make edits, change the save location of the image. Publish to Azure. Test first time - saves on the old path. Again load the image saves fine as prescribed in the edit.

Thus, the patterns cannot figure out.

Actually the question, is this normal? how to overcome it?
July 8th 19 at 15:55
1 answer
July 8th 19 at 15:57
Solution
If you have a basic subscription to the resource you have deployed and type in free mode, the application is possible after deployment rolling your shadow changes and restart your app, well, as the old Keshi and assemblies shall be released it takes time and if you paid enough and Lee do not pay, do not take offense. Always hang the application, like: "there is a system update do not blame me", and in a very large application and more than 5 fronts rolling deals time and don't really want to see the users in old version DB wrote =)
I'm not crazy? :)))))) and that was the impression that the balls for the rollers. Yes, tari Base stood. I have switched to standard, it will be all OK? or at least better. - Maggie18 commented on July 8th 19 at 16:00
: It should, but still do not forget that when you deploy there is a moment of rolling out applications and all sorts of code first identity work when it is restarted after deployment. - Janick.Morissette commented on July 8th 19 at 16:03
: Thank You very much! - Maggie18 commented on July 8th 19 at 16:06

Find more questions by tags ASP.NETMicrosoft Azure