Flag to include not only the dependents, but also the dependencies

[BenjaBobs]

Our team uses dotnet-affected ( ❤️ ) to only built/test/deploy the affected projects in our monorepo.

However due to various small issues between the dotnet tools (build/test/publish) and traversal files, we output the affected projects as .txt, and use that to create a new affected.sln.
It turns out that not all properties (e.g. configuration) are passed properly to all built projects when building a solution file whose projects have dependencies that are not also in the solution file, see dotnet/sdk#25973.

For that reason we also manually construct an affected_with_dependencies.sln using dotnet list reference.

If dotnet-affected could do this with a flag it would greatly simplify (and probably speed up) our CI pipeline.

Thanks for your time and hard work so far.

[leonardochaia]

Hi @BenjaBobs, thanks for reaching out.

I think this should be easy to implement since we already have some code to generate Solution files for testing. However, we also use dotnet-affected to buld/test/publish against the resulting traversal SDK file.

due to various small issues between the dotnet tools (build/test/publish) and traversal files

Would you mind clarifying which are the small issues you guys are facing when using the traversal SDK project? curious to know cause this may be affecting other users of the tool as well.

Thank you,
Leo.

[BenjaBobs]

Yes sure!
It seems that I miss-remembered, and it was actually only dotnet format that didn't work with .proj files.
dotnet/sdk#42296

If build/test/publish all work with proj files, and properly propagate --configuration Release and --runtime linux-x64 and the likes, then it this might not even be necessary.

[leonardochaia]

Hi @BenjaBobs , I think it would be nice if dotnet format plays good citizen and supports .proj files. I will take a look to the dotnet format code and see if I can implement it.

If that does not work we can support outputting a solution in dotnet affected.