Hello MuZzy,
As for the WCF sample, would you tell me which sample is the exact one you
test against? I can try peforming some tests on my side.
Also, for WCF issue, there is a dedicated MSDN forum below:
#Windows Communication Foundation ("Indigo")
http://forums.microsoft.com/msdn/showforum.aspx?forumid=118&siteid=1
Hope this helps.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
MuZZy - 13 Nov 2006 15:50 GMT
Hi Steve,
Thanks for the reply! I actually figured it out - ASP.NET wasn't
registered for my IIS server. When i ran aspnet_regiis.exe it started
working fine. Now it gives some other error but i'm still trying to
figure it out.
> Hello MuZzy,
>
[quoted text clipped - 41 lines]
>
> This posting is provided "AS IS" with no warranties, and confers no rights.
Steven Cheng[MSFT] - 14 Nov 2006 01:29 GMT
Sounds great MuZzy,
Glad that you have figured it out.
Have a good day!
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.
kbuckley17@gmail.com - 22 Dec 2006 16:55 GMT
Hi, I'm working through a problem right now with WCF
I want to make a single service, that has many endpoints. It can
process each endpoint at the same time, but can only process an end
point's messages one at a time.
For example, I have a WCF service that has 2 end points, each one to an
MSMQ queue. I want the service to process the messages coming in one
at a time, but it can process each queue concurrently. So, in this
scenario, the most number of messages it could be processing at one
time would be 2.
I know I can make a service a singleton by using the
[ServiceBehavior( InstanceContextMode = InstanceContextMode.Single]
attribute, but it seems like in this case I want to make the endpoint a
singleton.
Does that make sense?