Note that there are some explanatory texts on larger screens.

plurals
  1. POTargetting x64 platform with entity framework 4.1 in Visual Studio 2010
    primarykey
    data
    text
    <p>I have a database application that references Entity Framework 4.1. In the properties window of the project both the <strong>Configuration</strong> as well as <strong>Platform</strong> selection options are disabled. I wan't to target this application only for x64 systems.</p> <p>Also there are some other projects in the same Solution and they have only x86 option avaliable as platform.</p> <p>I don't get the idea why I couldn't target x64 systems specifically. I have windows 7 64 bit running on my pc.</p> <p>Any clues how to target specifically to x64 based systems. All projects reference .Net Framework 4.</p> <p>Screen shot of the project showing only "Any CPU" option</p> <p><img src="https://i.stack.imgur.com/e4DRK.png" alt="enter image description here"></p> <p><strong>Edit 1: Why I need to target x64 systems.</strong></p> <p>Actually, the dlls that I am developing will have to load in Autocad x64 systems. But when I am trying to load the dll into Autocad it is rejecting the dll with the following error </p> <pre><code>NETLOAD Cannot load assembly. Error details: System.BadImageFormatException: Could not load file or assembly 'file:///D:\RailwayProjects\RelayAnalysis_New\RelayAnalysis_Autocad\bin\Debug\Gl obalArea.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format. File name: 'file:///D:\RailwayProjects\RelayAnalysis_New\RelayAnalysis_Autocad\bin\Debug\Gl obalArea.dll' at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark&amp; stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark&amp; stackMark, Boolean forIntrospection, Boolean suppressSecurityChecks) at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark&amp; stackMark) at System.Reflection.Assembly.LoadFrom(String assemblyFile) at Autodesk.AutoCAD.Runtime.ExtensionLoader.Load(String fileName) at loadmgd() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. </code></pre> <p>I have a strong suspicion that Autocad x64 is rejecting the dll because it not in x64 format, although I may be wrong here. So now I expand the scope of my question to include AutoCAD, as the root of the problem is loading the dll in autocad. I have searched the web and found that AutoCAD is very picky about x32 and x64 types. The native developement environment <strong>AutoCAD.net</strong> for developing the Autocad plugins is also available separately under x32 and x64 types and I don't think that plugins developed with x32 will run in x64 type Autocad versions, and vice-versa. So, I need to be specific about the target platform for Autocad plugins</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload