Loading User Information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading User Information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements


kettch kettch
  • So how did the Win10 install go for you?

    They are probably also releasing updates based on hardware and software configuration. From the data you got from the upgrade reservations, you could release the upgrade to a few hundred of a specific hardware and software setup. Based on the instrumented data you get back, you may decide to release it to a larger batch or hold them back while you make some tweak.

  • I'm not happy with Windows 10 (details inside) - am I missing something?

    , ScottWelker wrote


    I'll say it again. MS is not listening (to our kind) and is not interested in our input. They are going a different direction. As am I. I suggest you consider your alternatives JamieMitchell.

    There's nothing to say that they aren't listening. Look at the sheer volume of (often conflicting) feedback that they've gotten. If you have any proposals on how to integrate all of that and still have a usable product, the entire software industry would love to know how to do that.

  • Strange Lumia 950 button layout.

    The only stuff I've seen on future Lumias has all been wild speculation, including the name. Basically, we know absolutely nothing and there's no point in getting excited.

  • Win10: ​Bewildermen​t.... Not loading it...

    @SimonJ: It's not too late. We know that there will be regular updates, so hopefully as they work through the list of stuff, cleaning up icons might end up being a priority. People just need to make sure that the feedback keeps happening.

  • Why does Windows think it knows better than me?

    , cheong wrote

    @Sven Groot: No. I use manual update option, and see the message that it'll reboot after 4-minutes-something some time after I installed the updates. The two options I can select are "Reboot now" and "Close". The machine rebooted automatically several minutes after I selected the "Close" option and the work that I have on hand is lost because at that time I just thought it's the usual "postpone" button you get in Win7 and didn't read carefully. The several days argument is not reality.

    My machine is Surface Pro 3, and I usually install update roughly one hour before I go to bed, if it need to reboot, I have no problem to let it reboot. (Afterall, I manually started the update)

    I don't have spare machine to install Win10 so never tried that, but from the screen caps I see on the web, I can't find such option to specify when to reboot. If you can confirm that such option exist on non-business line of Win10, that's good.


    While the result is inconvenient, there is not excuse for not reading the dialog box. IT people are the worst offenders at that.

  • Visual Studio Code

    , bondsbw wrote

    @spivonious:  VS Community is free.

    It depends on what you are using it for. The license doesn't allow use for just anything.

  • Visual Studio 2015 RTM on MSDN

    @felix9: It's an odd choice of naming. If you look at the history of VS ISOs they've always used x86, but never x64.

    For example:

    2012 - en_visual_studio_premium_2012_x86_dvd_920758

    2013 - en_visual_studio_premium_2013_x86_dvd_3009258

    2015 - en_visual_studio_enterprise_2015_x86_x64_dvd_6850497

  • Visual Studio 2015 RTM on MSDN

    I just got a chance to log into MSDN to download it. There appears to be an x64 build now. The VS team has had very specific concerns about doing that in the past. Has anyone seen anything published that details what went into finally doing it?

  • Visual Studio 2015 RTM on MSDN

    , Proton2 wrote

    *snip*And the first beta required uninstalling all versions of Visual Studio first.

    There were also the builds that only shipped in a VM because they couldn't actually be installed.

  • Visual Studio 2015 RTM on MSDN

    , PeterF wrote

    I'm quite conservative and only uninstall an old release when all project can build, execute and can be maintained with a newer release ;) harddisk space doesn't cost as much as trying to re-create an uninstalled but working development environment.

    It's hard to impress upon people the value of a properly aged developer environment. I've gone toe-to-toe with our desktop people on various occasions. Burn it and reimage is fine for standard users, but that's an absolute last resort for me. Especially when one of their weird "we can do better than group policy" scripts is the problem.