You can continue using the approach you describe. Deploying in the GAC is not the preferred approach.
There are only 2 things that really matter: resolving the assemblies at compile time and loading the assemblies at runtime. As long as the assemblies can be located everything should be OK.
As you say NuGet does help in managing dependencies and ensuring that the latest (and/or correct) version of assemblies is being used as well as ensuring that the correct assemblies are used for the target platform (e.g. Silverlight). Also, the Enterprise Library
binaries path is managed automatically which enables the VS integrated config console to work seamlessly (you can always configure the path to wherever the assemblies are located).
Another option that might be interesting is setting up a local NuGet repository: see
Hosting Your Own NuGet Feeds
If you don't want to use NuGet you can always download the installation from the Download Center:
. Then you could run the install-packages.ps1 (which does use NuGet) script to download all of the assemblies into one folder. Note that this method will download the versions included in the
original release and does not include any updates that have been released more recently.
Enterprise Library support engineer