Feature: use Azure Pipelines for building

[StefH]

#210

[kaylangan]

I'm a Program Manager on Azure Pipelines. Let me know if you have any suggestions or questions. I'm happy to help!

[StefH]

@kaylangan
Thanks for your help.

My plan was to implement the same steps as I did on https://github.com/WireMock-Net/WireMock.Net/tree/Response_BodyData

For this project this means

• remove appveyor CI
• add .yml file and make sure that tests run
• integrate sonarcloud
• publish to myget

Do you maybe have some hints or tips when integrating with Azure Pipelines?

[kaylangan]

Makes sense to me! It looks like you have a pretty good handle on how to get set up, based on what I see in the other project.

Also, this may be intentional, but your Azure DevOps project isn't public so I can't see the build results even though I can see the status in the checks section.

[StefH]

Some questions:

• can you tell me step by step how to make the build public?
• how to define multiple projects to build? I also asked that here Question about your article https://im5tu.io/article/2018/06/automated-builds-in-vsts-with-yml-build-definitions/ Im5tu/im5tu.github.io#1
• it seems that I cannot build net3.5 and uap10.0 with dotnet build? Or should I use msbuild with some workarounds?

[kaylangan]

1. can you tell me step by step how to make the build public?

Check out the docs on making a private project public.

2. how to define multiple projects to build? I also asked that here Im5tu/im5tu-hugo#1

You can use wildcards as you've done it here. We have a doc on more advanced file name patterns. Would this meet your needs?

3. it seems that I cannot build net3.5 and uap10.0 with dotnet build? Or should I use msbuild with some workarounds?

What's the error that you are getting? If you can get MSBuild to work, that's great. Otherwise, I'll have to check with one of my teammates.

[StefH]

@kaylangan

1. This does not work for me because my project / sourcecode is from GitHub. I only use the devops pipelines in Azure to build.

2. I solved it like:

variables:
  buildProjects: '**/src/**/+(System.Linq.Dynamic.Core|EntityFramework.DynamicLinq|Microsoft.EntityFrameworkCore.DynamicLinq).csproj'

3. I used a workaround to just excluded these two frameworks from the CI - build on Azure Pipelines like:

<PropertyGroup Condition=" '$(buildType)' == 'azure-pipelines-ci' ">
    <TargetFrameworks>net40;net45;net46;netstandard1.3;netstandard2.0</TargetFrameworks>
</PropertyGroup> 

[StefH]

3. Error message is like:

C:\Users\Stef\Documents\Github\System.Linq.Dynamic.Core\src\System.Linq.Dynamic.Core\System.Linq.Dynamic.Core.csproj : error MSB4057: The target "_GetRestoreSettingsPerFramework" does not exist in the project.
C:\Users\Stef\Documents\Github\System.Linq.Dynamic.Core\src\Microsoft.EntityFrameworkCore.DynamicLinq\Microsoft.EntityFrameworkCore.DynamicLinq.csproj : error MSB4057: The target "_GetRestoreSettingsPerFramework" does not exist in the project.

[kaylangan]

Azure DevOps projects include source control and pipelines so those steps should work to make your builds public. The reason I think your Azure Pipelines project is set to private is when I click to see the build results I get 401'd instead of seeing the logs.

[StefH]

Hello @kaylangan
I created a simple test project which shows the error when building net 3.5 (StefH/AzurePipelinesTest3#2)

This PR fails:
StefH/AzurePipelinesTest3#1