New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visual Studio 2017 RC #1179

Closed
FeodorFitsner opened this Issue Nov 16, 2016 · 552 comments

Comments

Projects
None yet
@FeodorFitsner
Member

FeodorFitsner commented Nov 16, 2016

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

@FeodorFitsner FeodorFitsner added this to the 6-nov-2016 milestone Nov 16, 2016

jnferner referenced this issue in jnferner/Hippocrates Nov 18, 2016

Downscale project settings
Change this to VS15 when appveyor supports it
@niemyjski

This comment has been minimized.

Show comment
Hide comment
@niemyjski

niemyjski Nov 21, 2016

We really really need this, any updates not this?

niemyjski commented Nov 21, 2016

We really really need this, any updates not this?

@ghuntley

This comment has been minimized.

Show comment
Hide comment

ghuntley commented Nov 22, 2016

@madskristensen

This comment has been minimized.

Show comment
Hide comment
@madskristensen

madskristensen Nov 22, 2016

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

madskristensen commented Nov 22, 2016

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

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 22, 2016

Member

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?

Member

FeodorFitsner commented Nov 22, 2016

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?

@onovotny

This comment has been minimized.

Show comment
Hide comment
@onovotny

onovotny Nov 22, 2016

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.

onovotny commented Nov 22, 2016

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

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 22, 2016

Member

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.

Member

FeodorFitsner commented Nov 22, 2016

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

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 23, 2016

Member

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@).

Member

FeodorFitsner commented Nov 23, 2016

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

This comment has been minimized.

Show comment
Hide comment
@madskristensen

madskristensen Nov 23, 2016

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

madskristensen commented Nov 23, 2016

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

@andrewvk

This comment has been minimized.

Show comment
Hide comment
@andrewvk

andrewvk commented Nov 23, 2016

andrewvk

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 23, 2016

Member

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

Member

FeodorFitsner commented Nov 23, 2016

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

@ejsmith

This comment has been minimized.

Show comment
Hide comment
@ejsmith

ejsmith commented Nov 23, 2016

ejsmith

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner
Member

FeodorFitsner commented Nov 23, 2016

@ejsmith - done

@madskristensen

This comment has been minimized.

Show comment
Hide comment
@madskristensen

madskristensen Nov 23, 2016

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

madskristensen commented Nov 23, 2016

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

@georgeduckett

This comment has been minimized.

Show comment
Hide comment
@georgeduckett

georgeduckett Nov 23, 2016

Yes please, georgeduckett

georgeduckett commented Nov 23, 2016

Yes please, georgeduckett

@madskristensen

This comment has been minimized.

Show comment
Hide comment
@madskristensen

madskristensen Nov 23, 2016

@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'

madskristensen commented Nov 23, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@ig-sinicyn

ig-sinicyn Nov 23, 2016

@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.

ig-sinicyn commented Nov 23, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 23, 2016

Member

Thanks, will take a look.

Member

FeodorFitsner commented Nov 23, 2016

Thanks, will take a look.

@jnferner

This comment has been minimized.

Show comment
Hide comment
@jnferner

jnferner Nov 23, 2016

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

jnferner commented Nov 23, 2016

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

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 24, 2016

Member

@georgeduckett, @SirRade - added

Member

FeodorFitsner commented Nov 24, 2016

@georgeduckett, @SirRade - added

@georgeduckett

This comment has been minimized.

Show comment
Hide comment
@georgeduckett

georgeduckett Nov 24, 2016

@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?

georgeduckett commented Nov 24, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 24, 2016

Member

Add this to project's appveyor.yml:

image: Visual Studio 2017 RC
Member

FeodorFitsner commented Nov 24, 2016

Add this to project's appveyor.yml:

image: Visual Studio 2017 RC
@georgeduckett

This comment has been minimized.

Show comment
Hide comment
@georgeduckett

georgeduckett Nov 24, 2016

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

georgeduckett commented Nov 24, 2016

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

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 24, 2016

Member

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

Member

FeodorFitsner commented Nov 24, 2016

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

@georgeduckett

This comment has been minimized.

Show comment
Hide comment
@georgeduckett

georgeduckett Nov 24, 2016

Ahh ok, thanks.

georgeduckett commented Nov 24, 2016

Ahh ok, thanks.

@TcT2k

This comment has been minimized.

Show comment
Hide comment
@TcT2k

TcT2k Nov 24, 2016

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

TcT2k commented Nov 24, 2016

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

@jnferner

This comment has been minimized.

Show comment
Hide comment
@jnferner

jnferner Nov 24, 2016

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

jnferner commented Nov 24, 2016

@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

This comment has been minimized.

Show comment
Hide comment
@caitchison

caitchison Nov 24, 2016

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

caitchison commented Nov 24, 2016

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

@matthargett

This comment has been minimized.

Show comment
Hide comment
@matthargett

matthargett Nov 24, 2016

Same here. Account name is matthargett. I'd love to try the Windows Server 2016 beta as well.

matthargett commented Nov 24, 2016

