Home Dashboard Directory Help
Search

WCF Discovery feature in .Net framework cannot be used in Windows XP SP 3 by Ruxo


Status: 

Closed
 as Won't Fix Help for as Won't Fix


3
0
Sign in
to vote
Type: Bug
ID: 588067
Opened: 8/21/2010 11:43:41 AM
Access Restriction: Public
0
Workaround(s)
view
2
User(s) can reproduce this bug

Description

Even in the MSDN library says that WCF Discovery's classes can be used in Windows XP SP 3 but it actually throws an SocketException instead. The exception states as following:

"SocketException (0x80004005): The requested address is not valid in its context"
Details
Sign in to post a comment.
Posted by RomanM on 4/24/2012 at 11:35 AM
I wonder if you can provide an update on this bug mainly on its resolution (since it's marked as resolved) as I am experiencing the same behaviour (Win XP SP3) and cannot find any workaround. Disabling antivirus sw, firewall, network interfaces did not help, neither re-installing .NET Framework.

Thanks
Posted by Ruxo on 9/13/2010 at 10:52 PM
This is the test code snippet:
________________________________________
     class MainClass
     {
        [ServiceContract]
        public interface ITestService{}
            public static void Main (string[] args)
            {
            Console.WriteLine("Begin Test");
            var discoveryClient = new DiscoveryClient(new UdpDiscoveryEndpoint());
                try{
                    discoveryClient.Find(new FindCriteria(typeof(ITestService)));
                } catch (Exception ex){
                    Console.WriteLine("Exception!");
                Console.WriteLine(ex);
                }
                discoveryClient.Close();

            Console.WriteLine("Test Ok... ENTER to end.");
            Console.ReadLine();
            }
________________________________________
As you can see, there is no user code involved in the socket binding process. The program runs fine on Windows 7 and Windows 2008 R2 but for my two XP machines it just crashed with the mentioned exception. All tested machines are IPv6 enabled.
Posted by Microsoft on 9/13/2010 at 8:04 PM
Hello Ruxoz-

Thank you for your feedback on Windows Communication Foundation. The exception you are mentioning is normally hit when trying to bind the socket to an IP address that isn't valid. Can you please check this and if possible try on a machine with a different OS. There are currently no known limitations of the WCF Discovery feature on XP.

Thanks,
Erica
Posted by Microsoft on 8/22/2010 at 9:32 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 8/21/2010 at 5:03 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.