Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I didn't attribute this bug into the C# binding component because it appears that it's an IDE/Editor issue.
I'm using three NET dlls in my project. Two of them are commercial 3rd party .NET libraries (one is a DirectX based renderer called "TrueVision3D" and the other a crossplatform Audio rendering library named "irrKlang") that i'm pretty certain are just wrappers of an undrelying C++ library. The third dll is a pure NET lib that i made myself with VS2008. When i add all of them in the reference list, all is fine. No problems there.
When i'm trying to "using" them, Intellisense ONLY shows the namespace of my pure NET dll. The namespaces of the other two commercial dlls are not shown.
When i explicitly type their name (which is a real pain without intellisense) ....
the IDE does marks every reference in these namespaces as erroneous "CS0103: The name '....' does not exist, blah, blah" BUT the project compiles WITHOUT ANY errors, the libraries function correctly and the program runs just fine. Having no Intellisense on these namespaces is a real pain because any syntax/type/etc error on a method and you'd have no clue as to which line caused it since all of them are marked as errors!
Sounds like the assembly reader has trouble with mixed-mode (managed+native) assemblies.
I don't suppose there's something i could do to fix that?
"The worthless maggots here in project-land will continue to pray and offer bananas, mangos and papayas from our harvests until a good and noble demi-god in the Xamarin pantheon decides to look upon this utter misfortune and extend his divine grace towards us mere mortals. Oh great ones, we kiss your .... feet!"
Hm, I'll do it for 2 bananas !
Should be fixed in our next major release :)