Wondering if sharing a Shared Project between different solutions, is the wrong approach?

Question

Some days ago I asked in this forum How to use a SharedProject between different solutions? And @Alex Li-MSFT answered it (thanks again, Alex!) But now I'm wondering if that's the wrong approach. Unless I'm misunderstanding the answer, it seems to me that the solutions referred to by Alex would bring the code from the original Visual Studio solution where the shared project was originally written, into the other Visual Studio solutions. Or if it didn't make a copy of the original shared project into other Visual Studio solutions, it would at least demand that every other developer on the team that uses the shared project, also have the original solution with the original shared project, on their development system. How else would all the other Visual Studio solutions that reference the shared project from the original solution, unless they were present on each system?

If I'm understanding it correctly, then I don't really think I've realized the benefit I'm trying to with a shared project in a Visual Studio solution and having other Visual Studio solutions with the same shared project in it, so that editing the shared project in any of the other solutions, then checking in the changes (push the changes) would allow all developers to update their copies by doing a get latest (pull). That is what I'm trying to realize, ultimately. I'm beginning to think that my approach simply will fall short of my goal. Am I correct about that?

Answer 1

Yes, you can.

But be sure to leave an eye-catching message to any other developers, tell them some else solution has also used this project, and tell them not to change anything that has been written before thoroughly understanding the project.