 Print
 Add To Favorites
 Email To Friend
 Rate This Article
|
Developing and Deploying a SharePoint Feature - Part 1
|
Published:
05 May 2008
|
Abstract
SharePoint 2007 has a number of new features over its predecessors. After examining the features of it, Steven demonstrates how to develop, package, deploy and enable a simple feature solution. He examines the required steps to build the solution and then delves deeper into the structure of the XML file being used, configuration of the install code and the relevant information to connect the functionality. |
 |
by Steven Barden
Feedback
|
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days):
30581/
77
|
|
|
|
| Introduction |
SharePoint 2007 is far more feature packed than SharePoint
2003, which is what Microsoft wanted to make sure of. They have also made
SharePoint 2007 even more extendable that 2003. This means that not only can
you immediately take advantage of the existing base of features, but you can
also develop your own features. For example, any WebPart that can be activated
is considered a feature. Any point of functionality that makes SharePoint more
useful, like base column types, is a feature. And any piece of functionality
that you can create in SharePoint that can be used by SharePoint or other users
is called a feature. So when you really look at it, Microsoft picked a pretty
good name … which is what confused me at first because a feature is just what
it sounds like… and I did not expect that.
|
|
|
|
|
Article Feedback
User Comments
Title:
Developing and Deploying a SharePoint Feature - Part 1
Name:
Swati Agarwal
Date:
6/28/2010 3:49:36 AM
Comment:
Please make your explanations simple man!!! It is like reading a psycology book :(
|
Title:
Create Custom SharePoint Features, it is simple.
Name:
sara
Date:
10/1/2009 2:01:37 AM
Comment:
Nice !!!!!!!!
Try this too,
http://sarangasl.blogspot.com/2009/09/in-this-article-im-going-to-describe.html
|
Title:
Configuring install code
Name:
Sohaib Khan
Date:
2/19/2009 1:45:46 AM
Comment:
Basically, I am doing this first time so i am not familiar with the syntax of PostBuildEvent.
Thanks in advance - Steven.
|
Title:
Configuring install code
Name:
Sohaib Khan
Date:
2/19/2009 1:44:36 AM
Comment:
and this one as well
Call ($ProjectDir)\Import.cmd
|
Title:
Configuring install code
Name:
Sohaib Khan
Date:
2/19/2009 1:41:42 AM
Comment:
I also tried this command
($ProjectDir)\Import.cmd
|
Title:
Configuring the install code
Name:
Sohaib Khan
Date:
2/19/2009 1:39:30 AM
Comment:
I am trying this command
set CONFIGURATION=$(Configuration) && ($ProjectDir)\Import.cmd
|
Title:
Configuring the Install Code
Name:
Sohaib Khan
Date:
2/19/2009 1:36:56 AM
Comment:
Hi Steve,
I've 2 files which are abc.wsp (Solution Package of SharePoint) and Import.cmd(stsadm commands). Now, for distribution, i am using VS Setup Project. In Setup Project, i want to execute cmd file automatically so i am using PostBuildEvent.
|
Title:
Configuring the install code
Name:
Steven Barden
Date:
2/18/2009 9:15:08 PM
Comment:
Sohaib,
You will have to provide me with allot more details than that. Pretend I'm sending the same request for help to you, and reconsider how you would like things described.
|
Title:
Configuring the install code
Name:
Sohaib Khan
Date:
2/18/2009 9:38:07 AM
Comment:
Hi,
I've included *.cmd file and *.wsp file in my setup project. Now, I want to run cmd file after completion of installation automatically. So, i am using PostEventBuilder. I also tried your command but i am getting error. Any hint please ......
|
|
Product Spotlight
|
|
|
