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.
Created attachment 5115 [details]
Test Project from Case #47844
Test project for the below error is attached.
When using the Assembly.Location the reference via
Assembly currentAssembly = Assembly.GetExecutingAssembly();
currentAssembly.Location property to feed a FileVersionInfo.
FileVersionInfo info = new FileVersionInfo(currentAssembly.Location), the File Version information appears in both Debug Mode. However, when set to Release mode, the following error occurs:
Linking: None, Use Shared Runtime: No, Use Fast Deployment: No
Expected Version: '188.8.131.52(AssemblyInfo.cs)'
GotVersion: 'File does not exist or wrong path.' (FileVersionInfo.FileVersion)
GotVersionUri:'File does not exist or wrong path.'(FileVersionInfo.FileVersion)
Windows 8.1 Professional
Visual Studio 2012 Professional
Xamarin 4.8.03005 (3c344aeb)
Tested Target Device(s):
Google Nexus 7 (2013): Android 4.3
Medion Lifetab (P9514): Android 4.0.3
Samsung Galaxy S (GT-I9000) [rooted running CyanogenMod 10.1.3]: Android 4.2.2
This is By Design (and documented!):
> * The application assemblies (containing IL) are stored uncompressed within
> the assemblies folder [within the .apk]
> * Note: Assembly location information such as Assembly.Location and
> Assembly.CodeBase cannot be relied upon in Release builds. They do
> not exist as distinct filesystem entries, and they have no usable