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.
Creating a new bindings project in Visual Studio generates an invalid project. For example, the assembly name is set to
which doesn't get substituted during build and results in $assemblyname$.dll being created.
What is going on? Are we the only ones using Xamarin with Visual Studio?
Support for iOS bindings projects in Visual Studio is a new feature starting in XamarinVS 3.11 (currently on the Alpha channel).
This bug was originally filed against XamarinVS 4.0 (C6), but that version has not been released yet, so I suspect the actual version might have been one of the XamarinVS 3.9 versions.
- Add your complete version information from "Help -> About Microsoft Visual Studio -> Copy Info" on this bug. (See also .)
>  https://kb.xamarin.com/customer/portal/articles/1910343-when-and-how-should-i-file-a-bug-report-
(If this link redirects to the top-level `https://kb.xamarin.com` page the first time you click it, try clicking it once more.)
- If you're already using XamarinVS 3.11, please zip up and attach on this bug report the complete project after you've generated it from the template. I just tested creating a new bindings project on XamarinVS 3.11, and the AssemblyName looks fine:
Thanks in advance!
I'll mark the bug as resolved fixed based on Comment 1.
Please feel free to reopen it if you can still reproduce the issue with current bits.