licence.licx files are preventing builds

Our developers all have Infragistics licences.

However, our build computer does not (no development takes place on it).

Today, our part of the product prevented a global build from completing successfully.

By trial and error, we discovered that it was caused by the licence.licx files. We found that if they are all EMPTY on the build computer, it builds successfully. We then learned that one of our developers had checked in one of his licence.licx files which contained token keys (written automatically, it seems).

My question is: What is the correct way to handle these licence.licx files on a build computer without an Infragistics licence?

So far, ensuring they exist but remain empty works for us, but an internet search turned up a mix of suggestions, including setting the Build Action in VS’s (2010 in our case) File Properties to “None”. We have it set to “Embedded Resource”, which seems to be the default.

What is right?

We had the same problem. Our solution was to check in an empty license file and then make sure that we don't overwrite it or if we do then we revert to the original inside our version control system (TFS).

Hi guys,

I confirm to you that if you let the license file empty it will works => you can build.

But if you "touch" any control via the GUI Editor the license engine of IG fill the file with some information about the control used in the "touched" from. That permit to IG DLLs to check license when build code.
The solution, and Ghram confirm that, is to let the license file empty, or without lines related to IG.

Obviously, by the law, you need the right number of licenses based on IG license terms.
Sincerely,

The Building Apps Using NetAdvantage with Team Build blog post covers using a separate server for building.  Davide is also correct that having an empty licenses.licx file will allow you to build and that you still do need to have a license to be in compliance with the license agreement.

I know this is a very old thread.  But the link to the blog provided no longer works and I'm experiencing the same issue.  I prefer not to create a blank license file.

I've tried using a vNext Pre-Build Event to copy a blank licences.licx file, but that does not seem to be working.  Is there a more graceful solution?

An archive of the old blog post can be accessed here: https://web.archive.org/web/20160729120944/http://ko.infragistics.com/community/blogs/ed_blankenship/archive/2007/07/16/building-apps-using-netadvantage-with-team-build.aspx

I have included a copy of the text here for posterity.

This post actually applies to many different situations in which you would automate a build on a separate server.  I just happen to be familiar with Team Build. 🙂

Because of how NetAdvantage deals with licensing each build server will need a full copy of NetAdvantage installed.  Some customers have only copied the NetAdvantage assemblies over to their build server and will see LicenseException errors in their build reports.  Even copying them into the GAC isn't enough…  Just to save yourself a couple of headaches, take a few minutes to install using the product installer.  There is an option in the installer to install just the assemblies and licensing components.  I'd recommend deselecting all of the options if you don't need them installed on the build server.  Be sure to also apply any hot fixes that your application may use as well.

As an aside, according to our current licensing agreement, each build server you install NetAdvantage on must have a separate license whoever creates the build script must be licensed.  If your team has separate build engineers, each of them should be licensed if they will be working on the build script.

 

Happy Building!