Welcome Guest! You need to login or register to make posts.

Notification

Icon
Error

Options
Go to last post Go to first unread
Dmitry.Obukhov  
#1 Posted : Tuesday, November 9, 2010 2:45:08 AM(UTC)
Dmitry.Obukhov

Rank: Advanced Member

Groups: Administration
Joined: 5/29/2010(UTC)
Posts: 1,310

Thanks: 8 times
Was thanked: 111 time(s) in 111 post(s)
Description

According to the Graphics Mill documentation, you can embed full license key into the resources using License.licx file. However, if you use .NET 4.0 as a target framework, you will get the error:

LC : error LC0000: 'Could not load file or assembly 'Aurigma.GraphicsMill' or one of its dependencies. Could not find or load a specific file. (Exception from HRESULT: 0x80131621)'

0x80131621 means: "Mixed mode assembly is built against version '2.x.x' of the runtime and cannot be loaded in the 4.x.x. runtime without additional configuration information."

Resolution

To fix the issue you should change license compiler configuration. Please create lc.exe.config in the same folder, as lc.exe (typically, "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\NETFX 4.0 Tools\" folder), and fill it with following text:
Code:
<?xml version="1.0"?>
<configuration>
  <startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0"/>
  </startup>
</configuration>

Edited by user Tuesday, May 29, 2012 2:07:36 AM(UTC)  | Reason: Not specified

Best regards,
Dmitry Obukhov
Technical Support. Aurigma, Inc.
AndyF  
#2 Posted : Thursday, September 22, 2011 3:33:15 AM(UTC)
AndyF

Rank: Newbie

Groups: Member
Joined: 9/20/2011(UTC)
Posts: 1

Instead of changing the configuration file for lc.exe and have it affect ALL applications on your system, you can put this in your app.config:

Code:

<startup useLegacyV2RuntimeActivationPolicy="true">
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
</startup>


Your app.config likely already has a <startup> block, so you'll just want to modify it to look like the above.

EDIT: this only seems to work on the dev system... fails on deployment and you have to do the above to get it to deploy. This is a terrible answer, by the way.

Edited by user Saturday, September 24, 2011 1:02:55 PM(UTC)  | Reason: Not specified

Users browsing this topic
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.