topic Re: Newbie -Warning message in Revit API Forum

Newbie -Warning message

Anonymous — Wed, 08 Apr 2015 17:16:53 GMT

Hi guys,

I am a newbie and going through various tools such as My first Plugin and other links.

When I add the Reference to the RevitAPI.dll and RevitAPIUI.dll in MS Visual Studio I get a Warning as follows:

Warning 1 There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "RevitAPI", "AMD64". This mismatch may cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a processor architecture that matches the targeted processor architecture of your project.

The Build still works but the plugin does not. The fist time I tried a plugin I didnt get this message and the plugin did work so not sure what I did to mess it up ?

thanks, any advice greatly appreciated.

Regards,

David

Re: Newbie -Warning message

arnostlobel — Wed, 08 Apr 2015 19:25:23 GMT

Hello David,

Do not worry about that particular warning. It's caused by a bug in VS. We do get that very warning too for all our internal add-ins and API regression tests; some thousand+ projects. Presumably, the bug has been fixed in VS2013 and VS2015.

Cheers

Arno?t L?bel
Autodesk, Revit R&D

Re: Newbie -Warning message

Anonymous — Wed, 08 Apr 2015 19:58:16 GMT

Thanks for your quick reply.

i can ignore it so, thats fine. i am uisng VS Comunity 2103.

this just means i must have done something else wrong so, since my plugin is not working.

Ths build is fine and i think my .Addin looks right so I am still stuck 🙂

I will have another look now that i know that is not the problem.

Thanks

David

Re: Newbie -Warning message

pteague — Wed, 08 Apr 2015 21:12:14 GMT

@Anonymous wrote:
i am uisng VS Comunity 2103.

Are you a time traveller?

Re: Newbie -Warning message

Anonymous — Wed, 08 Apr 2015 21:49:15 GMT

yes, clearly. its just so disappointing that Microsoft hasn't done more with VS in all that time!