Visual Studio seems to kill singleton instance of a WinFX service

I am using a service that is configured to run as a singleton instance,
hosted in IIS.
Whenever I start the same client out of Visual Studio I can see that the
instance of the service is reinitalized. I could also see it by attaching a
debugger, because I hit the constructor every time the client connects.

When I start the client directly e.g. out of Windows Explorer I get the
original instance.

Has anyone observed a similar behaviour concerning singleton services?

Did you check that InstanceID back, that always the same in that case at
least on my computer
Arkady

"Stefan Hinterscheid" <StefanHinterscheid@discussions.microsoft.com> wrote
in message news:88307F4E-991E-42CB-AED2-B0992E018108@microsoft.com...
>I am using a service that is configured to run as a singleton instance,
> hosted in IIS.
> Whenever I start the same client out of Visual Studio I can see that the
> instance of the service is reinitalized. I could also see it by attaching
> a
> debugger, because I hit the constructor every time the client connects.
>
> When I start the client directly e.g. out of Windows Explorer I get the
> original instance.
>
> Has anyone observed a similar behaviour concerning singleton services?

Stefan,

Do you see the same behavior when using the Instancing Sample? You can find
this sample under WCF Technology Samples/Basic WCF Technology Samples/Service
Samples/Instancing.

Thanks,