Consider migrating the src/redist/targets path to an arcade sdk for sdk based installers.

[AraHaan]

I feel like the work done here could be simplified and migrated on over to dotnet/arcade to make maintainability here far more easier.

Pros:

• easier to package any sdk to an installer/archive
• can be used by anyone outside of the foundation as well.
• can be configured more easily.

Cons:

• Might require a new sdk be added (or for an existing one to be updated) for this to arcade.

[marcpopMSFT]

Isn't the redist folder the majority of what the installer repo is for? Are you looking into the ability to create new installers that aren't the .NET SDK but other components? Do you have specific things in mind?

CC @richlander who is looking into some of our open source policies.

[AraHaan]

Yes, I am looking for the ability to create new sdk installers that are not the .NET SDK but are other components.

An example being an SDK that can pull in their own runtime / reference packs which are crossgen2'd and are not meant only for self contained situations (aka are meant to be framework dependent).

[richlander]

Can you describe your scenario a little more? That would help us understand why this direction is a good choice.

/cc @jkotas

[marcpopMSFT]

Old issue triage: No reply in a while so closing. Feel free to reactivate if still desired.