I suggest you ...

Allow use of Remoted iOS Simulator from ALL editions of Visual Studio

Until the latest release, where the iOS simulator on windows was renamed to Remoted iOS Simulator, it was possible to remote the iOS simulator to windows from any version of Visual Studio.

With the current release this has changed. Now a Visual Studio Enterprise Edition licence is required.

Clearly this is not a technical restriction as it was previously possible, so it must be a simple money grab, which goes completely against Microsoft's more open approach to feature availability from recent years.

For those of us who develop with neither direct, sole access to a Mac build machine, nor the offensively expensive Enterprise edition of VS, please change this back and allow use of the Remoted iOS simulator on windows from ALL editions of VS.

1,077 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Mark LawrenceMark Lawrence shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    39 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Alfred PellockAlfred Pellock commented  ·   ·  Flag as inappropriate

        yep, unwise product marketing decision that foils growth of the adoption of Xamarin and more. So shall I better sell my surface pro, install Windows 10 as a virtual machine on my macbook and just do without a touchscreen? Well, I may do that and I may even decide to do without Windows at all as I don't see much use of UWP. I was so happy with VS and now that. Too bad and hopefully rectified in a reasonable timespan.

      • ManuelManuel commented  ·   ·  Flag as inappropriate

        As an individual developer and having access to VS Professional, Remoted iOS simulator can help :(

      • Lukáš NovotnýLukáš Novotný commented  ·   ·  Flag as inappropriate

        I understand that MS needs to sell enterprise with something, but this combined with unavailability of the profiler seriously hinders our options when choosing hardware and extra ~$2400 yearly per developer is impossible for us as small group of 6 developers. Please reconsider adding both remote ios simulator and profiler to professional.

      • BrianBrian commented  ·   ·  Flag as inappropriate

        This is a really dumb move by Microsoft, not that they are any strangers to such!

      • Geoff DavisGeoff Davis commented  ·   ·  Flag as inappropriate

        It is vital to the growth of Xamarin vs Native that all tools be available to all levels of Visual Studio Developers. Keep up the good work Microsoft, Making Xamarin completely free to Developers is awesome but in keeping with the user experience is just as important.

        Please make the Remoted iOS Simulator accessable to all levels of Visual Studio.

      • Tim MyersTim Myers commented  ·   ·  Flag as inappropriate

        Our organization only allows us to use Visual Studio Professional via MSDN subscription. We can't cost justify MSDN Enterprise for nearly 5 times the cost of professional. Decisions like this will have a dramatic affect on the adoption of Xamarin for iOS development using Visual Studio.

      • PatrickPatrick commented  ·   ·  Flag as inappropriate

        Crazy decision. I've worked with the remote simulator since it was in preview. Tried setting a coworker up with it for about 2 days trying to update/uninstall/install Xamarin and Xcode, eventually updating the Mac OS to Sierra trying the newest version (and swapping Macs because an older Mac couldn't update to Sierra). 2 freaking lost days and now I find out it's not a malfunctioning program but a malfunctioning policy!
        They better return this option to all VS editions, as it's such an annoyance to need to use the Mac for everything :/

      • Mark LawrenceMark Lawrence commented  ·   ·  Flag as inappropriate

        So, given that the newly released VS2017 also has this restriction, it's clear they don't intend to change it now.

        It would have been nice to get some explanation as to why this is the case, but I guess we're just the fools who thought that maybe they actually used uservoice. It's clear that they do not.

      ← Previous 1

      Feedback and Knowledge Base