Meir Blachman

this project would basically be: ```xml net8 ``` then just start adding classes (see the examples)

these libraries are deprecated now, see https://github.com/dotnet/roslyn-sdk/tree/main/src/Microsoft.CodeAnalysis.Testing#obsolete-packages

@SimonCropp that was done back in https://github.com/dotnet/roslyn-sdk/pull/1162 @sharwell / @333fred - these packages are not marked as obsolete on nuget.org. Was this part missed?

@premun to be sure I understand - the syntax we want to have here is ```cs new Stage("Example") { // DisplayName is Conditioned DisplayName = If.IsBranch("main") .Value("job_1") .Else .Value("job_2") }...

@flcdrg interesting approach! I think the only property that might not be conditional is the `task` property which is the task identifier and I'm not sure about this. I think...

> [@Meir017](https://github.com/Meir017) [@flcdrg](https://github.com/flcdrg) this one I believe is now one of the largest shortcomings of the library at the moment. I wonder if refactoring the Yaml serialization logic of the...

I think generating something like this would work: ```yml steps: - powershell: | dotnet tool install ` Microsoft.DotNet.XHarness.CLI ` --global ` --add-source https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-eng/nuget/v3/index.json ` --version "1.0.0-prerelease*" ` ``` I think...

getting the current step name to use when `isOutput=true` looks tricky here. I was thinking of something like: ```cs public class AzureDevopsCommands(AzureDevOpsTask task) { public string SetVariable(string name, string value,...

maybe as part of the msbuild property `FailIfChanged` or by introducing a new `ValidateGeneratedPipelines` msbuild property?

The idea would be to use `$(System.AccessToken)` - https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml#systemaccesstoken