vb.net - Installer with Online Registration for Windows Application -

vb.net - Installer with Online Registration for Windows Application -

we have developed software in vb.net using visual studio 2013. want build custom installer next steps/features:

user start install our software. at 'enter serial key' option, user enters 16 digit serial have provided. when clicking 'ok' button, our software connect our ip , save serial key other user's info our database. a confirmation key returned our software. software writes file , save scheme folder.

it adobe or corel registration process. open other techniques must secure our software must install on single machine only. please noted grouping of novice programmers(not advance level), so; if process elaborated, helpful us.

i remove licensing features setup , add together them application. setup can still write license disk or registry passing msiexec.exe public property (uppercase properties):

class="lang-dos prettyprint-override">msiexec.exe /i "c:\install.msi" /qn /l*v "c:\msilog.log" license="123-456-789" this allow license added each machine in corporate deployment scenario. license value written disk or registry without validation. application verify (more secure validation dll in setup). there no need mess complex setup dialogs, need license dialog in application explained below. almost big corporations deploy msi files silently, setup gui ignored of time anyway. simply adding risk , wasting resources if deal licenses in setup.

there several more concrete reasons maintain license handling , validation out of setup:

a important number of back upwards requests result people have problems registering license keys in setup. a setup run once, application can started 1 time again if there problems. more of import might think inexperienced users. have improve features available handle exceptions , error conditions , whatever unexpected problems may occur in application. serial validation in setup exposes validation dll / method cracked pirates. won't prevent piracy eliminating setup, @ to the lowest degree create more difficult. more secure in application if cloak things bit (static linking, encryption, obfuscation, putting validation process online, , / or whatever done security professionals unfamiliar with). if setup needs back upwards trial version of application, should allow user come in license key if end buying product - preferably without having re-run setup or uninstall / reinstall add together license key. in other words need deal licensing in application anyway, why complicate setup too? if application runs different editions, if user buys upgraded license? should able come in license dialog , unlock features if possible , not uninstall , reinstall clunk involves. upgrades hard accomplish though, , end separate setups different editions. if network using proxy server net access, have problems registering license on net during setup (often asked marketing). have more features check , deal in application - can seek 1 time again , wait access (generally hook ie automagic proxy configuration if possible). corporate deployment need silent install alternative doesn't validate key writes registry. an application run non-admin user can not write hklm share serial between users on computer. must either write hkcu or setup must have prepared write access specific hklm location in registry application write to. prefer writing hkcu each user since license less available copying others, , kept user specific info (allows roaming, though hated feature professionals). however, hklm license key written application or setup during installation (as explained above public property set) allows users share license when launching application. setups mess licensing may cause license info deleted during upgrades, patching , migration scenarios due bugs in setup. lot more serious @ times think - bundle might nail thousands of workstations in big companies , cumbersome fix. licensing huge corporate headache - desired company or corporation licensing centrally managed on server, , not based on text serial numbers @ (for illustration concurrent or floating licenses acquired on application launch via network). mentioning though sort of out of scope question. in these cases specify during installation ip address pointing license server, or regular host name resolved wins or dns.

vb.net visual-studio-2013 installer windows-installer