Edit - Stack Overflow

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.

Rev

4

This rule makes sense to me. But consider the following situation: Native.dll (x64) used by NetA.dll (Any CPU) used by NetB.dll (Any CPU) used by App1.exe (x64). There is no real problem here, but compiling NetA.dll gives me the warning. OK, since this assembly directly depends on Native.dll, I could mark it as x64 also. But then compiling NetB.dll complains. I want to keep NetB.dll as "Any CPU" because it is a common assembly used in a different, pure-dot-net application. I conclude that my only option is to suppress/ignore the warning. Yes?

Steve Robbins
– Steve Robbins

2015-06-29 19:00:03 +00:00
Commented Jun 29, 2015 at 19:00
2

Because of the dependency on Native.dll, your entire app/assembly lineage is now x64, whether your suppress the warning or not. While suppression works in your scenario, weird situations could arise in the future. For example, 1) assembly NetB is used in an x86 environment, where Nativex64 will not load, or 2) your customer wants an x86 version of App1.exe, and you compile happily, since NetB is marked as any CPU, but again, Nativex64 at the top of the stack will not load

Gustavo Mori
– Gustavo Mori

2015-08-20 22:30:46 +00:00
Commented Aug 20, 2015 at 22:30
While Gustavo's rule is a good principle, it cannot be used for the specific problem asked in this question as the project already has a dependency on a 3rd party assembly that didn't follow the rule (it's x86, not AnyCPU). Hence as long as the dependency is there the whole chain of projects must target x86 and nothing else.

David Burg
– David Burg

2018-12-07 00:48:08 +00:00
Commented Dec 7, 2018 at 0:48

Add a comment |

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

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>

formatting help »
answering help »

Collectives™ on Stack Overflow