Idea - Remove Unused Dependencies When Publishing Solution

Back to Ideas

Follow Idea

Mustafa Emad Shaker

Remove Unused Dependencies When Publishing Solution

New

Service Center

One of the purposes of publishing a solution, is to refresh all modules in it, and reflect a change of an upgrade.

What I propose, is to remove unused dependencies between the defined modules in the solution.

I recommend for it to a configurable option. But it would be helpful especially in big projects, where the architecture is big and complicated.

Also, it could be a helpful option before checking the architecture in Discovery. Before the check we have all modules refreshed, and all unnecessary links broken.

07 Jan

Daniël Kuhlmann

MVP

There about 15 to 20 other similar ideas on improving the auto removal of dependencies, dating back 15 years. None of them will be implemented, is my guess, I created one myself wit 75 likes, also that one is ignored.

08 Jan

Mustafa Emad Shaker

Indeed @Daniël Kuhlmann, I did notice that many community members recommended it.

Instead of replying to an existing idea, I hoped that by posting a new one would gain reach to raise the point again.

08 Jan

Mustafa Emad Shaker

Also, I posted the idea to demonstrate my point of view on how and why it should done.

08 Jan

Borislav Shumarov PhD

Champion

Maybe not by publsishing, but definitely by Deployment from one environment to another.

If optional checkbox during the deployment too cumbersome, just mandatory in the background would suffice

20 Jan

Mustafa Emad Shaker

I totally agree with you @Borislav Shumarov PhD, there is not point of keeping unnecessary links between module when deploying between environments.

However, having the option to do so on the development environment, can be helpful.

20 Jan