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.
MTVS is removing periods from the produced exe. This is causing issues during compiling/deploying.
Steps to reproduce: Add a period in the project namespace. Or go to components and add Alert Center. Then build the iOS sample.
It seems not to be a VS issue. Instead, it seems the AlertiOSSample.csproj have no periods in the AssemblyName
*** Bug 9982 has been marked as a duplicate of this bug. ***
Today, we have verified this issue with the latest build:
We have observed that the issue still exists and the root cause of this issue is:
For some of the application for example the iOS sample of the Component Range Slider.
As if the Assembly name of the application contains periods in between it, then when the user try to debug the application it gives the deployment error, and does not debug the application successfully.
However, when the user removes those periods from the assembly name, and then try to debug the application it successfully deploys to the device as well as on the simulator.
Below is the screencast for the same:
Here is the path of the assembly name:
Project Option >> Application >> Assembly name
Hence, reopening this issue.
Hello Jatin, the csproj is invalid, the AssemblyName is "RangeSlider"
For some reason VS behave different from XS (and is displaying RangeSlider.iOS.Sample).
So, every other csprojs with period or not are working. :)
An update to the above issue:
As per our understanding this should not be an invalid issue. As this is happening for only few applications.
In case of VS:
In the project properties the assembly name is appearing as "RangeSlider.iOS.Sample" whereas, the assembly of this sample is generated with the name of "RangeSlider.exe" at the location:
C:\Users\win7\Documents\Visual Studio 2012\Projects\HelloWorld_App11\Components\rangeslider-1.0\samples\RangeSlider.iOS.Sample\bin\iPhoneSimulator\Debug
And since system tries to search for assembly name "RangeSlider.iOS.Sample" and not able to find that, it gives the error message and the application does not deploy to device/simulator.
In case of MD on Mac:
However, when we check the same using MD on the Mac environment, then for the same sample in the Project option -> Output the assembly name is appearing as "RangeSlider" and also the assembly is getting generated with the same name.
So this issue is not appearing on the Mac environment using MD.
Note: This issue is appearing only on VS and for few applications not for all.
PJ, please review our assessment for this bug and take further appropriate action.
AS of now reopening this issue.
Are you able to create a project with dot on XS or VS and repro the error?
There are different assembly name fields for XS and VS, we should set both perhaps.
Fixed in mtvs-18.104.22.168
Today we have checked this issue on following builds :
If name of the application contains periods in between it and when we try to debug the application it deploys on device/simulator successfully.
It create .exe file without periods.
Like if name of application is "create.new.test.1" then it create exe with name "createnewtest1.exe"
Hence changing its status to verified.