BuildAssembler Error with XPath Reflection File Filter Plug-In

Topics: Developer Forum, User Forum
Jun 23, 2014 at 4:57 PM
Jun 24, 2014 at 7:34 PM
Edited Jun 24, 2014 at 7:34 PM
Some of the build steps and processing were rearranged. The plug-in probably needs to be moved to run a little earlier before the BuildAssembler manifest file is generated.

Jun 26, 2014 at 5:23 AM
Thanks Eric, I have changed the order and it works. ExecutionPoints collection in plug-in implementation is hard coded. Is there any other way we can change when to run without rebuilding? if not can we expect this change in next builds?
Jun 26, 2014 at 3:01 PM
Plug-ins have fixed execution points and they rarely if ever change so there's really no need to make them dynamic so they are hard coded. This was caused by a case of moving some of the build steps around to better fit with some new feature implementations. It'll be fixed in the next release.