Bug 33137 - Pinning of opened Xamarin Studio to a taskbar in Windows 10 produces icon duplicate
Summary: Pinning of opened Xamarin Studio to a taskbar in Windows 10 produces icon dup...
Status: REOPENED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Shell ()
Version: 5.9
Hardware: PC Windows
: Lowest enhancement
Target Milestone: Future Cycle (TBD)
Assignee: Marius Ungureanu
URL:
Depends on:
Blocks:
 
Reported: 2015-08-15 18:25 UTC by Mikhail Melnik
Modified: 2017-10-18 17:22 UTC (History)
7 users (show)

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


Attachments
Pinned icon plus duplicate (4.90 KB, image/png)
2015-08-15 18:25 UTC, Mikhail Melnik
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 for Bug 33137 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
REOPENED

Description Mikhail Melnik 2015-08-15 18:25:03 UTC
I have installed Xamarin Studio to a Windows 10 (upgraded from vanilla Windows 8.1). When I try to pin launched app to a taskbar it produces an icon duplicate. Launching the app from the pinned icon generates a duplicate as well.

Xamarin Studio
Version 5.9.5 (build 9)
Installation UUID: f31c63f5-caed-4b21-b062-e7fdfaa690d4
Runtime:
	Microsoft .NET 4.0.30319.42000
	GTK+ 2.24.22 (MS-Windows theme)
	GTK# 2.12.26

Xamarin.Android
Version: 5.1.5 (Indie Edition)
Android SDK: D:\Development\Android\bundle\sdk
	Supported Android versions:
		4.0.3 (API level 15)
		4.2   (API level 17)
		4.4   (API level 19)
		5.0   (API level 21)
		5.1   (API level 22)
Java SDK: C:\Program Files (x86)\Java\jdk1.7.0_71
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode, sharing)

Xamarin Android Player
Not Installed

Build Information
Release ID: 509050009
Git revision: b99cb19a1d3b15d8980c4616f13f837457e5b292
Build date: 2015-07-28 02:41:02-04
Xamarin addins: d53d6eceb828422f3d4aff8547f2f6bab6c9ea58

Operating System
Windows 6.2.9200.0 (64-bit)
Comment 1 Mikhail Melnik 2015-08-15 18:25:45 UTC
Created attachment 12526 [details]
Pinned icon plus duplicate
Comment 2 Atin 2015-08-17 11:03:32 UTC
I have Checked this issue and able to reproduce the reported behavior given in the bug description. When I open Xamarin Studio and select option "Pin this option to taskbar" then it creates a duplicate icon.

Screencast: http://www.screencast.com/t/GPFK2kTwe8lp
Ide Logs: https://gist.github.com/Mohit-Kheterpal/9c6562e954ef51bd306f

Environment Info:

=== Xamarin Studio ===

Version 5.9.5 (build 9)
Installation UUID: 25bf900b-cf03-4345-86c6-97f36fb7fd84
Runtime:
	Microsoft .NET 4.0.30319.42000
	GTK+ 2.24.22 (MS-Windows theme)
	GTK# 2.12.26

=== Xamarin.Android ===

Version: 5.1.5 (Enterprise Edition)
Android SDK: D:\Android\android-sdk
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
		5.1    (API level 22)
Java SDK: C:\Program Files\Java\jdk1.7.0_71
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) Client VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: 0.4.4
Location: C:\Program Files\Xamarin Android Player\DeviceManager.exe

=== Build Information ===

Release ID: 509050009
Git revision: b99cb19a1d3b15d8980c4616f13f837457e5b292
Build date: 2015-07-28 02:41:02-04
Xamarin addins: d53d6eceb828422f3d4aff8547f2f6bab6c9ea58

=== Operating System ===

Windows 6.2.9200.0
Comment 3 Cody Russell 2015-11-20 11:28:32 UTC
We need to make sure that SetCurrentProcessExplicitAppUserModelID() gets called during application initialization 1/ before any UI is presented and 2/ before jump lists are manipulated in any way.
Comment 4 xamarin-release-manager 2016-02-17 13:37:00 UTC
Fixed in version 6.0.0.4442 (master)

Author: Marius Ungureanu
Commit: 6d36b228830d9d1709a2b0800f92994eea004a11 (mono/monodevelop)
Comment 5 Atin 2016-02-18 14:01:45 UTC
I have checked this issue with latest Master build i.e. 
XamarinStudio-6.0.0.4472_037077baa787b678dbe6152f344c32d41de4a0b3 and I am getting same behavior given in the bug description. 

Hence I am reopening this issue.

Screencast: http://www.screencast.com/t/AEL4LNQh0

Environment Info:

=== Xamarin Studio ===

Version 6.0 (build 4472)
Installation UUID: 44f32fb4-6305-4e48-b118-0df2876ead69
Runtime:
	Microsoft .NET 4.0.30319.42000
	GTK+ 2.24.26 (Dark theme)
	GTK# 2.12.30.1

=== Xamarin.Profiler ===

Not Installed

=== Xamarin.Android ===

Version: 6.0.1.10 (Indie Edition)
Android SDK: D:\android-sdk
	Supported Android versions:
		2.3    (API level 10)
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.1
SDK Build Tools Version: 23.0.2

Java SDK: C:\Program Files\Java\jdk1.7.0_71
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

Version: 0.6.5
Location: C:\Program Files\Xamarin Android Player\DeviceManager.exe

=== Build Information ===

Release ID: 600004472
Git revision: 037077baa787b678dbe6152f344c32d41de4a0b3
Build date: 2016-02-18 03:47:45-05
Xamarin addins: 7064051bafa00aeb771d9ee8fbc1831a2be77517
Build lane: monodevelop-windows-master

=== Operating System ===

Windows 10.0.10240.0 (64-bit)

=== Enabled user installed addins ===

Test Template Parameters 0.2
Comment 6 Marius Ungureanu 2016-02-18 14:13:35 UTC
I'm not seeing this locally. It seems you have stale registries around. I'll dig up and try to find out what's causing this.
Comment 7 Marius Ungureanu 2016-02-18 14:18:40 UTC
Are you on a 64bit operating system?

Also:

1. Open regedit.exe
2. Go to HKEY_LOCAL_MACHINE -> SOFTWARE -> Xamarin -> XamarinStudio (tell me if it exists)
3. Go to HKEY_LOCAL_MACHINE -> SOFTWARE -> WOW6432Node -> Xamarin -> XamarinStudio (tell me if it exists)

If both of them exist, delete the one at 2. and tell me if you can still reproduce. If so, there's nothing we can do to fix this, Windows 10 had broken installers shortly after release by installing 32bit software under the registry at 2) instead of 3), and it still tries to load that before going to WOW6432Node - which is the proper place for 32bit apps.
Comment 8 Atin 2016-02-18 15:06:25 UTC
Yes, I am working on 64bit operating system.

Screencast: http://www.screencast.com/t/cHKh562b1kf5

Here is the info for the Comment 7:

1. Open regedit.exe
2. Go to HKEY_LOCAL_MACHINE -> SOFTWARE -> Xamarin -> XamarinStudio (Does not exist)
Screencast: http://www.screencast.com/t/8eaXxbvKa

3. Go to HKEY_LOCAL_MACHINE -> SOFTWARE -> WOW6432Node -> Xamarin -> XamarinStudio (it exists)
Screecast: http://www.screencast.com/t/s8DoB6hsQ7H
Comment 9 Marius Ungureanu 2016-04-25 02:15:42 UTC
Since this is environment specific - I managed to reproduce it, but it went away by itself after some time, I'm marking the priority and severity accordingly.