# package-development


01/15/2022, 2:44 PM
I think it's a false premise. If required, should be able to be switched on, but not the default position. Must make pure front end devs dealing with thousands of tiny dependency files mad with all the stuff they'd have to download on every build. Once you've got it, you've got it. Git for everything else. Opinions are my own of course and subject to persuasion, lol


01/15/2022, 8:50 PM
Work around we use.. in the project.csproj
$(MSBuildThisFileDirectory)..\ExternalDependencies\App_Plugins\**\*.* '$(ProjectDir)\App_Plugins\%(RecursiveDir)%(Filename)%(Extension)')" SkipUnchangedFiles="true" /> '$(OutputPath)\App_Plugins\%(RecursiveDir)%(Filename)%(Extension)')" SkipUnchangedFiles="true" /> '$(PublishDir)\App_Plugins\%(RecursiveDir)%(Filename)%(Extension)')" SkipUnchangedFiles="true" />
and then have a folder of files one level up, ours is called
in the above.. then if you replicate the app_plugins directory structure and place the file/files you want to be replaced after the nuget restore occurs.
works for build and publish directives. 😉
so in your case.. /ExternalDependancies/App_Plugins/TheDashboard/Lang/en-Us.xml would replace the nuget restored immutable file in the build/publish cycle.