C#

Roink wrote:

But what if you want to constrain the octets to ONLY values from 0 to 255? And what if you really wanna go whole hog and constrain the port to 0 to 65535?

Roink wrote:

As they say in Britain, Brilliant

<br />
@"^(\d{1,2}|1\d\d|2[0-4]\d|25[0-5])\.(\d{1,2}|1\d\d|2[0-4]\d|25[0-5])\.(\d{1,2}|1\d\d|2[0-4]\d|25[0-5])\.(\d{1,2}|1\d\d|2[0-4]\d|25[0-5]):(\d{1,4}|[0-5]\d\d\d\d|[0-5]\d\d\d\d|6[0-4]\d\d\d|65[0-4]\d\d|655[0-2]\d|6553[0-5])$"<br />

listView1.DrawColumnHeader += new DrawListViewColumnHeaderEventHandler(listView1_DrawColumnHeader);
listView1.DrawItem += new DrawListViewItemEventHandler(listView1_DrawItem);
listView1.DrawSubItem += new DrawListViewSubItemEventHandler(listView1_DrawSubItem);

// Draw sub item event handler
void listView1_DrawSubItem(object sender, DrawListViewSubItemEventArgs e)
{
    e.DrawDefault = true;
}

// Draw item event handler
void listView1_DrawItem(object sender, DrawListViewItemEventArgs e)
{
    /* PUT YOUR CODE HERE */
    //e.Graphics...Draw stuff
    //e.Graphics...Draw stuff

    e.DrawDefault = true;
}

// Draw header event handler
void listView1_DrawColumnHeader(object sender, DrawListViewColumnHeaderEventArgs e)
{
    e.DrawDefault = true;
}

Giorgi Dalakishvili wrote:

Crackers on the other hand have much more knowledge than general users and use advanced tools for cracking.

Giorgi Dalakishvili wrote:

What I suggest is that you put checks at different places in the program and not so obvious. Having a dll called license.dll will attract crackers. On the other hand you can put some code in license.dll which looks like license check but does nothing in reality.

Giorgi Dalakishvili wrote:

Obfuscators make it more difficult but not very much.

dan neely wrote:

only way to effectively limit piracy is to design an app that can't work without talking to servers owned by the company that wrote it.

Paul Conrad wrote:

Require your app to "phone home" and it does keep it on a leash so to speak when it is out in the wild Smile

dan neely wrote:

Just a simple phone home isn't any more effective than any other simple in application check.

dan neely wrote:

You need to store either a critical portion of the data or application functionality on a remote server.

Paul Conrad wrote:

Require your app to "phone home" and it does keep it on a leash so to speak when it is out in the wild

SeMartens wrote:

well there is a library called log4net http://logging.apache.org/log4net/index.html[^].