My initial question would be why do you have to "wake up" the windows
service? You could let that run on the machine with the proper crendentials
and then send it jobs through the website that it can pick up on
predetermined time intervals. The windows service could also run your dlls
and it can have an app.config file associated to it to contain data that is
needed like database connection strings.
hope this helps
"Boban Dragojlovic" <news (AT) _N_O_S_P_AM_dragojlovic (DOT) org> wrote
I have an dot net website which calls a class (which is in a project that |
referenced by the website project). I will call the class "WakeUp"
In other words, somepage.aspx.vb instantiates "wakeup" and calls a method
This method ... wakeup.now() ... uses the appropriate mechanism to start a
When I try to run this on my web server, it fails because of lack of
If I add an <identity impersonate="true" ...> section to my web.config
I can give it credentials so that the whole thing works.
The downside, of course, is that then the entire site runs under these
Is there a way that I can assign such administrative credentials (e.g.
impersonation) to only the "wakeup" class, instead of to the entire
Since wakeup.dll is in the website\bin folder, it doesn't have its own