John
Tue Oct 05 14:41:42 CDT 2004
Your solution is probably the best way if you're up against the 32 proc
limitation. I've looked into doing something kind of similiar - not a
services.exe .Net version, but a process that hosted managed code and had
managed callers limited to a specific problem domain.
Unfortunatly Compact Framework V1 doesn't have XML serialization, so if you
want to get complicated data objects across processes that may prove tricky.
I don't have any words of wisdom for you here - my managed process got cut.
I would recommend looking around on the Internet or getting ideas at
microsoft.public.dotnet.framework.compactframework. There may be clever
ways to solve this problem that aren't immediately obvious.
--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation
Check out the new CE Networking Team Blog at
http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.
"Geir Frimann Andersen" <GeirFrimannAndersen@discussions.microsoft.com>
wrote in message news:214C6BF0-AFFD-4CEA-9B75-6D5EE2BDBD3B@microsoft.com...
> Hmm, that's to bad... I'm developing a applications for the Qtek 2020 /MDA
> II,
> and it have a lot of processes running as is, and there is a limit of 32
> processes running.
> Maybe I should develop a .NET Service.exe, to run .NET dlls, so it will be
> only one process for all .NET applications. Any thoughts?
>
> "John Spaith [MS]" wrote:
>
>> I'm almost sure that the answer is no. Services.exe will only load
>> native
>> components DLLs. I don't think it's possible to hack VB.Net such that it
>> generates a dll that can be used directly from native, but maybe it is.
>>
>> I'd recommend against doing even if you can figure out a way to do it.
>> Services.exe is a system level process. All the the ramifications of
>> running managed in services.exe have not been fully considered.
>>
>> --
>> John Spaith
>> Software Design Engineer, Windows CE
>> Microsoft Corporation
>>
>> Check out the new CE Networking Team Blog at
>>
http://blogs.msdn.com/cenet/.
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> You assume all risk for your use. © 2003 Microsoft Corporation. All
>> rights
>> reserved.
>>
>> "Geir Frimann Andersen" <GeirFrimannAndersen@discussions.microsoft.com>
>> wrote in message
>> news:B4D01242-D827-4271-BCE2-CE67B4FE2D8D@microsoft.com...
>> > Is it possible to develop a service DLL in VB.NET that can be
>> > registered
>> > and
>> > run as a service on WM2003?
>>
>>
>>