I don’t recommend this for several reasons.
- Revit updates have made the utopian ideal of a single package working for all supported Revit builds a non-starter. This will likely get worse with the next revit release due to the .net migration (all previous versions of Dynamo were written for a Revit application running .net 4.x, but the 2025 product line will be .net 6 or .net 8). While some packages are built to scale across builds (Bimorph), many are not (Archi-Lab) and as such you’ll need a different version for each.
- Loading packages off a network can cause issues with information security, as you are enabling execution of remote code; while this wouldn’t be intentionally done, it’s another gap in the defenses which your infosec team will eventually shore up breaking ALL the Dynamo work unless exceptions are made.
- Loading packages from a network location can cause significant delay in node search, graph opening, and startup (due to the same infosec stuff).
- Users can (and eventually will) put packages onto their own local disc, and eventually you’ll get duplicate packages with conflicting versions, which can cause loading to fail.
By copying from the network directory for each build to the local disc you circumvent each of these issues, and prevent situations where you can have the graphs running in either 2021 or 2024, but not both.