Home/ Questions/Q 6838411
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-26T23:35:37+00:00

OK, this is a minor issue… but still irritating nonetheless. In MSVS 2008 .NET

  • 0

OK, this is a minor issue… but still irritating nonetheless.

In MSVS 2008 .NET 3.5 I IPAdress.Address was a long and I simply used

if(subnet == subnetmask.Address & addr.Address) { ... }

And then now i just installed MSVS 2010, still using .NET 3.5 but somehow it tells me the IPAddress.Address is obsolete.

I can still wrap a BitConvertor in BitConverter.ToInt64(subnet.GetAddressBytes(), 0) but it feels like i am going backwards. Is there a more elegant way or a built-in function to check for subnet?

Thanks.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The reason for IPAddress.Address to be marked as obsolete is:

    This property has been deprecated. It is address family dependent.
    Please use IPAddress.Equals method to perform comparisons.
    http://go.microsoft.com/fwlink/?linkid=14202

    With IPv6 coming, depending on specific features of IPv4 should be regarded as obsolete. Your workaround has the same problem – dependency on IPv4. I think that you have two options:

    • Keep your application IPv4-only and supress the obsolete warning.
    • Find out how to make the functionality work in both IPv6 and IPv4.
    • 0