Reputation: 10380
I'd like to "flush" an existing Azure Website (with an application published and running) and return it to its initial state (see sample link below) without loosing any of my configurations, connection strings, etc.
"initial state" sample: http://glenntest123.azurewebsites.net
I have an ASP.NET MVC 4 application deployed to another Azure Website and I changed the Assembly name
of the MVC application. Let's say the name changed from Hub2
to GlennApp
.
When I published to Azure through VS 2013 Community (Update 4) both Hub2.dll
and GlennApp.dll
are in the bin
folder and the errors that are surfacing are as follows:
My initial research pointed towards Owin.Startup
auto-discovery. So i've added the following two lines to the appsettings
:
<add key="owin:AutomaticAppStartup" value="false"/>
<add key="owin:AppStartup" value="GlennApp.Startup, GlennApp"/>
This doesn't seem to have stopped Hub2
from being loaded in the AppDomain.
I believe my options are:
Hub2.dll
from the disk with a WebJob?Startup
or Global.asax
to seek and destroy. Hub2
from loading into the AppDomain.Help?
Upvotes: 0
Views: 202
Reputation: 6376
In the Publish wizard in Visual Studio you can choose to delete all previous files prior to re-publishing. You can use this to redeploy your site, with the renamed DLL and have the old one removed.
If your settings etc. are stored inside the Web.Config
or in the settings stored in Azure that won't be a problem.
Upvotes: 3