VS 2015

lair's Avatar


22 Jul, 2015 12:52 PM

I have a private project on Basic paid plan, which is currently set up to run on "Windows Server 2012 R2" environment. I want to upgrade to VS 2015 and use C# 6 features. As far as I understand, I have to change my environment to one containing VS 2015.

What are pros and cons between setting environment to "Visual Studio 2015" and asking for the project to be moved to "faster OSS environment with VS 2015 installed"?

  1. Support Staff 1 Posted by Feodor Fitsner on 22 Jul, 2015 05:12 PM

    Feodor Fitsner's Avatar

    If you select "Visual Studio 2015" image (OS setting on UI or in appveyor.yml) builds will run on Azure which is slower compared to Basic/Pro workers.

    That Hyper-V-based environment for OSS is almost the same fast as Pro environment and it has VS 2015 on build workers, so you don't need a custom image.

    We'd install VS 2015 to Pro environment, but seems like this could break a lot of builds. The problem mainly in .NET 4.6 which is an "in-place" update to .NET 4.x causing incompatibility issues in many apps/libs. Just an example - Service Bus for Windows doesn't start at all if .NET 4.6 is installed on the machine.

    We are going to study demand for VS 2015 and plan capacity/migration. For now we're going to move customers one-by-one on request basis. Moreover, we don't expect everyone migrating to VS 2015 in one night :)

  2. 2 Posted by lair on 22 Jul, 2015 05:40 PM

    lair's Avatar

    Sounds pretty reasonable (run into a couple of bugs already). But let's give it a try and move both mine (srogovtsev) projects to OSS environment. Thanks!

  3. Support Staff 3 Posted by Feodor Fitsner on 22 Jul, 2015 05:44 PM

    Feodor Fitsner's Avatar


  4. 4 Posted by lair on 22 Jul, 2015 05:49 PM

    lair's Avatar

    Thanks, run both builds, doesn't seem to be a problem.

  5. lair closed this discussion on 22 Jul, 2015 05:49 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac