Always build ref pack even in servicing releases

[safern]

This was already done in release/6.0 branch, this is just making sure we have it in main so that in future servicing branches this is already taken care of.

[ghost]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[jkoritzinsky]

If similar work has been completed in dotnet/windowsdesktop, we should consider removing the ProjectServicingConfiguration feature from the SharedFramework SDK as there will be no users of it.

[ghost]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This was already done in release/6.0 branch, this is just making sure we have it in main so that in future servicing branches this is already taken care of.

Author:	safern
Assignees:	safern
Labels:	area-Infrastructure
Milestone:	-

[safern]

If similar work has been completed in dotnet/windowsdesktop, we should consider removing the ProjectServicingConfiguration feature from the SharedFramework SDK as there will be no users of it.

@RussKie can you confirm this was the case?

[RussKie]

Yes, addressed in dotnet/windowsdesktop#2571.
And dotnet/windowsdesktop#2633.

[akoeplinger]

If similar work has been completed in dotnet/windowsdesktop, we should consider removing the ProjectServicingConfiguration feature from the SharedFramework SDK as there will be no users of it.

@jkoritzinsky it looks like it is still used by https://github.com/dotnet/deployment-tools/blob/097b01d7091fdf281144b4e22a5ff6245ea7cf04/eng/Versions.props#L46-L50

[jkoritzinsky]

That looks like it was copied straight from the old dotnet/core-setup repo and might be dead, but I’ll make sure before doing anything.