This forum contains outdated content and is available for reading only. Please contact technical support if you have any questions.

Notification

Icon
Error

Options
Go to last post Go to first unread
ChingYen  
#1 Posted : Wednesday, January 13, 2010 3:56:26 AM(UTC)
ChingYen

Rank: Advanced Member

Groups: Guest
Joined: 3/3/2008(UTC)
Posts: 185

Thanks: 8 times
Hi,

We were trying to migrate our 32-bit application to 64-bit application.
We are facing problem to compile our 64bit application when we have a "license.licx" with "Aurigma.GraphicsMill.Bitmap,Aurigma.GraphicsMill" inside the license file. It will give error of "'Could not load file or assembly 'file:///C:\Program Files\Aurigma\Graphics Mill 5.5 for .NET\Binaries_64\Aurigma.GraphicsMill.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.'

Everything will compile without problem if we were to compile the application without the license.licx.

But, if we do not do that, end user will not be able to run our application as it will be stated Aurigma Trial version exp.

Please advice.
HenricusMagnus  
#2 Posted : Wednesday, January 13, 2010 4:34:33 PM(UTC)
HenricusMagnus

Rank: Member

Groups: Guest
Joined: 10/21/2008(UTC)
Posts: 14

Was thanked: 1 time(s) in 1 post(s)
Hi Forum,

some days ago, I had the same problem and posted it as a support case.
I got a very fast answer by Tamila Ashrafova, and I hope I'm allowed to post it here:

'***********************************************

I tried to investigate this problem and found that it is a bug in Visual Studio 2008 when it comes to building a 64-bit application on a 64-bit system. VS 2008 will use the 32-bit version of license compiler (LC.exe) when the build configuration is set to x64.

To workaround this issue you will need to modify your application project file in a text editor. Add the highlighted line shown below to all of your 64-bit build configurations:

<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|x64' ">
<DebugSymbols>true</DebugSymbols>
<OutputPath>bin\x64\Debug\</OutputPath>
<DefineConstants>DEBUG;TRACE</DefineConstants>
<DebugType>full</DebugType>
<PlatformTarget>x64</PlatformTarget>
<CodeAnalysisUseTypeNameInSuppression>true</CodeAnalysisUseTypeNameInSuppression>
<CodeAnalysisModuleSuppressionsFile>GlobalSuppressions.cs</CodeAnalysisModuleSuppressionsFile>
<ErrorReport>prompt</ErrorReport>
<LCToolPath>C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\x64</LCToolPath>
</PropertyGroup>
<PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|x64' ">
<OutputPath>bin\x64\Release\</OutputPath>
<DefineConstants>TRACE</DefineConstants>
<Optimize>true</Optimize>
<DebugType>pdbonly</DebugType>
<PlatformTarget>x64</PlatformTarget>
<CodeAnalysisUseTypeNameInSuppression>true</CodeAnalysisUseTypeNameInSuppression>
<CodeAnalysisModuleSuppressionsFile>GlobalSuppressions.cs</CodeAnalysisModuleSuppressionsFile>
<ErrorReport>prompt</ErrorReport>
<LCToolPath>C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\x64</LCToolPath>
</PropertyGroup>

'***********************************************

N.B.: Maybe you will have to replace the path to c:\Program Files by the appropriate naming for your local OS.
In Germany, it spells: c:\Programme ....

Adding these lines solved my problem, and I really highly appreciate that Aurigma is doing Microsoft's job...

Best regards
Heinz-Jürgen
Tamila  
#3 Posted : Thursday, January 14, 2010 3:43:33 AM(UTC)
Tamila

Rank: Advanced Member

Groups: Guest
Joined: 3/9/2008(UTC)
Posts: 554

Was thanked: 1 time(s) in 1 post(s)
Aurigma Support Team

UserPostedImage Follow Aurigma on Twitter!
Users browsing this topic
Guest (3)
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.