Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Hardware & Devices
  4. Printer-Windows application

Printer-Windows application

Scheduled Pinned Locked Moved Hardware & Devices
helpcsharpsysadmintutorial
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B Offline
    B Offline
    balu12345
    wrote on last edited by
    #1

    Hi, In my case..there is a server and client.. assume PC-A as server,PC-B as client. Printer is physically connected to PC-A server,which is now can be called as Print Server(i.e,PC-A). The problem is as below.. Here the user is at **PC-B(client machine),**then he opens a normal word document(not through my application) and gives the normal file print...Then Immediately i have to invoke my .net windows application which is used for some accounting purpose. To my knowledge I thought to write a service to watch/catch the spool file generation at client PC-B machine and then it should invoke the windows application..But actually the spool file is generated at Server end but at client end... Kindly guide me to resolve this issue..

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups