Question

I have a web application , for presentation to my client they ask me to install it on their local server so they can test it , here is my question !?

Is there any way so i can publish uniquely for that server , i did put some limitation but many features in my app are open , so they can make a disk image from server and use it anywhere else ,

Is there any method to use so my web application check if this server is same server ( by hardware id or anything i don’t have any idea ) then start to work !

I saw many codes but they are win forms for generating unique hid , but how can i connect done it with asp .net

EDIT

Could u take a look at this also ,

i am using system.management class

is this reliable i mean are they unique ?

  private string GetUniqueID()
    {
        string cpuInfo = string.Empty;
        ManagementClass mc = new ManagementClass("win32_processor");
        ManagementObjectCollection moc = mc.GetInstances();

        foreach (ManagementObject mo in moc)
        {
            if (cpuInfo == "")
            {
                //Get only the first CPU's ID
                cpuInfo = mo.Properties["processorID"].Value.ToString();
                break;
            }
        }
        ManagementObject dsk = new ManagementObject(@"win32_logicaldisk.deviceid=""" + "C" + @":""");
        dsk.Get();
        string volumeSerial = dsk["VolumeSerialNumber"].ToString();

        string HardWareUniqueID = volumeSerial + cpuInfo;

        return HardWareUniqueID;
    }

Appreciate your answers,
Thanks in advance

Answer 1

You hae a few choices…

1. Lock your web site to the single IP address you install it on. To make your life easier, check for that IP in a common page base class. (Note, you could also write HTTP handlers, but the base-class approach is easier.)

2. Put a ‘phone home’ call in the app that checks with your server every time it’s started up. That way you can check if they have moved it or if multiple instances are running.

3. Use the built-in licensing features of .NET (the same one third-party developers use for controls, etc.)

4. The easiest… just put in a time-bomb that lets them test it for a few weeks, then automatically blocks access. Be smart though… persist the last-checked time so you can tell if they’ve rolled back their clock trying to get more usage.

Just make sure to distribute a web application, not a web project so you can distribute your code as a compiled bumary rather than having to ship the code-behind files. That will keep prying eyes out, but does make deployment more a pain since you always have to recompile with every change (as opposed to on-demand compiling.)