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.
Created attachment 12212 [details]
Reloading iOS project removes "." period characters from the "AssemblyName" element if any are present
## Regression status: this has been messy for quite some time.
It appears this is related to the fix for Bug 19662 and Bug 19902?
At its core, it might be a duplicate of Bug 16081?
If we look at Bug 19483, we see some discussion to the effect that "fixing up" the AssemblyName automatically within the `.csproj` is probably _not_ the desired behavior. Users should probably be allowed to set the AssemblyName _any way that Visual Studio will allow_ within the `.csproj`, and VS shouldn't "change that behind the user's back." If Xamarin.iOS has to do some "internal fixups" of that name during the build process, that's another question. Throwing build errors rather than performing an "internal fixup" is another approach. A mix of approaches might be appropriate, but this all probably needs careful consideration.
What's more, as per Bug 30348, Comment 8, it appears that the "The assembly name ... cannot contain more than one dot." restriction is being lifted in Cycle 5 – Service Release 3, so this specific issue with removing "." dot characters is now even "more different" than how it used to be.
If nothing else, I believe we can now allow "." characters within the AssemblyName in XVS.
GOOD: Xamarin for Visual Studio 184.108.40.206 (4c7fa6a) (from Bug 16081, Comment 6)
BAD: Xamarin 220.127.116.113 (daebc31)
BAD: Xamarin 3.11.816.0 (cefca47)
BAD: Xamarin 3.11.666.0 (ebae43a)
BAD: Xamarin 3.9.547.0 (20fd2f0)
BAD: Xamarin 18.104.22.168 (10cfd17)
## Steps to reproduce
1. Open the attached test case in Visual Studio. This is a new "Visual C# -> iOS -> iPhone -> Single View" project with the AssemblyName set to "UnifiedSingleView.Iphone.1".
2. Right click the project in the solution explorer and select "Unload project".
3. Right click the project in the solution explorer and select "Edit [project name]".
All the dots have been removed from the AssemblyName:
*** Bug 31975 has been marked as a duplicate of this bug. ***
Any chances for a fix in the near future?
+1. We are also looking for a fix for this, and have been hampered for some time. Currently we are unable to use Visual Studio in conjunction with our continuous integration environment due to this issue.
I'm missing resharper and all the other joys that VS brings.
Please can someone from Xamarin get back to us on this? It has been open for over a year now and is causing us considerable issues. It prevents us from being able to use VS.
Fixed in version 22.214.171.1249 (cycle8)
Commit: 3adccba90a744cf50f4f7686431768ff2c4e4413 (xamarin/XamarinVS)
I have checked this issue with latest build of Cycle 8 and observed that this issue has been fixed as shown in screencast : http://screencast.com/t/z8iCXvHDu