Cancelado

Need to access windows message queue from a SERVICE(repost)

Problem:? I have written a service which uses a third party API.? This third party api would normally raise events when used in a Windows Form application.? Because i am using the api in a SERVICE, the events are not being raised to my service code.?

Task:? I need to access the windows message queue via a hook or another method to continuously retrieve the messages in the queue.?

I basically need to do this:

[[url removed, login to view]][1]

in C#? vs 2008 .net 3.5

Here is an excerpt from the third party companies support group:

Nope, I believe MSMQ is a tool from MS that allows apps to talk to each other. What I'm referring to is the actual messaging that's going on in Windows. Messages, like mouse movements, keyboard events, and XTAPI callbacks are all put on the same messaging queue for processing. Intercepting these messages is called hooking. I don't know a whole lot about the process, and perhaps there might be some updated libraries for this, but you can access these messages via MFC.

## Deliverables

Must be done in C# and .net 3.5

Code must continuously, via? an infinite loop or etc, retrieve messages from the program message queue.

Habilidades: Engenharia, Microsoft, MySQL, PHP, Gestão de projetos, Arquitetura de software, Teste de Software, Área de trabalho do Windows

Ver mais: windows programmer, us communities, need programmer php, msmq 3, microsoft win32, loop net, need raise, access group, third party api, microsoft mfc, windows net application, windows form application, windows api, windows 2008, rtc, queue, programmer php, message queue, process access, dg, application microsoft access, php api service, windows keyboard hook, excerpt, party keyboard

Acerca do Empregador:
( 50 comentários ) United States

ID do Projeto: #3023125

2 freelancers estão ofertando em média $315 para este trabalho

stephencleary

See private message.

$425 USD in 14 dias
(51 Comentários)
6.6
ujnvw

See private message.

$204 USD in 14 dias
(3 Comentários)
1.5