Compile Error - Processing complist 'Properties\licenses.licx'

[John]

I am posting here because the error is 'Telerik.Web.UI.GridFilterMenu' not found.


2> Processing complist 'Properties\licenses.licx'...
12>C:\Projects\CenterRail\Properties\licenses.licx(3): error LC0004: Exception occurred creating type 'Telerik.Web.UI.GridFilterMenu, Telerik.Web.UI, Version=2015.1.225.45, Culture=neutral, PublicKeyToken=121fae78165ba3d4' System.MissingMethodException: Constructor on type 'Telerik.Web.UI.GridFilterMenu' not found.
12> at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark)
12> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
12> at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture)
12> at System.SecurityUtils.SecureCreateInstance(Type type, Object[] args, Boolean allowNonPublic)
12> at System.ComponentModel.LicenseManager.CreateWithContext(Type type, LicenseContext creationContext, Object[] args)
12> at System.ComponentModel.LicenseManager.CreateWithContext(Type type, LicenseContext creationContext)
12> at System.Tools.LicenseCompiler.Main(String[] args)
12> The command exited with code -1.
12>Done executing task "LC" -- FAILED.

[Dimitar]

Hi,

Since Q1 2015, the Telerik UI for ASP.NET AJAX suite uses the standard .NET licensing mechanism, which means that using the controls in design-time causes Visual Studio to add a license.licx to the solution. In case your project build fails with errors pointing to the license file, you can delete it and rebuild. This should help you fix the issue.

More information about the license file is available here:
http://www.telerik.com/help/aspnet-ajax/introduction-license-file.html

Regards,
Dimitar
Telerik

 

 

[John]

Thank you! Out of desperation I deleted that file shortly after I posted, it seemed to work. Having your confirmation takes the worry out of my actions. I was afraid I would not be able to publish.

[Lenny_shp]

After I delete licenses.licx  2005 Q1 would work, but after I change the code and debug run, VS2013 update 4 would complain again and I have to delete licenses.licx multiple times an hour.   .NET 4.51

[Dimitar]

Hi,

We have implemented a fix to the licensing mechanism, which would be included in the Q1 2015 SP1 release, expected till the end of the week. It is expected to solve the issue faced. Please test it, when released and get back to us, if the issue persists.

Regards,
Dimitar
Telerik

 

 

[Tom]

We have this problem after updating from Q1 2015 to Q2 2015. After that update we get the license.licx. We remove the Q2 2015 so we can proceed as normal. we didn't installed Q1 2015 SP1, because of this license.licx. 

We decided to wait, if that problem is solved. Work with source control and this license.licx  is not possible.

When we can expect a solution of this problem?

We use VisualStudio 2013.

[Dimitar]

Hi,

I would like to clarify that the issue fixed is not the presence of a license.licx file, but the error when building your project, which is discussed in the beginning of this thread.

Since Q1 2015, the license file is expected to be generated, when using Telerik UI for ASP.NET AJAX. And as stated in the License File help article "If you are working under source control, once the file is created, it will be detected as a change by your source control system. We would suggest that you check-in this file initially. Then, when it is checked-out again during your work, it is up to you to decide whether to check it in, or discard the changes."

Could you clarify if you are concerned about the presence of the license.licx file or there are errors when building your project with Q2 2015?

Regards,
Dimitar
Telerik

[Tom]

Thanks for replay, 

OK that is maybe not the right post here, because we don't get errors because we roll back our version to Q1 2015. 

Sorry for that. Should I open a new thread?

We saw that license.lixc as we installed the Q2 2015 Version and that behavior we had never seen before. It disturbs our work extremely. Check in Check out ... and as we only look a at layout of our reports it will be checked out the report again and creates a license.lixc file again...  so again, deleting, checkin... this is useless work...

We decide to rollback to Q1 2015 and wait for a solution.

Thanks for License File help article, but that do not help us...

Sorry for my bad English

Regards
Falk Hebstreit

[Pavlina]

Hi,

As my colleague Dimitar mentioned and as stated in the help article, we are using the default licensing mechanism of .NET and there is no setting in VS that can stop the license file to be created automatically when you are using Telerik UI controls in Design time.

What you can try is to:

• delete the contents of the license.licx
• check in the file
• make the source control ignore the license file so any changes on a developer machine won't make it into the build machine or anywhere elsewhere.

Other already suggested options are to check-in the licx file in your source control and leave it as-is in the future, each local VS instance will modify them as needed. Otherwise, you can delete them if you like, but lc.exe will generate the license dll when you prepare your app for deployment. This is simply how the .NET licensing mechanism works.


Best regards, Pavlina
Telerik

[Charlie]

Hi I updated my telerik yesterday but had issues with my license.licx file I read at the below link that if you have any issues with the license file to just delete and rebuild the project so I tried that I deleted the license file and clicked rebuild only to get an error everywhere in my code where telerik is used so it wont recreate the license file and I can no longer debug the project or run the project.

 http://docs.telerik.com/devtools/aspnet-ajax/licensing/license-file 

 How do I solve this and what is the correct process for upgrading telerik as it always seems to cause issues in all of our projects we use it in when we update it.

[Pavlina]

Hello,

I would recommend you follow the instructions for upgrade to newer version provided in the article below and let us know if you still encounter any problems:
http://docs.telerik.com/devtools/aspnet-ajax/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version#upgrade-to-a-newer-version-of-telerik-ui-for-aspnet-ajax

Regards,
Pavlina
Telerik

[Salim]

Hi,

Where can I find the file Licence.lcx ?

[Pavlina]

Hello Salim,

The license.licx file will be added to the solution automatically by Visual Studio once you use the UI for ASP.NET AJAX controls in design-time. More information on the matter is available here:
http://docs.telerik.com/devtools/aspnet-ajax/licensing/license-file

Regards,
Pavlina
Telerik

[anand]

I'm using Telerik 2017.3.913.40 and I'm still having the issue. So painful to delete it every time. Do you have any TAT on when this will be fixed?

 

Thanks,

Anand

[Rumen]

Hi Anand,

This is how the Microsoft licensing mechanism works and I am afraid that there aren't any new available options for its improvement.

The available options are still the same:

• Delete the contents of the license.licx
• Or delete the whole license.licx file
• Or check in the file
• Or make the source control to ignore the license file so any changes on a developer machine won't make it into the build machine or anywhere elsewhere.

Best regards,
Rumen
Progress Telerik

[Tom]

To all suffering from this error, this solution worked for me. Right-click the .dll file and click the 'Unblock' button on the General tab near the bottom. The button goes away after it is unblocked (in case you don't see it). Found the solution here: http://www.chilkatforum.com/questions/8260/could-not-load-assembly-operation-not-supported-exception-from-hresult-0x80131515

Hope it helps.

[Tom]

Correction to instructions: Right-click the .dll file, select properties, and then click the 'Unblock' button on the General
tab near the bottom