Submit My Question - Recent Questions - Recent Answer
Msdn Tech >> .NET Development >> 64-Bit .NET Framework Development.

Itanium compiler error

I am porting a C# project to 64 bit. I successfully compiled in Whidbey using AnyCpu setting and ran the test client. However, after I changed the compiler setting to Itanium and copied settings from AnyCpu, I got this error upon compiling:

-

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(1500,9): error MSB3551: Unable to load referenced assembly "C:\Projects\...\bin\Itanium\Debug\MyClass.dll". Could not load file or assembly 'C:\Projects\...\bin\Itanium\Debug\MyClass.dll' or one of its dependencies. The system cannot find the file specified.

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50215\Microsoft.Common.targets(1500,9): error MSB3551: Parameter name: C:\Projects\...\bin\Itanium\Debug\MyClass.dll
--

Can anyone tell me how to resolve this?
Thanks much.

[1584 byte] By [JenniferGamble] at [2008-2-15]
«« VBA problem for Word 2003
»» Can't publish using August CTP
# 1
Upon further inspection, I see that a similar problem has been posted on MSBuild forum and submitted as an issue. Does anyone know for sure if this is a compiler bug? What is the status of this issue?
JenniferGamble at 2007-9-9 > top of Msdn Tech,.NET Development,64-Bit .NET Framework Development....
# 2
Jennifer:

Can you send a simple repro for this behavior?

Doing the following steps produced a valid assembly targeting Itanium:
New Project -> C# ...
Build -> Configuration Manager
In "Active solution manager" select "<new"
Select "Itanium" in "Type or select new platform"
Set "Copy settings from" to "Any CPU"
Check "create new project platforms"
OK
Build -> Rebuild Solution

Thanks

Jeff

JeffSchwartzmsft at 2007-9-9 > top of Msdn Tech,.NET Development,64-Bit .NET Framework Development....
# 3
I believe those errors must be related to this warning:
warning CS1699: Use command line option '/keyfile' or appropriate project settings instead of 'AssemblyKeyFile'

After I fixed all the /keyfile signings under project settings, the targeting errors went away. Does this make sense? I will mark this as resolved since this seemed to fix the problem.

JenniferGamble at 2007-9-9 > top of Msdn Tech,.NET Development,64-Bit .NET Framework Development....
# 4

That is likely if the original error was due to an invalid PE signature. We depricated the AssemblyKeyFile for various reasons. One being that the coder was really not in control of where we picked up the key file from.

Glad to hear that this resolved the issue.

Jeff

JeffSchwartzmsft at 2007-9-9 > top of Msdn Tech,.NET Development,64-Bit .NET Framework Development....
.NET Development
64-Bit .NET Framework Development.

.NET Development Hot Topic

.NET Development New Topic

.NET Development

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech

Site Classified