Breezback

UDP Client Server

//Create an instance of UdpClient.
UdpClient udpClient = new UdpClient(serverName, SAMPLEUDPPORT);
Byte[] inputToBeSent = new Byte[256];
inputToBeSent = System.Text.Encoding.ASCII.GetBytes(whatEver.ToCharArray());
IPHostEntry remoteHostEntry = Dns.GetHostByName(serverName);
IPEndPoint remoteIpEndPoint = new IPEndPoint(remoteHostEntry.AddressList[0], SAMPLEUDPPORT);
int nBytesSent = udpClient.Send(inputToBeSent, inputToBeSent.Length);
Byte[] received = new Byte[512];
received = udpClient.Receive(ref remoteIpEndPoint);
String dataReceived = System.Text.Encoding.ASCII.GetString(received);
Console.WriteLine(dataReceived);
udpClient.Close();

I started this project because of the lack of resources for the older, but still highly
used SNMP protocol. The SNMP protocol still remains the de facto standard when it comes
to network monitoring and management.

IDataProvider - Implement Provider Model C#

clipped from www.code-magazine.com

In the CreateDataAdapter method you will have to do a couple of things to create an instance of a specific data adapter. First you will need to initialize the appropriate provider based on the information in the configuration file. The InitProvider method is responsible for this and will be shown in the next section. After the appropriate DataProvider class is loaded the CreateDataAdapter method on that specific provider will be called. This is where the SqlDataAdapter or the OleDbDataAdapter or the OracleDataAdapter is created.

public static IDbDataAdapter CreateDataAdapter(
string SQL, string ConnectString)
{
  IDbDataAdapter da;

  // Make sure provider is created
  InitProvider();

  da = DataProvider.CreateDataAdapter();

  da.SelectCommand = CreateCommand(SQL,
   ConnectString, false);

  return da;
}
In Visual Basic

tcp

clipped from en.wikipedia.org

A TCP segment consists of two sections:

header

data

The TCP header[2] consists of 11 fields, of which only 10 are required. The eleventh field is optional (pink background in table) and aptly named "options".

TCP Header
Bit offset Bits 0–3 4–7 8–15 16–31
0 Source port Destination port
32 Sequence number
64 Acknowledgment number
96 Data offset Reserved CWR ECE URG ACK PSH RST SYN FIN Window
128 Checksum Urgent pointer
160 Options (optional)
160/192+
Data

Source port (16 bits) – identifies the sending port

TCP diagram

clipped from freebie.fatpipe.org

MSI parameter driven

clipped from blogs.msdn.com

Adding msi parameters in Visual Studio Setup Project

I can’t find how and where to add the parameter list of the msi.

I had to modify a setup project of which creates an msi for an application.

During modification I had to add an extra parameter that should be given to the msi during installation.

While I searched I found only how to read the parameters supplied from command line using Context.Parameters.

But I can’t find at any place where to specify the parameters those can be supplied with msi. Finally I found it and so I am writing here as it may be useful to others.

In property Pages of Install, in the option CustomEvents, we can specify the arguments.

For example if for our msi, we have to add 2 parameters INSTLOG & X

Then in the CustomEvents, we have to specify it as:

/INSTLOG=”[INSTLOG]” /X=”[X]”

Breezback

Adding msi parameters in Visual Studio Setup Project

Blog Archive