Neither. The purpose of setting license by code is so that code is compiled and the license code is not obvious to any third party that may be able to view your page files. If you were to set in asax, it would be practically no different than including the license file directly.

If you are only redistributing your application without your organization, or to a controlled environment (for example, only to your hosting servers), then you can just use the license file. It's much easier. If you do need to release your product to the public, you should take reasonable precautions to prevent our license being reused by any third party and setting license by code is only the first step of that. In addition to that, most vendors would also obfuscate their binary code. Basically you need to do what you do to guard license code for your own product.

You can never include any code in web.config.

Hi Loren,

Nobody is saying that you can not put license code in ASAX file. We are saying that if you are going to let everybody in the world to see your ASAX file, you'd better take any sensitive information off that file. The same goes for connection string in web.config. Would you put your connection string in web.config if everybody can get their hand on your web.config? Unless the database is theirs, not yours.

So if nobody expect for your own people will see your ASAX file, feel free to put the code in your ASAX file. You can also try to put the license file on your root directory, instead of your bin directory so that Visual Studio won't touch it. You can certainly build a .DLL with LICX file but then you will have to worry about how and when to load it, which is a totally separate chapter.

Thanks