"Test driven development" - some practical experiences in API development

Since last few years I was reading a lot of discussion about “extreme programing”  and “test driven development”. I decided to explore and apply some of those principles in my own development and within my team. Here are some of the interesting things I would like to share. These experiences are based on a project for developing…

1

Use NetworkInformation classes to get the list of listening ports on your machine

.Net frameworks 2.0 have new addition of Namespace, System.Net.NetworkInformation, it provide a number of interesting classes to extract the network related statistics and state of the machine, it pretty much provide most of the functionality which is exposed by native IPHelper APIs. Earlier I had shown a simple example for getting network availbility event notification. Here…

5

Does your application require customizing System.Net.WebPermission, SocketPermission or DnsPermission settings?

.Net frameworks comes with deefault security settings where components running under Intranet, Internet Zone can only have WebPermission to connect back to the server, from where they are downloaded. Also the component from Intranet zone and Internet zone don’t have any SocketPermission and DnsPermission by default. I am trying to find out some real world usage…

2