I am not sure if I entirely understand what you want to do:
- You want to import multiple artifacts (i.e. content types) from one specific site by selecting all of them in one import step (meaning on SPSF recipe)?
- Or do you want to import the settings for these artifacts from a table(i.e. an excel or CSV) to be able to create the neccesary code in one step instead of executing the recipe several times?
Plz confirm if I understand you right. Anyway either one is not possible at the moment with SPSF, but it would be possible as far as I know.
The best way would be if you post your request in the issue tracker as a new feature, so that others are able to vote for it.
Nevertheless, apart from bugfixes, currently all our efforts are focused on supporting VS2010.
1. In general, yes it is possible to edit artifacts through recipes. For example when you create a "Empty Feature" and afterward lets say a "Content Type" from which you choose the feature. The ContentTypes.xml is referenced automatically
in the feature.xml. The same would be possible to realize your idea modifiying the feature dependencies later after feature creation. One would have to retrieve the FeatureDependencies XML part of the feature.xml, modify it and update the feature.xml.
As the recipies can execute any programming that wouldn't be too hard i guess.
As mentioned above you can add it as a feature request in the issue tracker, or (even more appreciated :-) ) you could try to implement it, and share your code! which leads to
2. Yes you can create new recipes with the Guidance Automation Toolkit (GTK see download link in documentation tab). You can reference the SteriaMummert.SharePointSoftwareFactory.Base.dll an utilitze all wizard addons and actions we have created for
SPSF. Your package can be deployed separatly to SPSF or we can include your recipes in one of our releases. To get a start, have a look at the source code for SPSF and make yourself familiar with the recipes and their coresponding code templates. If you need
further assitance plz start a new thread and we will try to support your efforts as good as we can!
3. In theory, yes, you could add new recipes to an existing SPSF installation, but you could not be sure if the installed version is compatible with your "service pack" if you just copy the files into the installation directory. Especially if you
have to update existing files like the RecipeBindings.xml. So the much better approach would be the way you described in 2. Just develop your own recipe package which can be installed along with SPSF. Another approach would be that you could add your new or
modified recipes to the source code you can download here and provide us the package. We can then diff the changes you made and after thorough testing integrate it in one of the main releases of SPSF.
Thank you for your interest and feedback!
Expect more great things to come :-)