q. how can setup our config/transforms release management work in example way?
i'm trying release management work in way videos seem show. same build progressing through environments going through build --> dev/staging --> production.
it's making me step little , question way our configurations in visual studio solutions (and our git flow branch process). think way use configurations making things more difficult further down line build , release.
configurations
we use 2 default configurations, debug & release.
- we tend use debug build on our dev (contains dev database connection string & other app settings transforms). deploy 'dev'.
- then have release configuration production transforms in. deploy 'production'.
how can setup our config/transforms release management work in example way?
one option: build both configurations. publish both configurations artifacts in build.
in release definition, deploy appropriate configuration linked artifacts.
another option: don't compile-time configuration transforms , instead deployment-time configuration.
Comments
Post a Comment