Visual Studio 2017 RC

[FeodorFitsner]

After installing VS 2017 RC on top of VS 2015 base image:

1. Install AppVeyor vstest.console logger and MSTestV2 support libraries

2. Replace MSBuild in PATH with MSBuild 15.0

3. Install latest NuGet 3.5

4. Pre-cache .NET Core:

   cd %temp%
   md app1
   cd app1
   dotnet new
   dotnet restore
   dotnet run

5. Install CMake 3.7.1

6. Re-install Git and Git LFS

7. Disable Bonjour Service and IpOverUsbSvc and services:

   Set-Service -Name 'Bonjour Service' -StartupType Disabled
   Set-Service -Name 'IpOverUsbSvc' -StartupType Disabled

8. Apply workaround for NuGet Build Tasks

[niemyjski]

We really really need this, any updates not this?

[ghuntley]

[madskristensen]

Is the image created to include everything the "Visual Studio 2015" image has + Visual Studio 2017 RC with SDK?

[FeodorFitsner]

Well, this is what we were going to do - install VS 2017 RC on top of VS 2015 image. Would that work or you have other suggestions?

[clairernovotny]

One suggestion might be to include the build number in the image name... the version of the RC was updated two days ago, which is later than the one released last Wed. Might be safe to assume there'll be more, so there'll either need to be a way to identify them or something to keep an eye on the updates and roll out new images.

[FeodorFitsner]

I think we'll be maintaining a single Visual Studio 2017 RC image and update VS 2017 in it as soon as new updates appear.

[FeodorFitsner]

We've got a build worker image with Visual Studio 2017 RC installed. Before making it available for everyone we'd like to do some for of "private beta", so please let us know if you want this image to be added under your account (either post your AppVeyor account name here or send to team@).

[madskristensen]

@FeodorFitsner I would love to give it a spin. Account name "madskristensen"

[andrewvk]

andrewvk

[FeodorFitsner]

Image named Visual Studio 2017 RC has been added to both accounts.

[ejsmith]

ejsmith

[FeodorFitsner]

@ejsmith - done

[madskristensen]

@FeodorFitsner It works great! Just built an extension successfully. Thanks

[georgeduckett]

Yes please, georgeduckett

[madskristensen]

@FeodorFitsner I have an extension with a unit test project and when AppVeyor builds it, I get this issue:

Error: Could not find a test logger with URI or FriendlyName 'Appveyor'

[ig-sinicyn]

@FeodorFitsner

ours failed with

vstest.console /logger:Appveyor "C:\projects\codejam\PerfTests\src-MSTest\bin\Release\CodeJam.PerfTests.MSTest.dll" "C:\projects\codejam\PerfTests\tests-MSTest\bin\Release\CodeJam.PerfTests-Tests.MSTest.dll"

Microsoft (R) Test Execution Command Line Tool Version 15.0.0.0
Copyright (c) Microsoft Corporation.  All rights reserved.
Error: Could not find a test logger with URI or FriendlyName 'Appveyor'.
Command exited with code 1

Get-ChildItem *.PerfTests.log -r | % { Push-AppveyorArtifact $_.FullName -FileName $_.Name }
Uploading artifact CodeJam-Tests.Performance.ImportantOnly.PerfTests.log (39,279 bytes)...100%

Appveyor.yml is here.

[FeodorFitsner]

Thanks, will take a look.

[janhohenheim]

Can I try it too? I'm logged into AppVeyor with this Github account.

[FeodorFitsner]

@georgeduckett, @SirRade - added

[georgeduckett]

@FeodorFitsner, just tried compiling my extension which uses some C#7 syntax and it fails: https://ci.appveyor.com/project/georgeduckett/teamcoding I believe I've set the environment correctly. Is there something else I need to do?

[FeodorFitsner]

Add this to project's appveyor.yml:

image: Visual Studio 2017 RC

[georgeduckett]

@FeodorFitsner That's done the trick, thanks. Any reason why setting the Build Worker Image in Settings for the project didn't work?

[FeodorFitsner]

because if it's appveyor.yml then all settings should be there - UI settings are ignored.

[georgeduckett]

Ahh ok, thanks.

[TcT2k]

I would like to try the beta. (using this github account)

[janhohenheim]

@FeodorFitsner Works great so far, thank you very much.
I first had the same trouble that @georgeduckett had. The solution is not very intuitive.

[caitchison]

I would love to be in this beta. Account name is trinocity

[csmager]

@kzu I didn't know that existed. I see you're the owner. Will give it a look and see if we should go that way. I think the required VSIX still should be installed if it's intended that you should be able to use the installed version on the worker image, however.

[kzu]

I'm just redistributing in a convenient way the binaries, that's all. I did for this same reason, avoiding requirements on CI bots

[FeodorFitsner]

All right, WiX extension for VS 2017 was missing. It should be fine now.

[litichevskiydv]

