Branching Strategies for EPiServer Commerce solutions

There are just to many physical file path dependencies in EPiServer Commerce, and of course they are spread out in vaiours locations (read different config files ...).

So branching a solution is just a pain, or is it?

Anyone got a nice, simple and clean approach?

#79272
Dec 12, 2013 11:16
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.