You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
1The only other official MS reference to this solution that I've seen is in the Microsoft .NET Framework 4.5 RC Readme file. Strangely it was removed from the RTM Readme file.JohnC– JohnC2013-07-10 15:51:53 +00:00Commented Jul 10, 2013 at 15:51
-
-
4This works, but not for a variation of the warning: "Referenced assembly ... targets a different processor than the application". It would be great if there was a similar setting for this warning?Jimmy– Jimmy2014-02-20 16:38:09 +00:00Commented Feb 20, 2014 at 16:38
-
10"my projects platform is AnyCPU and I'm referencing an MS library built for AMD64"... This is WRONG. Since your target deployment is always 64-bit, you can set your platform to x64, which makes for a more appropriate error if your 64-bit assumption ever gets violated, and also prevents the warning.Ben Voigt– Ben Voigt2015-05-21 16:34:50 +00:00Commented May 21, 2015 at 16:34
-
3@BenVoigt a great idea in theory, but VS being a x86 process needs x86 builds of controls to run stuff like the Windows Forms Designer, even if your application will only ever be 64 bit. It's a valid, but unfortunate reason to use a false "Any CPU" build.jrh– jrh2018-02-19 19:49:42 +00:00Commented Feb 19, 2018 at 19:49
-
1@jrh: Then put the GUI in a DLL project, and build that as AnyCPU. The EXE needs to be marked with the right architecture to match the native dependencies. Proper separation of GUI from logic goes a long way (although it does still have its limits, such as when the native code is rendering part of the GUI, but then designer support is a lost cause unless you do builds of the entire project for both x86 and x64)Ben Voigt– Ben Voigt2018-02-19 21:56:05 +00:00Commented Feb 19, 2018 at 21:56
|
Show 4 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. python-3.x), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you
default