@FeodorFitsner, I have just tried new Visual Studio 2017 image (https://ci.appveyor.com/project/litichevskiydv/tipsandtricks/build/1.0.21) and in TESTS tab I see "The build job has not produced any test results", but in CONSOLE I see "Total tests: 88. Passed: 88...". Previously everything worked fine (https://ci.appveyor.com/project/litichevskiydv/tipsandtricks/build/1.0.6). Please, help.

[bhagvan]

@FeodorFitsner can you please add a custom image with VS 2017 + VS 2015 to my account please
account name is novitas

[csmager]

@bhagvan both are installed in the Visual Studio 2017 image - see this comment and the list of pre-installed software for more detail of what's on each VM.

[roji]

@FeodorFitsner confirm successful MSI build with Wix 3.11 RC, thanks for the superb reactivity!

[bhagvan]

@csmager thanks for the quick response ... i will look into my build scripts

[jbogard]

@FeodorFitsner does the VS 2017 image have any version of SQL Server installed? Even LocalDB would work.

[JSkimming]

@jbogard I believe it does, we use the Azure storage emulator, when it starts I noticed it logs the following:

"C:\Program Files (x86)\Microsoft SDKs\Azure\Storage Emulator\AzureStorageEmulator.exe" start
Windows Azure Storage Emulator 5.0.0.0 command line tool
Autodetect requested. Autodetecting SQL Instance to use.
Looking for a LocalDB Installation.
Probing SQL Instance: '(localdb)\MSSQLLocalDB'.
Found a LocalDB Installation.
Probing SQL Instance: '(localdb)\MSSQLLocalDB'.
Found SQL Instance (localdb)\MSSQLLocalDB.
Creating database AzureStorageEmulatorDb50 on SQL instance '(localdb)\MSSQLLocalDB'.
Granting database access to user APPVYR-WIN\appveyor.
Database access for user APPVYR-WIN\appveyor was granted.
Initialization successful. The storage emulator is now ready for use.
The storage emulator was successfully started.

Here's the full list of install software:

https://www.appveyor.com/docs/build-environment/#pre-installed-software

If you want to start SQL express, here's the documentation to follow:

https://www.appveyor.com/docs/services-databases/#sql-server-2016

[FeodorFitsner]

All - thank you very much for your efforts in testing Visual Studio 2017 RC image. I'd like to inform you that we are going to discontinue Visual Studio 2017 RC image starting next week (March 20).

Please switch to Visual Studio 2017 image if not done already.

[seburgi]

Currently I am not able to RDP into machines running on the new 2017 image. I tried 2015 machines and there it works. Can somebody confirm this behavior?

[onqtam]

Previously I could do builds with VS 2008/2010/2012/2013/2015 all at the same time.

Now I want to incorporate 2017 as well. To do that I need to set the image to Visual Studio 2017 but then the builds for 2008/2010/2012... all fail because the newest image doesn't have all those previous VS versions.

I tried adding image to the build matrix like this:

environment:
  matrix:
  - platform: x64
    image: Visual Studio 2015
  - platform: x64
    image: Visual Studio 2017

but it doesn't seem to work - only when setting it globally does it actually set anything - and if I set 2017 globally - then there are no older VS versions.

How can I tackle this problem?

[micbou]

@onqtam You need to set the APPVEYOR_BUILD_WORKER_IMAGE environment variable:

environment:
  matrix:
  - platform: x64
    APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2015
  - platform: x64
    APPVEYOR_BUILD_WORKER_IMAGE: Visual Studio 2017

[onqtam]

@micbou omg Thanks! just tested it and it worked!

[mcintyre321]

Does anyone know a good way to set the <PackageVersion> in csproj to the AppVeyor build no? All my packages are building as foo.1.0.0.nupkg

[jbogard]

Check out Serilog and its build and project file.

…

On Sat, Mar 18, 2017 at 7:39 AM Harry McIntyre ***@***.***> wrote: Does anyone know a good way to set the <PackageVersion> in csproj to the AppVeyor build no? All my packages are building as foo.1.0.0.nupkg — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1179 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAGYMrlsoV1Kw1uACVyGx7h6Jbi9rHgCks5rm9BqgaJpZM4K0h-h> .

[JSkimming]

@mcintyre321 I got it working on a project I manage. Essentially:

msbuild <proj path> /t:pack /p:Configuration=%CONFIGURATION%;PackageVersion=%APPVEYOR_BUILD_VERSION%;IncludeSource=true

Here's the documentation.

[mcintyre321]

Thanks @jbogard and @JSkimming

I brute forced it with this beforeBuild script in the end

nuget restore

$configFiles = Get-ChildItem . *.csproj -rec
$versionString = "<PackageVersion>" + $env:APPVEYOR_BUILD_VERSION + "</PackageVersion>"
foreach ($file in $configFiles)
{
    (Get-Content $file.PSPath) |
    Foreach-Object { $_ -replace "<PackageVersion>1.0.0</PackageVersion>", $versionString  } |
    Set-Content $file.PSPath
}

[FeodorFitsner]

Visual Studio 2017 RC image has been removed. Please switch to Visual Studio 2017 image.