|
#1
|
|||
|
|||
Is this a bug in "Custom Actions" or did I miss something?
Hi
I've just come across something odd. I've created a custom action and in the .Action file used the tab key to lay out the XML nicely and make it easy to read (... and adhere to our corporate standards which state that each "begin" and "end" tag statement and the data they enclose have to be on seperate lines, indented.). When I registered the action the data in the ActionComponent registry key included the tab characters, so that the build failed with an "Invalid class string" error. Took me a day to get to the bottom of that. Has anyone else seen this behaviour or was I just unlucky? Sam |
#2
|
|||
|
|||
You are the first to report this problem. I don't think that it's a bug (the XML standard [1] doesn't specify whether whitespace should or should not be considered significant to an application). I do apologize that this caused some difficulty. We'll consider changing this behavior, since it does seem reasonable for whitespace to be ignored in most cases.
[1] http://www.w3.org/TR/REC-xml/#sec-white-space |
|
|