One of the reasons why I run Windows Server 2003 on my notebook is that "Services without Components" (managed incarnation is System.EnterpriseServices.ServiceDomain) didn't work on XP. If you just touch the ServiceConfig or ServiceDomain classes on XP, you get rewarded with a PlatformNotSupportedException, because the unmanaged implementation of that feature was present, but not quite-as-perfect-as-it-should-be on XP. That will soon be history. Windows XP SP2 and the COM+ 1.5 Rollup Package 6 will fix that and will bring COM+ 1.5 pretty much on par with Windows Server 2003.

Tuesday, May 18, 2004 3:09:09 PM UTC
Actually I had an argument with a developer recently when he told me it worked on his WinXP machine. I told him it couldn't possibly and pointed him at all the documentation that said it wouldn't work. He then showed me it working!!! He didn't have XP sp 2 installed... but after looking through all the windows updates etc he had we finally tracked it down to: Windows XP Hotfix 828741. Without it the familiar PlatformNotSupportedException and with it success. So it anyone needs to use ServiceDomains today on WinXP just look for this Hotfix (ps you should have it installed anyway since I think it is associated with removing the Sasser exploit).
Alex James
Saturday, July 31, 2004 3:28:11 AM UTC
What about the host for SWC's? Not only do you give up several key services using SWCs (eg queuing, pooling), but you also lose the host, no? What about the cool v.1.5 hosting niceties like application pooling? Also, it also means you lose the automatic DCOM, right? You have to then roll your own remoting if I understand things right.

I'm still learning about this stuff so I may be missing something....

Thanks
Andy Smith
Comments are closed.