• Advertisement
Sign in to follow this  
  • entries
  • comments
  • views


Sign in to follow this  


I was recently bitten by a bug in the .NET framework. Apparently, calling ChannelServices.UnregisterChannel(foo) doesn't actually unregister the channel properly and close the socket. Subsequent attempts to call RegisterChannel() for a socket on the same port fail with an "Only one usage of each socket address is normally permitted" exception. I worked around it by leaving the channel open for the entire lifetime of the application.

ReactOS 0.2.4 was released a few days ago. Download it here, or have a peek at the changelog here.
Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Advertisement