Same here. Account name is matthargett. I'd love to try the Windows Server 2016 beta as well.

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner
Member

FeodorFitsner commented Nov 24, 2016

@TcT2k, @caitchison, @matthargett - image added

@TcT2k

This comment has been minimized.

Show comment
Hide comment
@TcT2k

TcT2k Nov 24, 2016

@FeodorFitsner Thank you, it works for me, see my build here

I would be nice if you could include an updated CMake in the image. The current release 3.7.0 is not yet compatible with VS 2017 RC but the current nightlies are.

TcT2k commented Nov 24, 2016

@FeodorFitsner Thank you, it works for me, see my build here

I would be nice if you could include an updated CMake in the image. The current release 3.7.0 is not yet compatible with VS 2017 RC but the current nightlies are.

@djanosik

This comment has been minimized.

Show comment
Hide comment
@djanosik

djanosik Nov 24, 2016

djanosik - thank you!

djanosik commented Nov 24, 2016

djanosik - thank you!

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner
Member

FeodorFitsner commented Nov 24, 2016

@djanosik - done

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 24, 2016

Member

@TcT2k this is the script we use for updating CMake on build workers. You can adopt it for installing CMake nightly builds:

$cmakeUninstallPath = "${env:ProgramFiles(x86)}\CMake\Uninstall.exe"
if([IO.File]::Exists($cmakeUninstallPath)) {
    Write-Host "Uninstalling previous CMake ..." -ForegroundColor Cyan
    # uninstall existent
    "`"$cmakeUninstallPath`" /S" | out-file ".\uninstall-cmake.cmd" -Encoding ASCII
    & .\uninstall-cmake.cmd
    del .\uninstall-cmake.cmd
    Start-Sleep -s 5
}

Write-Host "Installing CMake 3.6.2 ..." -ForegroundColor Cyan
$msiPath = "$($env:TEMP)\cmake-3.6.2-win32-x86.msi"

Write-Host "Downloading..."
(New-Object Net.WebClient).DownloadFile('https://cmake.org/files/v3.6/cmake-3.6.2-win32-x86.msi', $msiPath)

Write-Host "Installing..."
cmd /c start /wait msiexec /i $msiPath /quiet
del $msiPath

Write-Host "CMake 3.6.2 installed" -ForegroundColor Green
Member

FeodorFitsner commented Nov 24, 2016

@TcT2k this is the script we use for updating CMake on build workers. You can adopt it for installing CMake nightly builds:

$cmakeUninstallPath = "${env:ProgramFiles(x86)}\CMake\Uninstall.exe"
if([IO.File]::Exists($cmakeUninstallPath)) {
    Write-Host "Uninstalling previous CMake ..." -ForegroundColor Cyan
    # uninstall existent
    "`"$cmakeUninstallPath`" /S" | out-file ".\uninstall-cmake.cmd" -Encoding ASCII
    & .\uninstall-cmake.cmd
    del .\uninstall-cmake.cmd
    Start-Sleep -s 5
}

Write-Host "Installing CMake 3.6.2 ..." -ForegroundColor Cyan
$msiPath = "$($env:TEMP)\cmake-3.6.2-win32-x86.msi"

Write-Host "Downloading..."
(New-Object Net.WebClient).DownloadFile('https://cmake.org/files/v3.6/cmake-3.6.2-win32-x86.msi', $msiPath)

Write-Host "Installing..."
cmd /c start /wait msiexec /i $msiPath /quiet
del $msiPath

Write-Host "CMake 3.6.2 installed" -ForegroundColor Green
@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Nov 24, 2016

Member

@ig-sinicyn, @madskristensen - we've fixed AppVeyor logger issue with VS 2017. Please give it another try and let us know how that worked.

Member

FeodorFitsner commented Nov 24, 2016

@ig-sinicyn, @madskristensen - we've fixed AppVeyor logger issue with VS 2017. Please give it another try and let us know how that worked.

@ig-sinicyn

This comment has been minimized.

Show comment
Hide comment
@ig-sinicyn

ig-sinicyn Nov 24, 2016

It works, thanks!

ig-sinicyn commented Nov 24, 2016

It works, thanks!

@ig-sinicyn

This comment has been minimized.

Show comment
Hide comment
@ig-sinicyn

ig-sinicyn Nov 25, 2016

@FeodorFitsner can you add my account too?

Need to do some A-B testing on our project:)

ig-sinicyn commented Nov 25, 2016

@FeodorFitsner can you add my account too?

Need to do some A-B testing on our project:)

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner
Member

FeodorFitsner commented Nov 25, 2016

@ig-sinicyn - added

@onovotny

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Mar 10, 2017

Member

@seburgi it's GCE Central US region.

Member

FeodorFitsner commented Mar 10, 2017

@seburgi it's GCE Central US region.

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Mar 11, 2017

Member

Visual Studio 2017 image has been updated:

  • Visual Studio Community 2015 with Update 3 installed
  • WiX 3.11 RC
  • PostgreSQL 9.5
  • MySQL 5.7
  • MongoDB 3.5
  • docker-composer
