Glen,
Thanks for the quick response. I did run it several times with
another setting. So that is triggering the 'no days left' option.
I'm still a bit confused. For instance if I create a new master
file with a 30 day trial and create a new assembly. I send this to my
customer and after the trial they want a registered version. So I go
into the licence manager not changing any settings and create a new
license with only the expiration date enabled. The expiration date is
5/4/2012. I also add a key that the program can use to select
options. Now does this new licence file need to be loaded everytime
the users program starts with License.Status.LoadLicense or is there a
different method?
One more question is there any way to run this in debug mode? I'm
using vs2010 with
vb.net.
Thanks for your help,
Bob
On May 4, 7:26 pm, Glen Harvy <
glenha...@gmail.com> wrote:
> Hi Bob,
> Whenever you run a protected assembly on your computer, .Net Reactor will record it's 'static' protection mechanism on your computer 'somewhere'. The location is naturally a closely guarded secret and may or may not be in the registry. I honestly don't know nor care. In future, there is nothing you can do to change the 'static' data recorded, nor amend it. I'm not even sure what data is in fact recorded.
> The only way you can create a new test of the same assemblyand change your protection setupis to change the Master Key. You can do that using the Licence Manager tab of your project. Unless you change the Master Key, .Net Reactor will use the original data to work out usage etc etc etc.