Bug 9235 - SDK Updater app and MTVS Installer need to be signed.
Summary: SDK Updater app and MTVS Installer need to be signed.
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 1.0.x
Hardware: PC Mac OS
: High major
Target Milestone: ---
Assignee: Duncan Mak
Depends on:
Reported: 2013-01-03 13:12 UTC by PJ
Modified: 2015-10-06 16:08 UTC (History)
6 users (show)

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

Description PJ 2013-01-03 13:12:17 UTC
In the UAC dialog, the publisher is listed as Unknown.

Assigning to Duncan, CC-ing Grendel for any additional information needed.
Comment 1 PJ 2013-01-25 14:40:23 UTC
Can we do this?
Comment 2 Marek Habersack 2013-01-25 15:11:13 UTC
the SDK Synchronization utility would have to be signed. Jose, can you help Duncan with this? Thanks :)
Comment 3 Dominique Louis 2013-06-04 10:49:06 UTC
Duncan any further info on this issue?
Comment 4 Duncan Mak 2013-08-28 15:16:38 UTC
Do we still need to do this?
Comment 5 Marek Habersack 2013-08-28 19:30:26 UTC
Comment 6 PJ 2013-12-09 12:26:51 UTC
I know Duncan and Bacon were working on doing more signing, I'm putting this back to NEW to see where we're at with this after comment 5.
Comment 7 Daniel Cazzulino 2014-05-19 13:41:23 UTC
Is this done already? Can I put it in the 2.0.1 milestone? (that's our vNext for now)
Comment 8 Joaquin Jares 2015-10-06 16:08:55 UTC
This has gone through a lot of iterations now so I'm assuming it's fixed. Marking FIXED for retesting.