(snip)
> Just to make sure...you want the web service to be initialized AFTER you
> do your deployment? If so, how are you doing deployment (XCopy, Setup
> Package, etc)
I need it to be initialized very time IIS restarts and/or the application is
(re-)deployed. I.e. - it should always be running. After reboot, after
restart of IIS, after (re-)install etc. The manner of deployment is not of
concern here.
> I like doing the XCopy method, because I can run it via a batch file.
> If I needed to kick off the initialization of the Web Service After
[quoted text clipped - 13 lines]
>
> Does that help?
Sorry - not really. I don't need to have it started every minute or every
hour or whatever (yes, in practice it may in fact work, but it's not quite
what I need). It should be started as soon as that web site is started (and
of course after (re-)deployment too). A scheduled restart is just a kludge -
I'd like there to be a better way.
Svante
rviray - 29 Sep 2005 20:39 GMT
I guess my point is this...I don't believe that there is an intrinsi
tool (via .NET framework or Windows API) that will help, so we have t
build one...
so...if the client asked me to solve this issue, I would
1. Think about all the scenarios (or at least most of them) when you
application needs to be re-initialized. You mentioned a few...when II
restarts, when you deploy, and other scenarios...
2. Are their any common event hooks or APIs that are called via .NE
CLR, Windows API or IIS API...that we can use to monitor and o
eventually tie into...
- for the .NET CLR there is a profiling tool that I have used in th
past to help troubleshoot issues with various applications...its prett
good to figure out what the CLR is doing at certain points in th
Application life cycle (I have never used it to see what it does t
determine if a web application needs to be initialized o
not...probably try to look at that this weekend)
http://msdn.microsoft.com/msdnmag/issues/01/12/hood/
- for the windows and IIS API calls, I never had to figure those out s
I don't have any resources off hand...
3. Once we figure out all the scenarios that need our attention alon
with figuring out what you need to tap into to...then we have to figur
out how to monitor it... that is how I came up with a Windows Service (
only mentioned SQL Scheduled Job because that is REAL easy to deploy, i
we were to just have an app contact the Web Service..to force
re-initialization if need be...not try to be a Kludge)...the Window
Service is probably one of the easiest thing to create...
Anyway, that is the thought process I would use to figure your issu
out
--
rvira
test@test.com - 30 Sep 2005 21:55 GMT
Can you give us an example of how you are going to use this?
>(snip)
>> Just to make sure...you want the web service to be initialized AFTER you
[quoted text clipped - 31 lines]
>
>Svante