I had a website connected with TFS and Azure.
I added another project to that solution and accidentally messed with its nuget packages.
Now I rolled back to the changeset that was before, and the solution in both VS and TFS online looks like that changeset that used to be before.
Anyway, the website is still down, I get this error:
[FileLoadException: Could not load file or assembly 'Microsoft.Owin,
Version=2.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its
dependencies. The located assembly's manifest definition does not match the
assembly reference. (Exception from HRESULT: 0x80131040)]
<OLDPROJECTNAME!>.Startup.ConfigureAuth(IAppBuilder app) +0
<OLDPROJECTNAME!>.Startup.Configuration(IAppBuilder app) +5
Which definitely belongs to the old added project which has now been removed
from solution/changeset.
Why does TFS insist on complaining about a problem that doesn't exists in the changeset at all!
Another evidence that this is a misbehavior of the deployment process.
I've created a brand new website on azure and deployed the same website again and works like a charm.
The problem is I don't want to delete and recreate the website because I don't have access to the domain host and its settings.
Is there a way to clean an azure website's contents (but the domain settings) and redeploy it?
Well thanks to the help of David Ebbo of Microsoft, I've discovered in an msdn thread about this awesome tool Kudu, which is something you must know about if you use Azure.
With the the aid of Kudu I've been able to browse the files and discover the the folder was polluted with files from previous builds - just what I suspected.
After clearing the contents of wwwroot folder and redeploying again issue is gone.
Hope this helps