Bug 16970 - Incompatible version of Xamarin.shell detected
Summary: Incompatible version of Xamarin.shell detected
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: Installer ()
Version: 1.8.x
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Dominique Louis
URL:
Depends on:
Blocks:
 
Reported: 2013-12-26 12:11 UTC by Andy
Modified: 2014-01-09 12:48 UTC (History)
8 users (show)

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


Attachments
Wrong error (14.37 KB, image/png)
2013-12-26 12:11 UTC, Andy
Details


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 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 NOT_ON_ROADMAP

Description Andy 2013-12-26 12:11:32 UTC
Created attachment 5734 [details]
Wrong error

Obviously there is also an error in the detection

(no xamarin.shell version file ...)

Can you please demolish and recreate from zero all the installers and updaters ? They basically never work as they should.
Comment 1 PJ 2014-01-09 12:22:38 UTC
Hi Andy,

I completely understand how frustrating some of the installation experiences can be on Windows. Specifically, we don't currently support downgrading your extension versions without a full uninstall and re-install.

This is all changing in the next major MTVS release, as we're merging both of the extensions into a single installer that will ensure compatibility at all times.

Right now, you'll have to go and manually remove C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Xamarin\Shell\1.0.0\

In some cases, the steps can get a little bit more complicated. Here's a full set of steps for re-setting your machine so that you can install the current stables or betas and get back to working order:

Note that you should *always* make a backup of your registry, as improperly modifying your registry can be irrecoverable without a backup. 

1) Uninstall both VS extensions 
2) Open the registry editor (regedit)
3) Look for this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SharedDlls
4) Find all the entries that match this pattern:
C:\Program Files*\Microsoft Visual Studio 1*.0\Common7\IDE\Extensions\Xamarin
5) Delete them (see http://screencast.com/t/Oxhvr95Whref ).
6) Delete any leftover files on the filesystem that match this pattern:
C:\Program Files*\Microsoft Visual Studio 1*.0\Common7\IDE\Extensions\Xamarin

Hope this helps!
Comment 2 Andy 2014-01-09 12:28:32 UTC
Glad somebody understands me !

While a working installer/updater will certainly help, as I mentioned in other bug reports, there's the other part missing, that would help a lot in these not-so-final tools:

- a full, updated, _dated_ changelog for betas and stable, for VS too. 
- at least a mention on the bug tracking of the version where they appear to be fixed.

so this bug remains new, not confirmed ?
Comment 3 PJ 2014-01-09 12:31:46 UTC
Unfortunately it's actually going to become a WONTFIX, as there is no plan for addressing the issue until the extensions are merged. 

Then this issue will be 'fixed' simply by removing the ability for the shell versions to become mismatched. All the logic for checking that compatibility will be removed.

I'll resolve this one now but please let me know if this doesn't work for you!
Comment 4 Andy 2014-01-09 12:33:14 UTC
Ok, thanks. Can you at least tell me roughly when can we get this fixed installer ?
Comment 5 PJ 2014-01-09 12:38:14 UTC
I'm hesitant to give even a rough estimate as the QA process always finds a significant number of bugs, but it's very close to being completed on the development side of things. 

The best course of action right now is to try to follow the steps outlined above and get into a working state.

I'm also wondering - has moving your projects off of the network share effectively reduced the wait time between starting debugging and the app running? I want to make sure we're helping you get the best experience possible with the current set of releases.
Comment 6 Andy 2014-01-09 12:48:18 UTC
Moving the solutions to the PC side was night and day, in respect to the Mac side. So yes, thanks that helped a lot. Unfortunately, since the VS plugin is still incomplete and buggy in many aspects, I have to periodically build on the Mac side, which actually takes about the same, or even more, than on the PC before trading places. 

So I'm marginally better off, but these things are still problematic:

- xcassets (not in VS) https://bugzilla.xamarin.com/show_bug.cgi?id=17061

- certificates (they still don't work on VS for me) https://bugzilla.xamarin.com/show_bug.cgi?id=17062

- glitches https://bugzilla.xamarin.com/show_bug.cgi?id=17063
https://bugzilla.xamarin.com/show_bug.cgi?id=17071
https://bugzilla.xamarin.com/show_bug.cgi?id=17072
https://bugzilla.xamarin.com/show_bug.cgi?id=16562

- random bugs. Yep, there's still a bit of unreliability in the plugin, and I suspect some races or similar stuff happens behind because I get randomly weird errors, some of which I reported.
https://bugzilla.xamarin.com/show_bug.cgi?id=17039
https://bugzilla.xamarin.com/show_bug.cgi?id=17055
https://bugzilla.xamarin.com/show_bug.cgi?id=16179

There's also the issue that I haven't reported that many times the VS plugin isn't able to kill the process on the simulator. This also slows down things a lot

I think that's a fairly comprehensive list of the problem I have on VS...

so yes, I appreciate your effort, although I don't know if it's best experience possible ... :)