Hi,
I'm developing a scheduler with VB.NET and .NET 2.0.
I made a Windows Service and a DLL for the event scheduler.
I want to send SMS at scheduled times. I've tested my code on a Windows Form and it works great!

Problem
When the windows service check for Skype is found that is running

When I try to attach Skype from the service, I receive a Wait Timeout error. I believe this is because the authorization screen for a third part component is not able to show up.

Error Message: Wait timeout.
at SKYPE4COMLib.SkypeClass.Attach(Int32 Protocol, Boolean Wait)
at EventSchedulerActions.SkypeSMS.SendSMS(String phone, String message)

Question:
Is there any method to open the 'Allow software....' dialog for an executable using the API? I like to register my app at once with a button.

Thanks in advance
Danilo

Danilo,

I too need this kind of functionality.

I have a simple electronic calendar I wrote for my family running on our home server. As my kids keep forgetting their appointments, I would like the server to send reminders to them. Since the client PCs do not necessarely run when an appointment takes place, I want messages to be sent from a windows service on the server.

A windows service has no windows. So to be able to send messages through Skype, send-SMS requests should be processable even if the GUI based client is not running.

Of obvious reasons, Skype has so far been extremely user centric. Opening for SMS through an API makes scenarios like your scheduler and my calendar interesting, not at least due to the reasonable cost of an SMS through Skype. However the API must be independent of the user to make these scenarios possible. The questions are: Will Skype make this rewrite? How will it change the architecture of Skype? What will the time frame be?

Peter

Hi

I haven't touched the Skype API yet so don't know if this will help but it enabled me to run the linksys cit200 as a service rather than a user application allowing the phone to be connected to Skype all the time that the PC was switched on.

1) Log on to the PC/Server as the user that will be running the service.
2) Run the application and Skype as normal applications and when the authorisation screen comes up click on Allow access (not the one that says for this time only)

Set up the service and Skype as a service if necessary using these user details and it should then be 'pre-authorised' to access Skype

HTH
Mark

When my system service attaches to skype for the first time
I got window if I allow this app. to control skype. I checked remember checkbox and yes.
After that it doesn't asked me again.

You shure that anything else couldn't be wrong?

Well I've finally solved this particular problem. Simply do the following to get your Windows Service communicating with Skype...

- Windows Control Panel
- Administrative Tools
- Services
- Find your Windows Service
- Right click and go to the Service's properties
- Go to the 'Log On' tab
- Select 'Allow service to interact with desktop'
- Click 'OK'
- Now restart the service
- Heh presto, it your service should now communicate ok with Skype!

There are changes with system services and session 0 ("The ability to interact with the desktop") in Vista please see this:

http://www.microsoft.com/whdc/system/vista/services.mspx