Hello,

I have an ASP application that prints from the server using Win32 spooler (see http://support.microsoft.com/kb/322091/EN-US/). Essentially, my program was written for an old ASP program to allow it to print raw data to a barcode printer. It runs in server side javascript. My print functions are in a class written in C# and is exposed for COM Interop and has a CPU Target of Any CPU.

The program works perfectly on Std. Windows 2003 or in Windows 2003 64 bit edition as long as IIS is set for 32 bit mode.

I have tried setting the Target CPU to x64, but it will not compile. I get the following error:

Error 1 File "C:\Programs\ZebraLabels\bin\ZebraLabels.dll" is not a valid assembly. ZebraLabels
Warning 2 Possible problem detected while building assembly 'ZebraLabels': Referenced assembly 'mscorlib.dll' targets a different processor
Warning 3 Possible problem detected while building assembly 'ZebraLabels': Referenced assembly 'System.Data.dll' targets a different processor

Interestingly enough, I wrote a windows form application in c# that calls my printer class using the Target CPU as x64 and it works! So, it looks like the problem is in IIS.

My question, then, is does anyone know how to fix this, OR, does anyone know how to print for VB or C# raw to a printer in any other way?

Thanks!

Hubman

Hello,

I have an update. I have found that my class (that calls winspool.drv through win32 API calls for RAW printing) works in 64 bit mode IIS when used in a ASPX page created with c#. This page is pure .NET and calls my class "code behind" in c#. I still have not been able to call the class through server side javascript (ex- var bc = new ActiveXObject("CFW.Barcode.ZebraLabels");).

So, if you're writing pure ASP.NET pages with "code behind" I think the code is executing in 64 bit mode and calling the 64 bit version of winspool.drv, but this is just a guess.

It may also be related to server side javascript as well.

Comments?