Apr 18, 2011 at 1:46 AM
Edited Apr 18, 2011 at 1:47 AM
First of all, you did a great job with this release. However, there are still some things that need polishing.
I have noticed, that some of the fields that define optional properties of objects in recipe wizards are in fact required (you can't continue until you enter something there). Example: Recipe for Site Column, Description field on Site coulmn type page. It
would be nice if clearing their value would result in omiting property in resulting xml (since prop is optional, it won't affect the deployment).
Next thing - list definition recipe. After checking, whether template should be hidden, the resulting xml comes with property Hidden="True", which does not always work. In order for this to work property must be Hidden="TRUE". I would recommend to change
all boolean values in xmls to uppercase, since this is not the only case in SP xml definitions, when "True" value is not working and "TRUE" is.
I would also suggest adding recipe for Package. I know that packaging is done after rebuid, but it would be nice to have an option to generate wsp right away (when all you did was correct a typo in xml definition).
Next nice to have this would be adding SharePoint schemas (wss.xsd etc.) to xml files generated by recipies. It would make any manual modifications much easier.
Finally, it would be good to have a recipe that checks feature folder and refreshes ElementManifests in feature.xml. When you change folder name for feature element (ex. site column), you need to remember to manually modify feature.xml as well. Rebuilding
feature.xml would simplify the matter and help avoid possible typos with synchronizing feature.xml contents.