StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHttpHandlers x64 problem
text
Body
copied!<p>I developed a .Net 3.5 x64 web application that includes a custom HttpHandler in the config:</p> <pre><code><add path="*.class1" verb="GET" type="ClassLibrary1.Class1Handler"/> </code></pre> <p>This works when the platform target for ClassLibrary1 is set at x86.<br> However, when I set this to x64 I get the following error when I run web application starts (it compiles just fine):</p> <blockquote> <p>Configuration Error</p> <p>Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. </p> <p>Parser Error Message: Could not load file or assembly 'ClassLibrary1, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.</p> </blockquote> <p>Does this mean that a HttpHandler can be compiled at x86 only?<br> That doesn't make much sense to me.<br> Does anyone have an idea of what could be going on?</p> <p>Edit 1:<br> The ClassLibrary1 project is just an empty class library project with a single HttpHandler added (which is also empty).</p> <p>Edit 2:<br> I am also getting these warning messages when compiling, I am pretty sure they have something to do with this problem:</p> <blockquote> <p>Assembly generation -- Referenced assembly 'mscorlib.dll' targets a different processor HttpTest</p> </blockquote> <p>Edit 3:<br> I manually edited the project file to force references to the x64 assemblies, like this:</p> <blockquote> <p><Reference Include="$(Windir)\Microsoft.NET\Framework64\v2.0.50727\System.dll"/></p> </blockquote> <p>This does supress the above warning message, but the problem isn't resolved.</p> <p>Thanks!</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload