SCF 1.0 Next release

Dec 12, 2008 at 8:38 PM
What do you want to be included in the next release?
Mar 5, 2009 at 12:45 PM
Thanks you very much for sharing this nice piece of code.
Here are my first encouragements ...

1) Is resources declaration already allowed?
... for example instead of "Pages" directory would be "$Resources:cmscore,List_Pages_UrlName;"
2) Could be publishing took in accout too? 
... it will need to extend at least FileToProvision command by sometnig like ProvisioningPath (or just Publishing="TRUE"/"FALSE")


FileToProvision FileName="default.aspx" NavBarHome="true" ProvisioningPath="Pages" />


... Sample project with activated publishing features would be great to have

3) How is possible to provision more than just one file (default.aspx)?

4) Posibility to set Variation Root would be nice to have?
... bellow is the code for / as the most top root it would be:


SPSite site = (SPSite)properties.Feature.Parent;



SPWeb web = (SPWeb)site.RootWeb;



SPList variationSettings = web.Lists[new Guid(web.AllProperties["_VarRelationshipsListId"].ToString())];



SPListItem item;



if (variationSettings.ItemCount == 0)



item = variationSettings.Items.Add();


"GroupID"] = "F68A02C8-2DCC-4894-B67D-BBAED5A066F9";



"Deleted"] = false;










item = variationSettings.Items[0];



"ObjectID"] = web.Url + "/";





I'm looking forward to see this project in beta soon :-)
Mar 5, 2009 at 7:31 PM

1. That should work.

2. We are thinking about/looking into publishing, but it might require a bit more than just this... However, just adding a path parameter for fileprovisioning should be easy enough.

3. Sure, add as many as you want:
<FileToProvision FileName="page1.aspx" NavBarHome="false" />
<FileToProvision FileName="page2.aspx" NavBarHome="false"  />

4. Good idea. Would you like to contribute to the next release? 

Mar 6, 2009 at 9:24 AM

2. I'm currently working on it. Could you give me some guide lines what all must be resolved for Publishing, please. Or do you have a new version in your drawer already?
3. If there could be more pages, on which page will be the Web Parts added. If  I understand well to your CodeBehind, it is by order. OK, great. 
4. I'll be glad to participate. At least as a tester of Publishing and Variations, because I'm not senior CSharp developement.

5. Unfortunately I don't know about any SharePoint parameter like VariationOnly which could be used instead of RootOnly or SubSiteOnly. Because in my current project (and I guess in most of typical variation cases) after introducing variation should behave variation webs behave like roots of particular language.

Trace Logging is working fine, thanks for kick.