Automating Build Process with Wizard

Wizard for Windows Forms Forum

Posted 20 years ago by sgoertzen
I recently purchased the Wizard component, and incorporated it into my program. When I build and run my program through visual studio, the license file is picked up correctly and the warning dialog is not displayed.

However, the final software builds are not done through Visual Studio, but instead using a .Net build automation tool called NAnt (<A HREF="" TARGET=_blank></A> if you are interested). This tools saves a tremendous amount of time as we can just start the build and come back in 10 minutes and have a single executable to install.

My issue however, is that when the project is being built with NAnt, it doesn't appear to be picking up the license file at all. It displays the warning dialog when it is building everything, then again every time you run the program.

Does anyone know more details on where the LIC file must be at for it to be properly picked up? I'm sure automatic build tools must be fairly common out there, has anyone else run into this problem?

And just in case someone here is familiar with NAnt, here is my config line that builds the project:

commandline=" Get $/Directory/Viewpoint.root -R -I-"
&lt;solution solutionfile="Source\Viewpoint\Viewpoint.sln" configuration="debug"&gt;

Only thing special to note is that all the files are retreived from Source Safe before building. Do I need the LIC file in Source Safe to it gets pulled out too? (it is already in program files with the .dll)

Thanks in advance for any help!

Comments (3)

Posted 20 years ago by sgoertzen
I did just figure out that I can keep the register warning box from poping up by including the LIC file in the build. But as the documentation says not to do this in BIG BOLD LETTERS, I figured I better keep looking for a better way. <IMG SRC="wink.gif" border="0">

I'll keep trying stuff, but any help would be greatly appreciated.
Posted 20 years ago by Actipro Software Support - Cleveland, OH, USA
Hi Shawn,

Including the LIC file with your build is completely illegal so don't do that. <IMG SRC="smile.gif" border="0">

We are eventually going to be upgrading Wizard to use the licensing scheme that SyntaxEditor uses, which is registry-based and much better. That will eliminate problems like this that arise with Microsoft's LIC file scheme.

I assume you placed the LIC file in the Program Files folder where the control was installed? Another thing you might try is placing the LIC file in the GAC folder that contains the assembly. You have to do that via command line though since Windows Explorer doesn't let you into those folders. Let me know if that helps.

Actipro Software Support

Posted 20 years ago by sgoertzen
It looks like moving the LIC file into the GAC worked!

I never even heard of the GAC before, so I didn't even think of doing that. I had searched for all copies of the dll on my machine and stuck the LIC file with each one, but since Find doesn't search the GAC, I never caught the dll in there.

Thanks for your help!! Looking forward to the registry license version, as this LIC method does seem less then perfect. <IMG SRC="wink.gif" border="0">

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

Add Comment

Please log in to a validated account to post comments.