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 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 use my own custom MT.D.
My App has a project reference to my MT.D.
My lib, auto added a reference to the built in monotouchdialog-1.dll
When I ran the build, it compiled everything fine. At run time it was blowing up without giving me any real error. Just there was an issue at my static main.
When I ran the same code in XS it told me there was an error casting types which let me know the real problem.
The debugger on VS should tell me the same error.
Hey James, any chance you could zip up your repro project with the custom MT.D?
I'd like to see if this is still a problem.
No response yet, although that doesn't really mean it's gone. I can't track this down before the release myself, so if you do have a repro please attach!
Pj, try the sample for https://github.com/Clancey/FlyoutNavigation
IT is easily caused by referencing MT.D in source from either the lib or the sample. Then referencing the built in one in the other repo. Flyout is doing that right now.
This one might be fixed in the current master + 1.8 builds, following Alan's changes which removed the custom assembly resolver we had in the MTVS tasks. James, can you retest?
This has been fixed. We let MSBuild resolve all the references for us now.
I have checked this issue with following builds:
All Windows and Mac
X.S 4.2.3(build 54)
Xamarin for VS 1.12.207
I have run the attached sample which is mentioned in Comment#3. I am successfully able to run the application on both Windows and Mac.
Please let me know it is correct behavior or not?
I have checked this issue with attached sample in Comment3, I am able to build and run this sample successfully. Also in Comment 7, Prashant was able to build and deploy the sample successfully.
Xamarin for VS 1.12.278
Please let me know if I have to check any this else to verify this issue.
As of now, I am closing this issue.