You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to be able to create transforms that are specific to a developer.
The idea would be to include a transform that typically would not be committed to source control and could be used by a developer to customize the transform output on their own machine.
I often make changes to app.Debug.config for developing and testing specific features of my application, or to transform the resulting configuration to include paths, certificate lookups, or other things that are specific to my development environment. On occasion, I will accidentally commit these changes to source control. I then have to revert those changes before they impact other developers. If there existed a mechanism to create a transform that ran after the configuration named transforms, I could keep my personal configuration changes out of the mix.
I suggest handling something like app.user.config or even app.machine.config that would be applied after app.Debug.config or app.Release.config. This concept could (and should) of course be extended to web configurations and other transforms.
The text was updated successfully, but these errors were encountered:
It would be nice to be able to create transforms that are specific to a developer.
The idea would be to include a transform that typically would not be committed to source control and could be used by a developer to customize the transform output on their own machine.
I often make changes to app.Debug.config for developing and testing specific features of my application, or to transform the resulting configuration to include paths, certificate lookups, or other things that are specific to my development environment. On occasion, I will accidentally commit these changes to source control. I then have to revert those changes before they impact other developers. If there existed a mechanism to create a transform that ran after the configuration named transforms, I could keep my personal configuration changes out of the mix.
I suggest handling something like app.user.config or even app.machine.config that would be applied after app.Debug.config or app.Release.config. This concept could (and should) of course be extended to web configurations and other transforms.
The text was updated successfully, but these errors were encountered: