Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
C# Community
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Home
Forums
Components & Controls
Reporting / Printing
Error on "Claim" with OPOS Printers
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="Taesith" data-source="post: 118128" data-attributes="member: 28126"><p>OK, I've been wracking my brain for a few days now, can't seem to find a solution to a problem I'm having with OPOS printers. Here's my scenario; </p><p></p><p>I have a winforms application written in vs2005 vb.net, we'll call it program.exe</p><p></p><p>program.exe launches other programs (dlls) that contain various winforms. we'll call those module1.dll, module2.dll, etc. program.exe is basically a launcher app, mdi parent, that contains references to the DLLs.</p><p></p><p>Now, I am trying to write a bit of code that uses OPOS to communicate with an EPSON TM-U230M. </p><p></p><p>If I put the code in the executable project (program.exe) everything works fine. I can open, claim, and print. However, if I put the code in one of the DLL projects, i get an error during the ClaimDevice method (if using OPOS generic drivers, the error is "106", if using microsoft.pointofservice the "Claim" method throws an exception).</p><p></p><p>I have tried anything I could think of; adding a separate executable project to contain all of the OPOS code, calling the new executable with Process.Start and some command line parms, but nothing seems to alleviate the issue.</p><p></p><p>One other point, as i mentioned before, program.exe contains references to multiple projects (built as DLLs). In one of those projects, this works (it's an invoicing application), however, in another DLL project, this fails. I can't seem to find any difference in the two.</p><p></p><p>Thanks for any help...</p></blockquote><p></p>
[QUOTE="Taesith, post: 118128, member: 28126"] OK, I've been wracking my brain for a few days now, can't seem to find a solution to a problem I'm having with OPOS printers. Here's my scenario; I have a winforms application written in vs2005 vb.net, we'll call it program.exe program.exe launches other programs (dlls) that contain various winforms. we'll call those module1.dll, module2.dll, etc. program.exe is basically a launcher app, mdi parent, that contains references to the DLLs. Now, I am trying to write a bit of code that uses OPOS to communicate with an EPSON TM-U230M. If I put the code in the executable project (program.exe) everything works fine. I can open, claim, and print. However, if I put the code in one of the DLL projects, i get an error during the ClaimDevice method (if using OPOS generic drivers, the error is "106", if using microsoft.pointofservice the "Claim" method throws an exception). I have tried anything I could think of; adding a separate executable project to contain all of the OPOS code, calling the new executable with Process.Start and some command line parms, but nothing seems to alleviate the issue. One other point, as i mentioned before, program.exe contains references to multiple projects (built as DLLs). In one of those projects, this works (it's an invoicing application), however, in another DLL project, this fails. I can't seem to find any difference in the two. Thanks for any help... [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Components & Controls
Reporting / Printing
Error on "Claim" with OPOS Printers
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
Top
Bottom