Tips & Tricks for SolutionPackager RRS feed

  • Question

  • After years of CRM development, I am finally looking into the SolutionPackager tool to see how we can use it with (or to replace) our development tooling. I'm wondering if others have found it to be useful, and how they have integrated it into their development processes.

    I know, for example, that because the solution export routinely includes minor unexpected changes(changedinversion or whatever nonsense is now in the customizations.xml), the ideal and beautiful goal of having only intended changes show up in diffs and end up in source control is more complicated than described. I'm looking for any other 'gotchas'. Also wondering how people have used sdkmessageprocessingsteps with this tool and source control? For me, ideally, it would be great if a developer could add a new plugin step to the solution *without* having to actually export the solution and unpack it, and perhaps my plugin registration tool could manually create these xml files in a place for the solution packager to pack in a build. Has anyone else gone down that path?

    Thanks for anyone with some 'been there, done that' knowledge!

    Friday, March 21, 2014 7:08 PM