Ideas for new features & functions
Moderators: JRL, Dorian (MJT support)
-
Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
-
Contact:
Post
by Marcus Tettmar » Wed Feb 26, 2014 4:45 pm
This tool converts VBScript to a .exe. Macro Scheduler Pro already converts macro scheduler scripts to exes.
If you then want to launch one of those exes as a service you can do that with SrvAny or similar:
http://support.microsoft.com/kb/137890
Frankly - before people get excited - I don't see the benefit. It certainly won't have any benefits for 99.99% of macros. Most macros - indeed the main point of Macro Scheduler macros - perform user simulation and control a user interface. Since no UI is present when the machine is locked/logged out there is little to gain from having the macro run as a service.
If you have a macro that does NOT need to see a UI and does NOT need to access any user level resource then it might be useful but then I'd wonder why you are using Macro Scheduler anyway
Since most macros need to run as a user and access UI elements/simulate user activity it is better to run them as user level processes on startup. Making them run as a service won't help.
-
newuser
- Pro Scripter
- Posts: 64
- Joined: Tue Jun 11, 2013 4:53 pm
Post
by newuser » Thu Feb 27, 2014 2:11 pm
SrvAny is consider third party tool in this case. I hope it would be a standalone MS tool.
Marcus Tettmar wrote:
If you have a macro that does NOT need to see a UI and does NOT need to access any user level resource then it might be useful but then I'd wonder why you are using Macro Scheduler anyway
Bacause MS have become so powerful, that I could use it for things other than perform user simulation and control a user interface.
