Does SetDefaultPrinter send its own SendMessageTimeout ?
- From: RobCowell <niceguyuk@xxxxxxxxx>
- Date: Fri, 4 Jul 2008 05:34:06 -0700 (PDT)
Subject kind of explains the basics of my question, but here's the
background :-
I'm using the System.Managed namespace in a C#.Net app to set the
default printer via WMI. This is a conversion of an older bit of code
that was using an API call (via P/Invoke). After the call to set the
default printer, the recommended practice was to use another API call,
SendMessageTimeout, to notify other running applications of the
change.
Now that I'm using WMI to set the default printer, do I still need to
call SendMessageTimeout to let other applications know, or does WMI
handle it internally and automatically?
Cheers
Rob
.
- Follow-Ups:
- Prev by Date: How to set the policy 'Password must meet complexity requirements'?
- Next by Date: Re: How to set the policy 'Password must meet complexity requirements'?
- Previous by thread: How to set the policy 'Password must meet complexity requirements'?
- Next by thread: Re: Does SetDefaultPrinter send its own SendMessageTimeout ?
- Index(es):
Relevant Pages
|
|
