In VS 2008 you have to do most of the skeleton work yourself, but in VS 2010 it’s all setup for you.Once VS finishes processing, you will have a solution structure similar to the below image.
- Mak dating sek
- consolidating multiple itunes libraries hard drive
- jason cook and kirsten storms dating
- Chat without id with girl
For now we’ll use the quick-and-dirty ‘code transformation’. This class also has a single method Save File To Library that takes the site url, library name, html content and file name as parameters.
I mentioned earlier also how easy it is to develop for SP 2010 using VS 2010.
In this article we’ll continue where we left off and see how we can add a hook in Share Point and enhance the content creation and approval process to make it more valuable to end users.
Policy documents, Functional Specs, Technical Specs, Time Sheets, Work-Orders etc.
It gives you two deployment options for your feature, one is Sandboxed and other is Farm deployment.
I selected Sandboxed because I want the feature to be limited to the site collection where I am publishing only.
Step 3: As seen below we’ve selected our “Type of event receiver” to be “List Item Events” and “Event Source” to be the “Pages Library” because that’s the library use has the pages that have our custom content type.
Step 4: Click Finish and wait for Visual Studio to do the skeleton work for you.
I have renamed it to Custom Content Publish Feature.
Double click on it bring up the Feature properties editor. This class will encapsulate our ‘logic’ to generate HTML from our list item.
Custom Content types help us with defining the data-structure while layouts help us define the presentation.