vendredi 8 août 2014

Accueil - Difficulté exécutant OwinHost depuis la ligne de commande - Stack Overflow


I have been working through various OWIN tutorials and have consistently encountered the same problem; the applications work fine when I launch them from within Visual Studio (2013) using F5, but when I navigate via the command line to Owinhost.exe and launch it, I get the same error every time:


Error: System.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.



Of the various suggestions online, I have:


1) Made sure that the output directory is just "/bin" and not "/bin/debug".


2) Defined the assembly in my startup class:


[assembly: OwinStartup(typeof(StartUpDemo.Startup))]

3) Set my web.config


<appSettings>
<add key="owin:AppStartup" value="StartUpDemo.Startup"/>
</appSettings>

4) I have also tried disabling OWIN startup discovery using appSetting owin:AutomaticAppStartup with a value of "false" all to no avail.


It seems like OwinHost.exe is not even finding my application .dll, but as I mentioned before, it works fine in VS2013 when I launch it from within the IDE. I have changed the project settings in the "web" tab to use OwinHost, but otherwise the project setup is normal. Does VS2013 have information that I need to pass into the command line to get it to work correctly? Am I missing something in my configuration?



I have been working through various OWIN tutorials and have consistently encountered the same problem; the applications work fine when I launch them from within Visual Studio (2013) using F5, but when I navigate via the command line to Owinhost.exe and launch it, I get the same error every time:


Error: System.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.



Of the various suggestions online, I have:


1) Made sure that the output directory is just "/bin" and not "/bin/debug".


2) Defined the assembly in my startup class:


[assembly: OwinStartup(typeof(StartUpDemo.Startup))]

3) Set my web.config


<appSettings>
<add key="owin:AppStartup" value="StartUpDemo.Startup"/>
</appSettings>

4) I have also tried disabling OWIN startup discovery using appSetting owin:AutomaticAppStartup with a value of "false" all to no avail.


It seems like OwinHost.exe is not even finding my application .dll, but as I mentioned before, it works fine in VS2013 when I launch it from within the IDE. I have changed the project settings in the "web" tab to use OwinHost, but otherwise the project setup is normal. Does VS2013 have information that I need to pass into the command line to get it to work correctly? Am I missing something in my configuration?


0 commentaires:

Enregistrer un commentaire