Member

FeodorFitsner commented Mar 11, 2017

Visual Studio 2017 image has been updated:

  • Visual Studio Community 2015 with Update 3 installed
  • WiX 3.11 RC
  • PostgreSQL 9.5
  • MySQL 5.7
  • MongoDB 3.5
  • docker-composer
@onovotny

This comment has been minimized.

Show comment
Hide comment
@onovotny

onovotny Mar 11, 2017

@FeodorFitsner Thank you so much!!!! Are you going to be at BUILD in May? I owe you a 🍺

onovotny commented Mar 11, 2017

@FeodorFitsner Thank you so much!!!! Are you going to be at BUILD in May? I owe you a 🍺

@fabiocav

This comment has been minimized.

Show comment
Hide comment
@fabiocav

fabiocav Mar 11, 2017

@FeodorFitsner thank you for the hard work on this! Moving things over to take advantage of what you've done right now.

fabiocav commented Mar 11, 2017

@FeodorFitsner thank you for the hard work on this! Moving things over to take advantage of what you've done right now.

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Mar 11, 2017

Member

@onovotny I'd love to, but we are so busy right now with so many things :)

Member

FeodorFitsner commented Mar 11, 2017

@onovotny I'd love to, but we are so busy right now with so many things :)

@FeodorFitsner

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner
Member

FeodorFitsner commented Mar 11, 2017

We've updated the page with pre-installed software: https://www.appveyor.com/docs/build-environment/#pre-installed-software

@csmager

This comment has been minimized.

Show comment
Hide comment
@csmager

csmager Mar 11, 2017

@FeodorFitsner thanks! I'm still hitting issues with WiX:

The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

Did you also install the VSIX extension into VS 2017?

csmager commented Mar 11, 2017

@FeodorFitsner thanks! I'm still hitting issues with WiX:

The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\WiX\v3.x\Wix.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

Did you also install the VSIX extension into VS 2017?

@kzu

This comment has been minimized.

Show comment
Hide comment
@kzu

kzu Mar 11, 2017

kzu commented Mar 11, 2017

@csmager

This comment has been minimized.

Show comment
Hide comment
@csmager

csmager Mar 11, 2017

@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.

csmager commented Mar 11, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@kzu

kzu Mar 11, 2017

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

kzu commented Mar 11, 2017

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

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Mar 12, 2017

Member

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

Member

FeodorFitsner commented Mar 12, 2017

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

@litichevskiydv

This comment has been minimized.

Show comment
Hide comment
@litichevskiydv

litichevskiydv Mar 12, 2017

@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.

litichevskiydv commented Mar 12, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@bhagvan

bhagvan Mar 12, 2017

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

bhagvan commented Mar 12, 2017

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

@csmager

This comment has been minimized.

Show comment
Hide comment
@csmager

csmager Mar 12, 2017

@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.

csmager commented Mar 12, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@roji

roji Mar 12, 2017

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

roji commented Mar 12, 2017

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

@bhagvan

This comment has been minimized.

Show comment
Hide comment
@bhagvan

bhagvan Mar 12, 2017

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

bhagvan commented Mar 12, 2017

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

@jbogard

This comment has been minimized.

Show comment
Hide comment
@jbogard

jbogard Mar 13, 2017

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

jbogard commented Mar 13, 2017

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

@JSkimming

This comment has been minimized.

Show comment
Hide comment
@JSkimming

JSkimming Mar 13, 2017

@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

JSkimming commented Mar 13, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Mar 14, 2017

Member

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.

Member

FeodorFitsner commented Mar 14, 2017

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

This comment has been minimized.

Show comment
Hide comment
@seburgi

seburgi Mar 15, 2017

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?

seburgi commented Mar 15, 2017

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

This comment has been minimized.

Show comment
Hide comment
@onqtam

onqtam Mar 15, 2017

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?

onqtam commented Mar 15, 2017

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

This comment has been minimized.

Show comment
Hide comment
@micbou

micbou Mar 15, 2017

@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

micbou commented Mar 15, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@onqtam

onqtam Mar 15, 2017

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

onqtam commented Mar 15, 2017

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

@mcintyre321

This comment has been minimized.

Show comment
Hide comment
@mcintyre321

mcintyre321 Mar 18, 2017

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

mcintyre321 commented Mar 18, 2017

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

This comment has been minimized.

Show comment
Hide comment
@jbogard

jbogard Mar 18, 2017

jbogard commented Mar 18, 2017

@JSkimming

This comment has been minimized.

Show comment
Hide comment
@JSkimming

JSkimming Mar 18, 2017

@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.

JSkimming commented Mar 18, 2017

@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

This comment has been minimized.

Show comment
Hide comment
@mcintyre321

mcintyre321 Mar 18, 2017

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
}

mcintyre321 commented Mar 18, 2017

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

This comment has been minimized.

Show comment
Hide comment
@FeodorFitsner

FeodorFitsner Mar 24, 2017

Member

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

Member

FeodorFitsner commented Mar 24, 2017

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment