Many people will want to use nuget to deploy files that can potentially be locked
-assemblies containing MSBuild tasks
-assemblies containing designer files
Is it possible to have nuget detect locked files and recommend a restart of VS? Similar to the approach taken by visual studio extensions.
Comments: Have you guys considered shadow-copying the contents of the package and telling VS to reference that instead of the copy inside the packages folder? It should prevent the update process from failing, so the project wont be left in an inconsistent state. If the actual process of creating the shadow copy fails, you could inform the user that a restart of VS is required for the new version of package to take effect. The package restore process might be a feasible place create/refresh the shadows. Since creating copies of all the packages in a project with a dozen or more dependencies could severely impact performance, it'd probably be best to add a __requiresShadowCopy__ flag to the nuspec file so packages can opt in. Anyway, I'll leave the details up to the experts, hope the idea helps. p.s. Thanks for all the great work, I can't even remember how to manage dependencies without nuget ;)
-assemblies containing MSBuild tasks
-assemblies containing designer files
Is it possible to have nuget detect locked files and recommend a restart of VS? Similar to the approach taken by visual studio extensions.
Comments: Have you guys considered shadow-copying the contents of the package and telling VS to reference that instead of the copy inside the packages folder? It should prevent the update process from failing, so the project wont be left in an inconsistent state. If the actual process of creating the shadow copy fails, you could inform the user that a restart of VS is required for the new version of package to take effect. The package restore process might be a feasible place create/refresh the shadows. Since creating copies of all the packages in a project with a dozen or more dependencies could severely impact performance, it'd probably be best to add a __requiresShadowCopy__ flag to the nuspec file so packages can opt in. Anyway, I'll leave the details up to the experts, hope the idea helps. p.s. Thanks for all the great work, I can't even remember how to manage dependencies without nuget ;)