Bug 13990 - Monogame add-in Installation Failed
Summary: Monogame add-in Installation Failed
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Version Control ()
Version: 4.0.12
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Alan McGovern
URL:
Depends on:
Blocks:
 
Reported: 2013-08-14 21:37 UTC by luthfi.chandra
Modified: 2013-08-14 23:14 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description luthfi.chandra 2013-08-14 21:37:54 UTC
Description of Problem:
Can't install Monogame addin.
It says:
"“The installation failed!

There was an error while scanning assembly: C:\Program Files(x86)\Xamarin Studio\AddIns\VersionControl\SharpSvn-SASL21-23-Win32.dll”"

I've tried to reinstall but the problem still not fixed yet.
Comment 1 Alan McGovern 2013-08-14 23:14:04 UTC
This has already been fixed and luckily we have a workaround: 

Rename the file: C:\Program Files(x86)\Xamarin Studio\AddIns\VersionControl\SharpSvn-SASL21-23-Win32.dll

to: SharpSvn-Sasl21-23-win32.dll  or SharpSvn-Sasl21-23-Win32.dll

There's a case mismatch in the filename which introduced this issue. By changing the case to the expected casing you will not get this error.