tag:help.appveyor.com,2012-11-13:/discussions/problems/2465-experiencing-issues-deploying-to-azure-websiteAppVeyor: Discussion 2018-10-19T08:17:18Ztag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T18:11:28Z2015-07-09T18:11:28ZExperiencing issues deploying to Azure Website<div><p>Hi Erik,</p>
<p>If the publishing went OK I think this might be
application-specific issue. Disable custom errors as suggested to
see actual exception.</p>
<ul>
<li>Feodor</li>
</ul></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T18:25:08Z2015-07-09T18:25:09ZExperiencing issues deploying to Azure Website<div><p>Thanks Feodor. Is there any other configuration setting that
needs to be put in place for Azure website deployment from
appveyor? As mentioned earlier, Im just trying to hit the root URL
in Azure and getting the error. When I remote debug the same code
on my local everything is working fine.</p>
<p>Appreciate your assistance.</p>
<p>Erik</p></div>Erik Schlegeltag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T19:30:19Z2015-07-09T19:30:19ZExperiencing issues deploying to Azure Website<div><p>+my colleagues Eric/Brian/Brad</p>
<p>Feodor,</p>
<p>After removing custom errors we’re receiving the following
error which is complaining about Owin startup attribute. Have any
of your other clients on Azure complained about this in the past?
When we deploy the same code via Kudu we do not run into this
issue. This seemed to start when we setup continuous deploy through
Appveyor.</p>
<p>Thanks again for your assistance.</p>
<p>Error<br>
The following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.<br>
Description: An unhandled exception occurred during the execution
of the current web request. Please review the stack trace for more
information about the error and where it originated in the
code.</p>
<p>Exception Details: System.EntryPointNotFoundException: The
following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.</p>
<p>Source Error:<br>
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location
of the exception can be identified using the exception stack trace
below.</p>
<p>Stack Trace:</p>
<p>[EntryPointNotFoundException: The following errors occurred
while attempting to load the app. - No assembly found containing an
OwinStartupAttribute. - No assembly found containing a Startup or
[AssemblyName].Startup class. To disable OWIN startup discovery,
add the appSetting owin:AutomaticAppStartup with a value of "false"
in your web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.]<br>
Microsoft.Owin.Host.SystemWeb.OwinBuilder.GetAppStartup() +357
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
+28 System.Threading.LazyInitializer.EnsureInitializedCore(T&
target, Boolean& initialized, Object& syncLock, Func`1
valueFactory) +86
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication
context) +91
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr
appContext, HttpContext context, MethodInfo[] handlers) +418
System.Web.HttpApplication.InitSpecial(HttpApplicationState state,
MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr
appContext, HttpContext context) +336
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr
appContext) +296</p></div>Erik Schlegeltag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T19:38:57Z2015-07-09T19:38:58ZExperiencing issues deploying to Azure Website<div><p>Hi Erik</p>
<p>I can’t explain why you see a difference using different
deployment technologies but what you’ve done in the
web.config issue will fix the issue.</p>
<p>Basically, Owin middleware has been into the project to support
authentication but we are not doing authentication. However, the
Owin runtime is still trying to discover a class decorated with the
Startup attribute, like this:</p>
<p>[assembly: OwinStartup(typeof(Startup))] namespace
SomeNamespace</p>
<p>This would give Owin a gateway into running code to configure
authN.</p>
<p>So, another way to solve the problem would be to remove all Owin
related Nuget packages. We aren’t using them anyway.</p>
<p>Cheers</p>
<p>Brad</p>
<p>From: Erik Schlegel<br>
Sent: 09 July 2015 20:30<br>
To: Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert; Bradley Cotier<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>+my colleagues Eric/Brian/Brad</p>
<p>Feodor,</p>
<p>After removing custom errors we’re receiving the following
error which is complaining about Owin startup attribute. Have any
of your other clients on Azure complained about this in the past?
When we deploy the same code via Kudu we do not run into this
issue. This seemed to start when we setup continuous deploy through
Appveyor.</p>
<p>Thanks again for your assistance.</p>
<p>Error<br>
The following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.<br>
Description: An unhandled exception occurred during the execution
of the current web request. Please review the stack trace for more
information about the error and where it originated in the
code.</p>
<p>Exception Details: System.EntryPointNotFoundException: The
following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.</p>
<p>Source Error:<br>
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location
of the exception can be identified using the exception stack trace
below.</p>
<p>Stack Trace:</p>
<p>[EntryPointNotFoundException: The following errors occurred
while attempting to load the app. - No assembly found containing an
OwinStartupAttribute. - No assembly found containing a Startup or
[AssemblyName].Startup class. To disable OWIN startup discovery,
add the appSetting owin:AutomaticAppStartup with a value of "false"
in your web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.]<br>
Microsoft.Owin.Host.SystemWeb.OwinBuilder.GetAppStartup() +357
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
+28 System.Threading.LazyInitializer.EnsureInitializedCore(T&
target, Boolean& initialized, Object& syncLock, Func`1
valueFactory) +86
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication
context) +91
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr
appContext, HttpContext context, MethodInfo[] handlers) +418
System.Web.HttpApplication.InitSpecial(HttpApplicationState state,
MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr
appContext, HttpContext context) +336
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr
appContext) +296</p></div>Bradley Cotiertag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T19:45:40Z2015-07-09T19:45:40ZExperiencing issues deploying to Azure Website<div><p>I don’t see us referencing Owin anywhere in our code. I
don’t think that’s it as our deployment worked fine
with Kudu, and works fine locally.</p>
<p>Erik</p>
<p>From: Bradley Cotier<br>
Sent: Thursday, July 9, 2015 3:39 PM<br>
To: Erik Schlegel; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>Hi Erik</p>
<p>I can’t explain why you see a difference using different
deployment technologies but what you’ve done in the
web.config issue will fix the issue.</p>
<p>Basically, Owin middleware has been into the project to support
authentication but we are not doing authentication. However, the
Owin runtime is still trying to discover a class decorated with the
Startup attribute, like this:</p>
<p>[assembly: OwinStartup(typeof(Startup))] namespace
SomeNamespace</p>
<p>This would give Owin a gateway into running code to configure
authN.</p>
<p>So, another way to solve the problem would be to remove all Owin
related Nuget packages. We aren’t using them anyway.</p>
<p>Cheers</p>
<p>Brad</p>
<p>From: Erik Schlegel<br>
Sent: 09 July 2015 20:30<br>
To: Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert; Bradley Cotier<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>+my colleagues Eric/Brian/Brad</p>
<p>Feodor,</p>
<p>After removing custom errors we’re receiving the following
error which is complaining about Owin startup attribute. Have any
of your other clients on Azure complained about this in the past?
When we deploy the same code via Kudu we do not run into this
issue. This seemed to start when we setup continuous deploy through
Appveyor.</p>
<p>Thanks again for your assistance.</p>
<p>Error<br>
The following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.<br>
Description: An unhandled exception occurred during the execution
of the current web request. Please review the stack trace for more
information about the error and where it originated in the
code.</p>
<p>Exception Details: System.EntryPointNotFoundException: The
following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.</p>
<p>Source Error:<br>
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location
of the exception can be identified using the exception stack trace
below.</p>
<p>Stack Trace:</p>
<p>[EntryPointNotFoundException: The following errors occurred
while attempting to load the app. - No assembly found containing an
OwinStartupAttribute. - No assembly found containing a Startup or
[AssemblyName].Startup class. To disable OWIN startup discovery,
add the appSetting owin:AutomaticAppStartup with a value of "false"
in your web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.]<br>
Microsoft.Owin.Host.SystemWeb.OwinBuilder.GetAppStartup() +357
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
+28 System.Threading.LazyInitializer.EnsureInitializedCore(T&
target, Boolean& initialized, Object& syncLock, Func`1
valueFactory) +86
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication
context) +91
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr
appContext, HttpContext context, MethodInfo[] handlers) +418
System.Web.HttpApplication.InitSpecial(HttpApplicationState state,
MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr
appContext, HttpContext context) +336
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr
appContext) +296</p></div>Erik Schlegeltag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T20:00:53Z2015-07-09T20:00:54ZExperiencing issues deploying to Azure Website<div><p>Feodor,</p>
<p>I can confirm that I can publish our .NET website from my local
to Azure, and the site is coming up with no issues. The issue only
happens when I try to deploy from Appveyor.</p>
<p>Can you please advise on what can be causing this issue?</p>
<p>Thanks,</p>
<p>Erik</p>
<p>From: Erik Schlegel<br>
Sent: Thursday, July 9, 2015 3:45 PM<br>
To: Bradley Cotier; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>I don’t see us referencing Owin anywhere in our code. I
don’t think that’s it as our deployment worked fine
with Kudu, and works fine locally.</p>
<p>Erik</p>
<p>From: Bradley Cotier<br>
Sent: Thursday, July 9, 2015 3:39 PM<br>
To: Erik Schlegel; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>Hi Erik</p>
<p>I can’t explain why you see a difference using different
deployment technologies but what you’ve done in the
web.config issue will fix the issue.</p>
<p>Basically, Owin middleware has been into the project to support
authentication but we are not doing authentication. However, the
Owin runtime is still trying to discover a class decorated with the
Startup attribute, like this:</p>
<p>[assembly: OwinStartup(typeof(Startup))] namespace
SomeNamespace</p>
<p>This would give Owin a gateway into running code to configure
authN.</p>
<p>So, another way to solve the problem would be to remove all Owin
related Nuget packages. We aren’t using them anyway.</p>
<p>Cheers</p>
<p>Brad</p>
<p>From: Erik Schlegel<br>
Sent: 09 July 2015 20:30<br>
To: Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert; Bradley Cotier<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>+my colleagues Eric/Brian/Brad</p>
<p>Feodor,</p>
<p>After removing custom errors we’re receiving the following
error which is complaining about Owin startup attribute. Have any
of your other clients on Azure complained about this in the past?
When we deploy the same code via Kudu we do not run into this
issue. This seemed to start when we setup continuous deploy through
Appveyor.</p>
<p>Thanks again for your assistance.</p>
<p>Error<br>
The following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.<br>
Description: An unhandled exception occurred during the execution
of the current web request. Please review the stack trace for more
information about the error and where it originated in the
code.</p>
<p>Exception Details: System.EntryPointNotFoundException: The
following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.</p>
<p>Source Error:<br>
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location
of the exception can be identified using the exception stack trace
below.</p>
<p>Stack Trace:</p>
<p>[EntryPointNotFoundException: The following errors occurred
while attempting to load the app. - No assembly found containing an
OwinStartupAttribute. - No assembly found containing a Startup or
[AssemblyName].Startup class. To disable OWIN startup discovery,
add the appSetting owin:AutomaticAppStartup with a value of "false"
in your web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.]<br>
Microsoft.Owin.Host.SystemWeb.OwinBuilder.GetAppStartup() +357
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
+28 System.Threading.LazyInitializer.EnsureInitializedCore(T&
target, Boolean& initialized, Object& syncLock, Func`1
valueFactory) +86
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication
context) +91
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr
appContext, HttpContext context, MethodInfo[] handlers) +418
System.Web.HttpApplication.InitSpecial(HttpApplicationState state,
MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr
appContext, HttpContext context) +336
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr
appContext) +296</p></div>Erik Schlegeltag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T20:00:54Z2015-07-09T20:00:55ZExperiencing issues deploying to Azure Website<div><p>Yes it is strange but I’ve seen that error many times and
those are the fixes.</p>
<p>Is the CI build server perhaps holding on to some files from
builds past and is uploading them to the server? i.e. – is an
old build continually being uploaded? That would also explain why
we get a 404 when hitting the new URL, as that version of the
website is not being deployed. Are there any folders on the CI
build server that you could clear down?</p>
<p>From: Erik Schlegel<br>
Sent: 09 July 2015 20:45<br>
To: Bradley Cotier; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>I don’t see us referencing Owin anywhere in our code. I
don’t think that’s it as our deployment worked fine
with Kudu, and works fine locally.</p>
<p>Erik</p>
<p>From: Bradley Cotier<br>
Sent: Thursday, July 9, 2015 3:39 PM<br>
To: Erik Schlegel; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>Hi Erik</p>
<p>I can’t explain why you see a difference using different
deployment technologies but what you’ve done in the
web.config issue will fix the issue.</p>
<p>Basically, Owin middleware has been into the project to support
authentication but we are not doing authentication. However, the
Owin runtime is still trying to discover a class decorated with the
Startup attribute, like this:</p>
<p>[assembly: OwinStartup(typeof(Startup))] namespace
SomeNamespace</p>
<p>This would give Owin a gateway into running code to configure
authN.</p>
<p>So, another way to solve the problem would be to remove all Owin
related Nuget packages. We aren’t using them anyway.</p>
<p>Cheers</p>
<p>Brad</p>
<p>From: Erik Schlegel<br>
Sent: 09 July 2015 20:30<br>
To: Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert; Bradley Cotier<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>+my colleagues Eric/Brian/Brad</p>
<p>Feodor,</p>
<p>After removing custom errors we’re receiving the following
error which is complaining about Owin startup attribute. Have any
of your other clients on Azure complained about this in the past?
When we deploy the same code via Kudu we do not run into this
issue. This seemed to start when we setup continuous deploy through
Appveyor.</p>
<p>Thanks again for your assistance.</p>
<p>Error<br>
The following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.<br>
Description: An unhandled exception occurred during the execution
of the current web request. Please review the stack trace for more
information about the error and where it originated in the
code.</p>
<p>Exception Details: System.EntryPointNotFoundException: The
following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.</p>
<p>Source Error:<br>
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location
of the exception can be identified using the exception stack trace
below.</p>
<p>Stack Trace:</p>
<p>[EntryPointNotFoundException: The following errors occurred
while attempting to load the app. - No assembly found containing an
OwinStartupAttribute. - No assembly found containing a Startup or
[AssemblyName].Startup class. To disable OWIN startup discovery,
add the appSetting owin:AutomaticAppStartup with a value of "false"
in your web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.]<br>
Microsoft.Owin.Host.SystemWeb.OwinBuilder.GetAppStartup() +357
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
+28 System.Threading.LazyInitializer.EnsureInitializedCore(T&
target, Boolean& initialized, Object& syncLock, Func`1
valueFactory) +86
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication
context) +91
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr
appContext, HttpContext context, MethodInfo[] handlers) +418
System.Web.HttpApplication.InitSpecial(HttpApplicationState state,
MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr
appContext, HttpContext context) +336
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr
appContext) +296</p>
<p>From: Feodor Fitsner [mailto:tender2+dd1b64204</p></div>Bradley Cotiertag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T22:59:00Z2015-07-09T22:59:00ZExperiencing issues deploying to Azure Website<div><p>Is it ASP.NET 5 (vNext) app?</p>
<ul>
<li>Feodor</li>
</ul></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T23:32:55Z2015-07-09T23:32:55ZExperiencing issues deploying to Azure Website<div><p>ASP.NET 5</p></div>Erik Schlegeltag:help.appveyor.com,2012-11-13:Comment/373465652015-07-09T23:37:28Z2015-07-09T23:37:28ZExperiencing issues deploying to Azure Website<div><p>No. Whatever the latest stable is (4.6?)</p>
<p>Sent from my Windows Phone</p>
<hr></div>Eric Rozelltag:help.appveyor.com,2012-11-13:Comment/373465652015-07-10T00:38:36Z2015-07-10T00:38:36ZExperiencing issues deploying to Azure Website<div><p>OK, because there is an issue with publishing ASP.NET 5 <a>
apps: http://help.appveyor.com/discussions/suggestions/698-batch-de...</a></p>
<p>Other than that it's hard to say what goes wrong while
publishing your app. Things to try: 1) check what you have in Web
Deploy package and 2) use FTP to see what you are getting after
deployment.</p>
<ul>
<li>Feodor</li>
</ul></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373465652015-07-10T08:01:04Z2015-07-10T08:01:04ZExperiencing issues deploying to Azure Website<div><p>Hi</p>
<p>We are currently using .NET 4.5.2 as we hit a code related
problem using .NET4.6.</p>
<p>Cheers</p>
<p>Brad</p>
<p>From: Erik Schlegel<br>
Sent: 09 July 2015 21:01<br>
To: Bradley Cotier; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>Feodor,</p>
<p>I can confirm that I can publish our .NET website from my local
to Azure, and the site is coming up with no issues. The issue only
happens when I try to deploy from Appveyor.</p>
<p>Can you please advise on what can be causing this issue?</p>
<p>Thanks,</p>
<p>Erik</p>
<p>From: Erik Schlegel<br>
Sent: Thursday, July 9, 2015 3:45 PM<br>
To: Bradley Cotier; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>I don’t see us referencing Owin anywhere in our code. I
don’t think that’s it as our deployment worked fine
with Kudu, and works fine locally.</p>
<p>Erik</p>
<p>From: Bradley Cotier<br>
Sent: Thursday, July 9, 2015 3:39 PM<br>
To: Erik Schlegel; Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>Hi Erik</p>
<p>I can’t explain why you see a difference using different
deployment technologies but what you’ve done in the
web.config issue will fix the issue.</p>
<p>Basically, Owin middleware has been into the project to support
authentication but we are not doing authentication. However, the
Owin runtime is still trying to discover a class decorated with the
Startup attribute, like this:</p>
<p>[assembly: OwinStartup(typeof(Startup))] namespace
SomeNamespace</p>
<p>This would give Owin a gateway into running code to configure
authN.</p>
<p>So, another way to solve the problem would be to remove all Owin
related Nuget packages. We aren’t using them anyway.</p>
<p>Cheers</p>
<p>Brad</p>
<p>From: Erik Schlegel<br>
Sent: 09 July 2015 20:30<br>
To: Feodor Fitsner<br>
Cc: Eric Rozell; Brian Lambert; Bradley Cotier<br>
Subject: RE: Experiencing issues deploying to Azure Website
[Problems #2465]</p>
<p>+my colleagues Eric/Brian/Brad</p>
<p>Feodor,</p>
<p>After removing custom errors we’re receiving the following
error which is complaining about Owin startup attribute. Have any
of your other clients on Azure complained about this in the past?
When we deploy the same code via Kudu we do not run into this
issue. This seemed to start when we setup continuous deploy through
Appveyor.</p>
<p>Thanks again for your assistance.</p>
<p>Error<br>
The following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.<br>
Description: An unhandled exception occurred during the execution
of the current web request. Please review the stack trace for more
information about the error and where it originated in the
code.</p>
<p>Exception Details: System.EntryPointNotFoundException: The
following errors occurred while attempting to load the app.<br>
- No assembly found containing an OwinStartupAttribute. - No
assembly found containing a Startup or [AssemblyName].Startup
class. To disable OWIN startup discovery, add the appSetting
owin:AutomaticAppStartup with a value of "false" in your
web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.</p>
<p>Source Error:<br>
An unhandled exception was generated during the execution of the
current web request. Information regarding the origin and location
of the exception can be identified using the exception stack trace
below.</p>
<p>Stack Trace:</p>
<p>[EntryPointNotFoundException: The following errors occurred
while attempting to load the app. - No assembly found containing an
OwinStartupAttribute. - No assembly found containing a Startup or
[AssemblyName].Startup class. To disable OWIN startup discovery,
add the appSetting owin:AutomaticAppStartup with a value of "false"
in your web.config.<br>
To specify the OWIN startup Assembly, Class, or Method, add the
appSetting owin:AppStartup with the fully qualified startup class
or configuration method name in your web.config.]<br>
Microsoft.Owin.Host.SystemWeb.OwinBuilder.GetAppStartup() +357
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.InitializeBlueprint()
+28 System.Threading.LazyInitializer.EnsureInitializedCore(T&
target, Boolean& initialized, Object& syncLock, Func`1
valueFactory) +86
Microsoft.Owin.Host.SystemWeb.OwinHttpModule.Init(HttpApplication
context) +91
System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr
appContext, HttpContext context, MethodInfo[] handlers) +418
System.Web.HttpApplication.InitSpecial(HttpApplicationState state,
MethodInfo[] handlers, IntPtr appContext, HttpContext context) +172
System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr
appContext, HttpContext context) +336
System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr
appContext) +296</p></div>Bradley Cotiertag:help.appveyor.com,2012-11-13:Comment/373465652015-07-10T16:20:40Z2015-07-10T16:20:40ZExperiencing issues deploying to Azure Website<div><p>Never had issues deploying 4.5.2 apps to Azure web sites.</p>
<p>I'm going to create a test ASP.NET app in Visual Studio 2015
targeting 4.5.2 and build/deploy it with AppVeyor. Would it be
enough to reproduce the issue?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/373465652016-04-19T04:56:22Z2016-04-19T04:56:24ZExperiencing issues deploying to Azure Website<div><p>Seems to be only when you use the Azure AD authentication with
the MVC template.</p></div>Eric Schrader