Chris is right. There's no inherent reason that a service can't be 32-bit
that I'm aware of. The only requirement is that anything that runs _at the
kernel level_ needs to be 64-bit. So, if you look at services running on
your machine, you're likely to see that you have 2 .NET Runtime versions.
One 32-bit, one 64-bit. And on my machine, you'll see "TiVo Beacon" running
as a service. And I assure you, they haven't got a 64-bit version! Just
because some thing is a service, doesn't make it inherently kernel mode.
--
Charlie.
http://msmvps.com/xperts64
Andre Da Costa [Extended64] wrote:
> Well, I don't know, I think its time for Charlie and Darrell to come clear
> this up.
> --
>
> "Chris Kushnir" <> wrote in message
> news:...
>> 32bit services will run, i have one i've written for a client and i
>> run/debug it under Win2003 R2 x64.
>>
>> A service is just a program that has a defined interface that allows it
>> to receive messages from the service manager (telling it to start, stop,
>> be notified of hardware changes, ...).
>>
>> The service does not run 'within' the service manager, it is spawned as a
>> distinct process that can be viewed in Task Manager.
>> As such, even though the service manager is 64bit it can spawn either 32
>> or 64bit services.
>>
>> A service is still bound by the normal rules of an app though - a 32bit
>> app can only use 32bit dlls, and 64bit apps can only use 64bit dlls.
>>
>>
>> cmk
Similar Threads
