Best practice to keep external DLL's in a solution updated for shared solutions?
Posted: Mon Sep 13, 2021 3:59 pm
In message https://www.xsharp.eu/forum/public-vo-v ... t=40#18499 Wolfgang wrote about using the NuGet manager or simply including a DLL:
"NuGet can do much more..."
Now I wonder what the best practice is. A programmer working on the .Net project, including X# conversion at my customer, created on (C#) program which included one NuGet package and a couple of Syncfusion DLL's, also retrieved from NuGet.
I cloned the project from BitBucket and most (or all) of these DLL's showed a faulty reference (yellow triangle icon). Nevertheless the NuGet Packages all seemed included. We removed them and tried to reinstall them, hoping that future pulls would keep the NuGet feeded DLL's at least in sync, but again a Syncfusion package showed as Installed while it was not included in the References.
My idea would be this:
1 For X# and related DLL's I would browse to the installation directory and pick the required DLL's manually, e.g. from C:Program Files (x86)XSharpAssemblies.
2 For all other 3rd party DLL's, including those obtained via NuGet, I would use a directory C:DotNetDLLs and keep all DLL's there and browse there to include.
This is the same location for all the users (now 2, will be more). It does mean that when there's an update we actually want to use that there are one or more manual steps:
1 The updated DLL's should be replaced in everyone's directories where the browse originally pointed to
2 Right mouse click in the project, Unload project, followed by Reload project with dependencies.
This seems to do the job properly without half or non working NuGet steps. Does this sound like a solid solution to keep everyone up to date? Or is there a better way?
Dick
"NuGet can do much more..."
Now I wonder what the best practice is. A programmer working on the .Net project, including X# conversion at my customer, created on (C#) program which included one NuGet package and a couple of Syncfusion DLL's, also retrieved from NuGet.
I cloned the project from BitBucket and most (or all) of these DLL's showed a faulty reference (yellow triangle icon). Nevertheless the NuGet Packages all seemed included. We removed them and tried to reinstall them, hoping that future pulls would keep the NuGet feeded DLL's at least in sync, but again a Syncfusion package showed as Installed while it was not included in the References.
My idea would be this:
1 For X# and related DLL's I would browse to the installation directory and pick the required DLL's manually, e.g. from C:Program Files (x86)XSharpAssemblies.
2 For all other 3rd party DLL's, including those obtained via NuGet, I would use a directory C:DotNetDLLs and keep all DLL's there and browse there to include.
This is the same location for all the users (now 2, will be more). It does mean that when there's an update we actually want to use that there are one or more manual steps:
1 The updated DLL's should be replaced in everyone's directories where the browse originally pointed to
2 Right mouse click in the project, Unload project, followed by Reload project with dependencies.
This seems to do the job properly without half or non working NuGet steps. Does this sound like a solid solution to keep everyone up to date? Or is there a better way?
Dick