VS 2017 Sharing Assemblies Across Solutions RRS feed

  • Question

  • We have a team of 6 developers.  OS used for development varies from windows 7 32 bit to windows 10 64 bit.

    The source control is git.  The development is in c#. 

    Currently, a common set of assemblies are used by 2 solutions.   One solution is a web application.  Another solution is a windows service.  The assemblies are build from a solution and copied to a designated location of solutions consuming them.

    We are experiencing 2 problems with it.  1) Consuming application may not end up with the latest common assemblies.  For instance developer forgot to copy an assembly to a designated location within a solution.  2) If a common assembly was built on another os platform,  there might be problems compiling the solutions referencing these assemblies.

    What is the proper approach to deal with this problem?

    Thanks in advance

    Friday, May 24, 2019 5:48 AM

All replies

  • Hi rgelfand,

    Welcome to the MSDN forum.

    Per your description, you can try to make those sharing assemblies as the NuGet package. Please follow this doc: Creating NuGet packages

    No matter what your package does or what code it contains, you use nuget.exe to package that functionality into a component that can be shared with and used by any number of other developers.

    Best regards,


    MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact

    Friday, May 24, 2019 9:17 AM