Not logged in▾
Log In Register
Forgot Password Resend Validation E-mail

Pop up wont go away -- need help

Wizard for Windows Forms Forum

Posted 19 years ago by Avinash
Avatar
Hi,

Cant seem to get rid of the "Purchase" popup on the wizard control we use. We are using version 2.0.80.0 and have copied the ActiproSoftware.Wizard.Wizard.LIC file to C:\Program Files\Actipro Software\Wizard\v2.00.0080 folder.

I am building in release mode and have looked at the licensing faq. The weird bit is that on some machines where there really is only one version of the control installed and is full release and has never had an older version of the control installed on it, it still throws up the purchase pop up.

Have tried this on several machines and no luck except for one of them. But thats not our build machine and so need this working on the build machine.

Cant think of why this may be. Spent way too much time on this. Am I missing something ?Any help/suggestions/ideas will be great.

Regards,
Avinash
aphaniraj@e5systems.com

Comments (11)

Posted 19 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Does our sample project compile without a popup?

Also on your build machine, what do you use for building it, like NAnt, etc.?

Actipro Software Support

Posted 19 years ago by Avinash
Avatar
Thanks for your response.
Yes your sample app seems to build without the pop up.

Also noticed that adding 'C:\Program Files\Actipro Software\Wizard\v2.00.0080' to Common Properties - Reference Path (as suggested in the faq) and setting that as the first item in the list seems to help too.

But this info in not being saved into the project file and so will probably have similar problems on the build machine. becuase the build engine gets the latest files automatically and does the buidl.

We use a custom build tool not much different from any other tools I suppose.

thoughts on how I should proceed ??

Regards,
Avinash
Posted 19 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
The problem probably is that your build tool is not compiling the license data into your application. I've seen that a lot with other customers who are setting up their build process for the first time using a licensed control.

You need to make sure that at some point, your build process executes lc.exe (Microsoft's license compiler app) using the licenses.licx file (make sure you have a proper entry for Wizard in there with the correct version). If you do that, it should work fine. You may have to look up some documentation on how to use that program but there is help in the MSDN.

Actipro Software Support

Posted 19 years ago by Avinash
Avatar
We dint have these problems when we were on the older .77 version. In fact all was ok then. Im not sure if there has been any change on the build machine itself. Will check.

However, we really are seeing problems even while building with VS.Net too.
What exactly does Reference Path - Common Properties setting do ? Ive tried to read up on MSDN. What puzzles me is where VS.Net stores this info. Also an even more odd thing is that this only works if the path is the first in a list. Does not work when its not the first item.

Since you have mentioned about this in the faq I thought you will know why or how this helps and so If I can save this in the project file or something of that sort, my build process will probably go throug fine.

Thanks & Regards,
Avinash
Posted 19 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
From what you're saying, it almost sounds like you didn't update the entry in your project's licenses.licx file to have the newer build number. Are you sure the entry in there says build 80 and not 77? Whenever you upgrade you have to update that.

The references path really shouldn't matter too much if you have the control installed in the GAC.

Actipro Software Support

Posted 19 years ago by Avinash
Avatar
Many many thanks for all the help. I think I've zeroed in on my problem and will share my findings with you.

Essentially because of some decisions we made, we set the copy local to true on the reference to the wizard component. What happens is that for the first time when the bin folder is empty VS.Net uses the license file in C:\Program Files\Actipro Software\Wizard\v2.00.0080 and then copies the dll into the local bin folder. On subsequent build attempts, and if the bin folder contains the wizard dll, it seems to pick up the dll from bin and not GAC and hence wont find the license file.

I need to figure out how this may be resolved.

Thanks for your time.
Best wishes,
Avinash
Posted 19 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
It should still work even if you have Copy Local on. But let's try something else anyhow. Open the Command Prompt and navigate to the Windows/Assembly folder then go to the subfolder where the Wizard assembly is installed in the GAC. You can only see this in the Command Prompt. Then copy the LIC file to that folder. See if that helps.

This all is one reason for our newer product releases (including Wizard 3.0), we now use registry based licensing mechanisms which eliminate the problems of locating LIC files.

Actipro Software Support

Posted 19 years ago by Avinash
Avatar
Tried copying the .LIC file into the version specific product folder within GAC. Does not seem to help.

Regards,
Avinash
Posted 19 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Here's one other thing you can try... we made a backdoor way in 2.0 to let you use the registry for the key.

Use regedit and create this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Actipro Software\Wizard\Licensing

Then add a string value named:
LicenseKey

Take the first line of your LIC file, and set it to the value of LicenseKey.

Then do a rebuild solution and see if that helps.

Actipro Software Support

Posted 19 years ago by Avinash
Avatar
The first line of the lic file we have out here reads -->
Wizard (licensed to E5 Systems): SOME-NUMBER-HERE.

I tried creating the key like you mentioned and added the whole line above. That din't work. I tried setting the LicenseKey value to only the number bit. That din't help either.

Regards,
Avinash
Posted 19 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar
Can you send me an email and I can continue helping you there? It's easier than going back and forth in the forums. <IMG SRC="smile.gif" border="0">

Actipro Software Support

The latest build of this product (v24.1.0) was released 2 months ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.