Hi @tjackson welcome to the community.
Unfortunately that is not something we currently support, for quite few reasons
- Integrating with .NET / MSBuild world : we benefit from this Prepare analysis configuration to install some build targets : though it might be your case, that’s something to consider
- We are relying on paths for computing some metrics (ie coverage), this is not easy to guess on a user’s system if this has changed from the original place file they have been analyzed vs the place they were on the filesystem
- We’re also using environment variable to kind of communicate between both tasks, again we don’t expect to pass it through multiple jobs as it can have impact on the value itself.
That makes it quite challenging for us, though i’m not saying we will not support it in the future.
Hope that clarifies
Thanks !