Best way is to sign your registration assembly with public key (strong name) You can make a client utility to send you via email the client's machine information and then generate a strong name assembly back to the client.
the software MUST check if the client has the assembly given and verify its machine info against the user machine to make sure they fit. this way you lock your software to one machine, but it is all depends on what you put in the assembly and in the registration options Best Regards, Ido Samuelson IBM Global Services (Israel) Tel: 972-3-5313765, Mobile: 972-67-888150. Fax: 972-3-5313500, E-mail : [EMAIL PROTECTED] Only 10 kind of people understand me. Those who are and those who aren't. "Mark A. Gregory" <[EMAIL PROTECTED]> Sent by: "Moderated discussion of advanced .NET topics." <[EMAIL PROTECTED]> 19/04/2004 09:34 AM Please respond to "Moderated discussion of advanced .NET topics." To [EMAIL PROTECTED] cc Subject [ADVANCED-DOTNET] Application registration I have nearly finished a new application and we want to protect our investment. What is the best way to implement product registration? Is there an example around? I have read that some people are using the HD Volume number as a key to ensure each installation is unique. Is this a good idea? We want registration to be such that the software generates a key (unknown to the user) and together with the serial number entered is used by our server to provide a license key. I would appreciate pointers on a satisfactory solution. Thank you Mark =================================== This list is hosted by DevelopMentor® http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
