Home Dashboard Directory Help
Search

MSB3270 bogus warning with C++/Mixed project by Sacks


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


10
0
Sign in
to vote
Type: Bug
ID: 728901
Opened: 3/5/2012 12:26:24 PM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
view
7
User(s) can reproduce this bug

Description

A C++/Mixed project generates the following warning when compiled with a reference to a .NET assemply or project that is set to x86.

warning MSB3270: There was a mismatch between the processor architecture of the project being built

However, the project is a Win32 (i.e. x86) project. So there is no mismatch.

There does not seem to be any easy way to make the compiler happy and get rid of the warning.
Details
Sign in to post a comment.
Posted by vxsery on 6/7/2012 at 10:29 PM
Addendum: Building the same solution in VS 2012 does not produce the warning.
Posted by vxsery on 6/7/2012 at 10:22 PM
I can reproduce this in VS2010. I also have VS 2012 RC installed.

Steps to reproduce in VS2010:

1. Create a new C++ CLR Class library.
2. Create a new C++ Test project.
3. Add a reference to the original project in the test project.
4. Build the solution.

...
5. ???
6. Profit!

Even though the C++ CLR project is compiling with /clr and producing a mixed assembly, the Targets are considering it a pure MSIL object.
Posted by vemundha on 3/30/2012 at 10:40 AM
Same problem after installing VS11 beta. Building with .net4 and mixed-mode c++ x64 project. And I checked the c++ project file it's reported a warning on and can't see anything wrong in that .vcxproj file. Both are using .net4.
Posted by ulku on 3/22/2012 at 5:45 AM
Same issue... VS2010 Ultimate, C# .net 4 and mixed-mode C++ x86 projects. I am receiving these warnings (in VS2010, no changes in project files) since I have installed VS11 beta on the same machine.
Posted by Microsoft on 3/22/2012 at 1:39 AM
Thank you for submitting feedback on Visual Studio and the .NET Framework. At this point, it has been more than two weeks since we initially requested additional information to reproduce your issue. Since we have not heard back from you we will close the issue. If you need further assistance on this or any other pre-release product issues in the future, please feel free to contact us and we will be happy to help.
Posted by Microsoft on 3/13/2012 at 2:54 AM
Hello,

Sorry for bothering. Is there any update?

It would be greatly appreciated if you could provide us with that information as quickly as possible. If we do not hear back from you within 7 days, we will close this issue.

Thanks again for your efforts and we look forward to hearing from you.
Posted by MS-Moderator08 [Feedback Moderator] on 3/6/2012 at 12:52 AM
Thank you for reporting this issue. But we were not able to reproduce it with the steps you proivded. Could you please attach a sample project to help us reproduce this issue?
Posted by MS-Moderator01 on 3/5/2012 at 7:13 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)
Sign in to post a workaround.