SharePoint Tutorial

What is SharePoint - SharePoint Product Overview

Fri, 20 Apr 2012 01:09:00 +0200

This guide explains in easy words how to license SharePoint.

Here we go…

SharePoint 2010

There are 3 different version of SharePoint 2010 if it comes to differences in functionality:

SharePoint Foundation 2010
SharePoint Server 2010 - Standard
SharePoint Server 2010 - Enterprise

For an overview about the different functionality visit SharePoint 2010: How to buy.

SharePoint 2010 Licensing

If you create an intranet you need to license:

Servers,
Each server running SharePoint needs to have a license.
Users or devices
Each user or device needs a CAL (client access license)

For each user or device you can buy the standard CAL. If you want enterprise features you need both: The standard CAL and an enterprise CAL.

If you create an extranet or internet site you need to license:

Servers,
Each server running SharePoint needs to have a specific SharePoint 2010 for internets license.

Learn more about SharePoint 2010 Licensing or read the SharePoint 2010 Licensing details.

What is SharePoint - Overview

What is SharePoint - Yes you are an Information Worker!

Fri, 20 Apr 2012 01:08:00 +0200

In our daily work we all have problems making a decision since we can’t find or use the information we need to make a good decision.

I need to have access to information and I need to know if they exist or not independent of their storage.

So how about an application that helps me:

To work more easily and more efficient and
To securely store, manage and retrieve any information from anywhere?

I don’t want to waste time finding something, doing the same job someone else already did or to prepare information just to make a decision based on that.

I need something to store, to manage and to retrieve information, to find a person who may have the information I need and to access it from anywhere. I also need something that not only gets information I also need something that prepares, visualizes it or sorts it by relevance.

An application that can do all the things will have a great impact on my performance during my working day.

Being more efficient doesn’t mean working more.

What is SharePoint - Overview

What is SharePoint - The Solution called SharePoint

Fri, 20 Apr 2012 01:08:00 +0200

SharePoint is the tool Microsoft provides which can improve my work and the result of my work. It can also improve the work of my team, my department, my company or my partners.

You already know the following graphic:

You can use sites and communities to store and manage information as well as to collaborate with colleagues.

You can use content management features to set up compliance features for the information stored.

Content management also allows you to use information in your already existing working environment like Microsoft Office.

Search allows you to retrieve information independent of their storage or to find people with the skills needed.

Insights allow you to get, to prepare and to visualize (business) information stored in a different repository.

SharePoint provides a solution to all your information management needs with a secure and remote access.

Furthermore SharePoint can be enhanced with no code solutions called Composites.

The great thing is that SharePoint has a lot more facets and advantages than outlined here.

What is SharePoint - Overview

What is SharePoint - Way Too Much Information!

Fri, 20 Apr 2012 01:05:00 +0200

Information overload is a term which can be found in history before the digital or information age even started.

Usually it means that you have difficulties to make a decision because of too much information.

Information Overload

The amount of available information and the rate in which it is created increased and the way people communicate changed. Within an intranet scenario information can be stored at:

File shares,
Local hard disks,
Personal folders,
Different applications,
E-Mails or
In the head of a person you don’t know.

People may have problems to make decisions because they have too much information.

They may also have problems because they can’t find the information they need.

You can imagine that storage is one of the problems: Files are stored in different folders or sub folders without Meta information or with strange file names.

Information may not be retrieved since people just don’t know that certain information exists.

The access to information can be problematic because of remote or mobile access or due to granular security.

So how should I make a decision if I can’t find or use the information I need? Even if I find all the information how should I make a decision in time if it takes me hours or days to search and rate them?

What is SharePoint - Overview

SharePoint 2010 - Create Site Definitions and Site Templates with Visual Studio

Tue, 27 Mar 2012 20:00:00 +0200

Home > Branding > SharePoint 2010 - Create Site Definitions and Site Templates with Visual Studio

This guide shows you step by step how to create a SharePoint Publishing Site Definition and two Site Templates.

Site Definitions are XML files which are language dependent and therefore stored in different folders:

Each of the language dependent folders has a sub folder called XML:

Each Site Definition corresponds to a XML file and in order to create a new Site Definition you need to place a new XML file with the right markup in that folder.

1. Create a new solution called SharePoint2010.Publishing using the Site Definition template:

2. Deploy the solution to the Central Administration Web Application:

Actually you need a running Site Collection to deploy the solution using Visual Studio. Since the goal is to create a new Site Collection using a custom Site Definition it doesn’t exist right now. Instead we deploy the solution to the Central Administration for now.

3. Open the ‘webtemp_SharePoint2010.Publishing.xml’ file:

Remove the existing XML from the file.

4. Add the following XML to the file:

<?xml version="1.0" encoding="utf-8"?>
<Templates xmlns:ows="Microsoft SharePoint">
  <Template Name="SharePoint2010.Publishing" ID="14099">
    <Configuration ID="0"
      Title="Homepage"
      Description="Creating a custom polishing site…"
      DisplayCategory="SharePoint Tutorial"
      Hidden="False"
      ImageUrl="/_layouts/images/SharePointTutorial/SPT_Homepage.png" 
      RootWebOnly="TRUE"/>

    <Configuration ID="1"
      Title="Content Site"
      Description="Creating a custom polishing site…"
      DisplayCategory="SharePoint Tutorial"
      Hidden="False"
      ImageUrl="/_layouts/images/SharePointTutorial/SPT_Content.png"
      SubWebOnly="TRUE"/>
  </Template>
</Templates>

5. Before I explain the parts just deploy the solution to the Central Administration.

6. Open Central Administration and click to create a new site collection:

I think the picture explains the XML from above. The image URL property refers to an image lying under \14\TEMPLATE\IMAGES.

The first configuration can only be used to create Site Collections and the second one only to create sub sites.

7. In order to deploy an image for your custom Site Templates you need to add a mapped folder:

8. Add 2 images:

9. If you create a new site inside an existing Site Collection you should see the following if you have Silverlight installed:

10. Open the onet.xml file:

Remove the exiting XML from the file. Since Microsoft knows best how to do this we are going to reuse the XML from an existing file.

Go to the \14\TEMPLATE\1033\XML folder and look for a file which includes the Site Definition for the publishing site.

Open ‘webtempsps.xml’ and you will find a template named ‘BLANKINTERNET’ around line 34. This refers to a folder named ‘BLANKINTERNET’:

Inside \14\TEMPLATE\SiteTemplates\BLANKINTERNET\XML you’ll find an onet.xml file including Publishing Site Templates for reuse.

Important: The template name ‘BLANKINTERNET’ in webtemp.xml is the folder name where the onet.xml is stored! Otherwise onet.xml can’t be found during the creation of a new site.

11. Add the following XML to the file:

<?xml version="1.0" encoding="utf-8"?>
<Project Title="SharePoint2010.Publishing" Revision="2" ListDir="" xmlns:ows="Microsoft SharePoint" xmlns="http://schemas.microsoft.com/sharepoint/">
  <NavBars>
  </NavBars>
  <Configurations>
  </Configurations>
  <Modules>
  </Modules>
</Project>

This is the main structure which will be extended with configurations and modules.

12. Add the following XML inside the configurations section:

<Configuration ID="0" Name="Homepage">
  <Lists/>
  <SiteFeatures>
    <Feature ID="A392DA98-270B-4e85-9769-04C0FDE267AA" />
    <Feature ID="7C637B23-06C4-472d-9A9A-7C175762C5C4" />
    <Feature ID="AEBC918D-B20F-4a11-A1DB-9ED84D79C87E">
      <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
        <Property Key="AllowRss" Value="false"/>
        <Property Key="SimplePublishing" Value="false" />
      </Properties>
    </Feature>
    <Feature ID="F6924D36-2FA8-4f0b-B16D-06B7250180FA" />
  </SiteFeatures>
  <WebFeatures>
    <Feature ID="22A9EF51-737B-4ff2-9346-694633FE4416">
      <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
        <Property Key="ChromeMasterUrl" Value="~SiteCollection/_catalogs/masterpage/CustomV4.master"/>
        <Property Key="WelcomePageUrl" Value="$Resources:osrvcore,List_Pages_UrlName;/default.aspx"/>
        <Property Key="PagesListUrl" Value=""/>            
        <Property Key="AlternateCssUrl" Value="~SiteCollection/Style Library/Custom.css" />
        <Property Key="SimplePublishing" Value="true" />
      </Properties>
    </Feature>
    <Feature ID="541F5F57-C847-4e16-B59A-B31E90E6F9EA">
      <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
        <Property Key="InheritGlobalNavigation" Value="true"/>
        <Property Key="IncludeSubSites" Value="true"/>
        <Property Key="IncludePages" Value="false"/>
      </Properties>
    </Feature>
    <Feature ID="94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" />        
  </WebFeatures>
  <Modules>
    <Module Name="ModuleHomepage" />
  </Modules>
</Configuration>

<Configuration ID="1" Name="ContentSite">
  <Lists/>
  <WebFeatures>
    <Feature ID="22A9EF51-737B-4ff2-9346-694633FE4416">
      <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
        <Property Key="ChromeMasterUrl" Value="~SiteCollection/_catalogs/masterpage/CustomV4.master "/>
        <Property Key="WelcomePageUrl" Value="$Resources:osrvcore,List_Pages_UrlName;/default.aspx"/>
        <Property Key="PagesListUrl" Value=""/>
        <Property Key="AlternateCssUrl" Value="="~SiteCollection/Style Library/Custom.css" />
        <Property Key="SimplePublishing" Value="true" />
      </Properties>
    </Feature>
    <Feature ID="541F5F57-C847-4e16-B59A-B31E90E6F9EA">
      <Properties xmlns="http://schemas.microsoft.com/sharepoint/">
        <Property Key="InheritGlobalNavigation" Value="true"/>
        <Property Key="IncludeSubSites" Value="true"/>
        <Property Key="IncludePages" Value="false"/>
      </Properties>
    </Feature>
    <Feature ID="94C94CA6-B32F-4da9-A9E3-1F3D343D7ECB" />
  </WebFeatures>
  <Modules>
    <Module Name="ModuleContent" />
  </Modules>
</Configuration>

This is a lot of XML. We have 2 Site Templates… each of them references features which will be activated and configured during the creation of the site.

The first configuration includes ‘SiteFeatures’ which are site scoped features and activated during the creation of the site collection. The first configuration also includes ‘WebFeatures’ which are web scoped features which are also activated. Some of the features have properties which are set during activation like a Custom Master page ‘ChromeMasterUrl’ or custom CSS ‘AlternateCssUrl’.

All together each configuration can be described as a collection of settings of a SharePoint site. Each configuration references a module.

13. Add the following XML inside the modules section:

<Module Name="ModuleHomepage" Url="$Resources:cmscore,List_Pages_UrlName;" Path="">
  <File Url="default.aspx" Type="GhostableInLibrary">
    <Property Name="Title" Value="Homepage" />
    <Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/Homepage.aspx, ~SiteCollection/_catalogs/masterpage/Homepage.aspx" />
    <Property Name="ContentType" Value="TODO" />
    <Property Name="PublishingAssociatedContentType" Value=";#TODO;#TODO;#" />
  </File>
</Module>
<Module Name="ModuleContent" Url="$Resources:cmscore,List_Pages_UrlName;" Path="">
  <File Url="default.aspx" Type="GhostableInLibrary">
    <Property Name="Title" Value="ContentSite" />
    <Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/ContentPage.aspx, ~SiteCollection/_catalogs/masterpage/ContentPage.aspx" />
    <Property Name="ContentType" Value="TODO" />
    <Property Name="PublishingAssociatedContentType" Value=";#TODO;#TODO;#" />
  </File>
</Module>

Again we have some complex XML. Each module can be seen as the default page which is created if you create one of the sites. Each page contains a name, a URL, a Page Layout and a Content Type (since content is stored in columns which belong to a content type).

14. Done.

The XML looks quite complex and huge but if you copy and paste it inside a Visual Studio project you can use the Visual Studio editor to open and collapse each node of the XML. This way it’s easier to read.

Summary

Using the Site Definition and Site Definition Configurations (Site Templates) you have a basic structure for implementing custom Columns, Content Types, Master Pages and Page Layouts so you can create a SharePoint Publishing environment. This environment can be highly adapted to the needs of authors and their processes.

The guide was an excerpt from my popular book:

Learn SharePoint 2010 - Branding
80 pages focused step-by-step guide about Publishing and Collaboration
2 Visual Studio solutions

SharePoint Master Pages and Page Layouts - Deployment Process

Mon, 26 Mar 2012 20:00:00 +0200

Home > Branding > SharePoint Master Pages and Page Layouts - Deployment Process

This guide is part of Learn SharePoint and shows the deployment process of Master Pages and Page Layouts in basics words.

Here we go...

What is deployed?

Deploying Master Pages and Page Layouts involves the following components:

Feature.xml
Feature definition
Elements.xml
Defines:
- Which files belong to the feature
- Where to upload in the site collection
*.master and *.aspx
Files referenced in elements.xml
Assembly
Code behind for Master Pages or Page Layouts

Where is deployed?

If the feature is deployed to a web application it becomes available at the scope site collection. The feature.xml and the elements.xml are written to the file system in the features folder.

Master Pages and Page Layouts are also written to the same folder.

Assemblies are deployed to the Global Assembly Cache (GAC). Additionally files referenced in the elements.xml are uploaded to the SharePoint library called Master Pages Gallery.

Things to know!

If you retract the feature *.master and *.aspx files will remain in the Master Pages Gallery.
You need to deactivate and activate the feature if you deploy changes to the elements.xml and want them to show up in the Master Pages Gallery.
Changes to *.master and *.aspx files are reflected without feature reactivation.

The guide was an excerpt from my popular book:

Learn SharePoint 2010 - Branding
80 pages focused step-by-step guide about Publishing and Collaboration
2 Visual Studio solutions

SharePoint Publishing vs. Collaboration - The difference in basic words

Sun, 25 Mar 2012 20:00:00 +0200

Home > Branding > SharePoint Publishing vs. Collaboration - The difference in basic words

The difference between SharePoint publishing and collaboration is not only the flexibility to set Master Pages and Page Layouts using the User Interface.

A publishing site also has:

Additional libraries like Pages where your pages (.aspx) are stored. A SharePoint site is like a container for SharePoint pages.
Additional site settings e.g.
- Master Page allowing you to change the Master Page.
- Content and Structure showing you a hierarchical view of your sites.
A global navigation.
Additional security groups like Approvers, Designers or Hierarchy Managers and additional permission levels like Approve or Manage Hierarchy.
Additional images, styles, Web Parts, content types, columns or buttons inside the ribbon just to name a few.

Publishing isn’t some kind of template or Site Definition … it’s a mechanism changing the authoring and deployment experience of your web content sites.

Regarding branding publishing allows you to set Master Pages and Page Layouts in a more flexible way or to upload your own custom layouts via the User Interface using no code.

A publishing environment is more like a static website used to display information which does not change very often.

A collaboration environment is more dynamically regarding the information storage or exchange. Lists and libraries are extensively used in a collaboration environment.

SharePoint Publishing

Publishing is about web sites where content doesn’t change very often. Publishing equals a common web site where you directly edit a page via the browser, where you represent a club or a company. You have people with different roles like authors or designers and users which can be anonymous Internet users.

SharePoint Collaboration

A collaboration site is used if content changes dynamically. Usually you have libraries with a lot of documents. A small group of people are working together on a project or in a team. They share a calendar, they have discussions or tasks… it’s about the extensive use of lists and libraries.

The guide was an excerpt from my popular book:

Learn SharePoint 2010 - Branding
80 pages focused step-by-step guide about Publishing and Collaboration
2 Visual Studio solutions

Learn SharePoint 2010 - Branding

Thu, 22 Mar 2012 19:04:00 +0200

Your Guide to Learn SharePoint 2010 Branding

Learn SharePoint 2010 in days
Without Weeks of Self-Study, Headaches, Saving You Money AND Time

Picture this... you need to learn SharePoint Branding, and you need it quick.

Your project is going on, there is a due date and your employer and your customer are expecting results. You have to deep dive into the huge amount of resources for SharePoint. Where do you start, how many books with thousands of pages do you have to read? Which courses do you have to attend?

That’s where this guide comes in…

"All information at one place saved me weeks of searching."
(Customer Testimonial)

When it’s time to learn SharePoint no one gives you enough time and resources. You as a developer are using your free time, in the evening and on the weekend. Everyone is expecting results and no one has a plan for you.

The SharePoint 2010 Branding Guide is the easy to follow, step by step guide to a successfully learn SharePoint Branding. You’ll avoid weeks of self study, instead you get a plan and resources.
80 pages of step by step instructions walk you through the entire process:

Learn the concept behind Site Definitions, Site Templates, Master Pages, Page Layouts, CSS and Images
Learn the concept behind Publishing and Collaboration
Learn how to deploy Site Definitions, Site Templates, Master Pages, Page Layouts, CSS and Images
Learn the difference between un-customized (ghosted) and customized (unghosted) files
Implement your own branding solutions for Collaboration sites
Implement your own branding solutions for Publishing sites including Site Definitions, Site Templates, Master Pages, Page Layouts, CSS and Images
Bonus: 2 reusable Visual Studio solutions - one for branding Collaboration sites and one for branding Publishing sites
Instant Access Download so you can get started right now

It seems that it's always up to the developers to learn, using their own free time and their own money... let alone having to deal with the steep learning curve of SharePoint Branding as well.

You don’t need to invest weeks of your time and hundreds of dollars. You just want to start right now developing your own SharePoint solutions.

When you buy the SharePoint 2010 Branding guide you’ll get instant access to:

The guide itself, an 80 page PDF with detailed, step by step instructions that walk you through the entire process of SharePoint Branding
Learn how to brand Collaboration and Publishing sites including custom Site Definitions and Master Pages
Bonus: 2 Visual Studio example solutions for
- Branding a Collaboration site with a custom Master Page and CSS
- Branding a Publishing site with a custom Site Definition, Site Templates, Master Pages, Page Layouts, CSS and Images
Instant Access Download so you can get started right now

Add to cart

Special Offer: Learn Branding + Learn Development
$60 US (-18%)
Add to Cart

A Word from the Author

It took me since 2006 literally 2 years before I implemented great SharePoint solutions. Since 2008 I delivered Intranet and Internet solutions which are still today essential for my clients. Using this knowledge I created this guide so you can start right now to do the things that took me a lot of time.

- Andreas Glaser,

What’s Inside the SharePoint 2010 Branding Guide

Learning Backgrounds

Understand the background.

What is Collaboration and Publishing?
What are Site Definitions, Site Templates, Master Pages and Page Layouts
What are customized (unghosted) and un-customized (ghosted) files?

Concepts

Understand the concepts.

How Site Definitions, Site Templates, Master Pages, Page Layouts, CSS and Images are related to each other
How to deploy customizations using solutions and features
How to deploy customizations in detail including Site Definitions, Site Templates, Master Pages, Page Layouts, CSS and Images

Practice

Develop your own solutions.

How to brand a collaboration site
How to create a new Publishing Site with a custom Site Definition

Troubleshooting & Tools

Ease your work.

How to enable custom errors, debug solutions and read the ULS
How to enhance the development process using Firebug and Fiddler

Buy now for just $37 USD and get:

80 pages of step by step instructions showing how to brand SharePoint 2010
Learn how to brand Collaboration and Publishing sites including custom Site Definitions and Master Pages
Bonus: 2 reusable Visual Studio solutions - one for branding Collaboration sites and one for branding Publishing sites
Instant Access Download so you can get started right now

Add to cart

Special Offer: Learn Branding + Learn Development
$60 US (-18%)
Add to Cart

Frequently Asked Questions

Will this guide show me exactly how to brand SharePoint 2010?

Yes. You’ll get clear, easy to follow instructions that include screenshots for every step of the development process.

Does this guide show me how to use SharePoint Designer to create HTML and CSS?

No, it's not about:

Web Templates (Saving existing sites as a site template).
SharePoint Designer.
Explaining each place holder.
Being a HTML or CSS guru.

Buy now for just $37 USD and get:

80 pages of step by step instructions showing how to brand SharePoint 2010
Learn how to brand Collaboration and Publishing sites including custom Site Definitions and Master Pages
Bonus: 2 reusable Visual Studio solutions - one for branding Collaboration sites and one for branding Publishing sites
Instant Access Download so you can get started right now

Add to cart

Special Offer: Learn Branding + Learn Development
$60 US (-18%)
Add to Cart

You have 30 days (more than enough time to go through the entire guide) to see if the SharePoint 2010 Branding Guide is the real deal or not. If you ever feel that it wasn't worth your money, please let me know and I will issue you a full, NO HASSLE refund for your investment.

Terms and license

SharePoint Web Parts - Development

Mon, 12 Mar 2012 11:27:00 +0200

Home > Development > ASP.NET and SharePoint 2010 - The difference in basic words

This guide is part of Learn SharePoint and shows the development of a Web Part in basics words.

We are going to develop a Web Part which creates, reads, updates and deletes content in a SharePoint list.

Create a new Site Collection based on the “Blank Site” template where we are going to deploy our solution.

1. Create a new farm solution called SharePoint2010.WebParts.

2. Right click the SharePoint2010.WebParts project and add a new Web Part:

3. Rename your Web Part:

4. Let’s brand the feature using a reference to an image lying in \14\TEMPLATES\Images:

Double click the feature to see the built-in designer.
Click Manifest at the bottom to see the XML.
Click edit to add custom XML.

5. Right click on the SharePoint2010.WebParts project and add a mapped SharePoint images folder:

6. Rename the mapped folder and add a custom feature.gif and a webpart.gif file:

7. Let’s brand the Web Part using a reference to the image lying in \14\TEMPLATES\Images.

Open WebPartDemo.webpart and create a reference to the webpart.gif:
Note: You need to deploy the image to the folder \14\TEMPLATES\Images although there is a reference including /_layouts/.

8. Open WebPartDemo.cs and create 2 buttons and attach an event handler to the click event:

protected override void CreateChildControls()
{
    Button btnCreateContent = new Button();
    btnCreateContent.Text = "Create content";
    btnCreateContent.Click += new EventHandler(btnCreateContent_Click);

    Button btnDeleteContent = new Button();
    btnDeleteContent.Text = "Delete content";
    btnDeleteContent.Click += new EventHandler(btnDeleteContent_Click);

    Controls.Add(btnCreateContent);
    Controls.Add(btnDeleteContent);

    base.CreateChildControls();
}

9. Add the following code below the CreateChildControls() method to delete content:

void btnDeleteContent_Click(object sender, EventArgs e)
{
    SPList list = SPContext.Current.Web.Lists.TryGetList("Products");

    if (list != null)
        list.Delete();
}

10. Add the following code below the CreateChildControls() method to create content:

void btnCreateContent_Click(object sender, EventArgs e)
{
    SPContext.Current.Web.Lists.Add("Products", 
        "Contains products with a product number.", 
        SPListTemplateType.GenericList);

    SPList list = SPContext.Current.Web.Lists.TryGetList("Products");

    if (list != null)
    {
        list.OnQuickLaunch = true;
        list.Update();

        for (int i = 0; i < 100; i++)
        {
            SPListItem item = list.Items.Add();
            item["Title"] = "Product - " + i.ToString();
            item.Update();
        }
    }
}

11. Right click on the project and deploy the solution. If you edit the blank site and add your Web Part you can see the following Web Part displayed:

12. Deploy the solution, click create content and refresh the homepage:

A new list appears with 100 list items.

13. Let’s add a new button to update content:

protected override void CreateChildControls()
{
    ...

    Button btnUpdateContent = new Button();
    btnUpdateContent.Text = "Update content";
    btnUpdateContent.Click += new EventHandler(btnUpdateContent_Click);

...

    Controls.Add(btnUpdateContent);
    base.CreateChildControls();

}

14. Add the following code to the event handler to update content.

First we try to get the list.
If the list exists we add a new column called “Price” and we update the list.
If the default view doesn’t show the price column we add it to the shown columns.
At the end we write content for each item to the new price column.

void btnUpdateContent_Click(object sender, EventArgs e)
{
    SPList list = SPContext.Current.Web.Lists.TryGetList("Products");

    if (list != null)
    {
        list.Fields.Add("Price", SPFieldType.Text, false);
        list.Update();

        if (!list.DefaultView.ViewFields.Exists("Price"))
        {
            SPView view = list.DefaultView;
            view.ViewFields.Add("Price");
            view.Update();
        }

        SPListItemCollection itemColl = list.Items;

        foreach (SPListItem item in itemColl)
        {
            item["Price"] = "Free of cost";
            item.Update();
        }
    }
}

15. Deploy the solution, click update content and open the products list:

16. Let’s add new code to read and display content.

First we try to get the list.
If the list exists we add a new ListViewByQuery which aggregates data from the products list using the default view.

protected override void CreateChildControls()
{

    SPList list = SPContext.Current.Web.Lists.TryGetList("Products");

    if (list != null)
    {
        ListViewByQuery grid = new ListViewByQuery();
        grid.List = list;

        SPQuery myQuery = new SPQuery(list.DefaultView);
        myQuery.RowLimit = 5;

        grid.Query = myQuery;

        Controls.Add(grid);
        Controls.Add(new LiteralControl("<br />"));
    }
    base.CreateChildControls();
}

17. After you deploy the solution you can see a list view if the list exists:

18. Done

The guide was an excerpt from my popular book:

Learn SharePoint 2010 - Development
100 pages focused step-by-step guide
6 Visual Studio solutions

SharePoint Web Parts - Deployment Process

Mon, 12 Mar 2012 10:47:00 +0200

Home > Development > ASP.NET and SharePoint 2010 - The difference in basic words

This guide is part of Learn SharePoint and shows the deployment process of Web Parts in basics words.

What is deployed?

Deploying a Web Part involves the following components:

Feature.xml
Definition of the customization that is deployed
Elements.xml, defining:
- Which Web Part belongs to the feature
- Where to upload in the Site Collection
Web Part definition, *.webpart or *.dwp referenced by the elements.xml including e.g.
- A title
- An assembly reference
Safe Control
Web Parts need an entry in the web.config so the code will be executed
Assembly,
Code of the Web Part

Where is deployed?

If the feature is deployed to a Web Application it becomes available at the scope Site Collection. The feature.xml, the elements.xml and the Web Part files (*.webpart, *.dwp) are written to the file system in the features folder.

Assemblies are deployed to the Global Assembly Cache (GAC) and the web.config is modified with entries in the safe control section.

If you activate the feature the declaration in elements.xml will be executed which contains the upload of the *.webpart and *.dwp files to the Web Parts Gallery on the Site Collection root.

Only after the upload a Web Part becomes available if you click “Add a Web Part” on your site:

Things to know!

Assemblies of Web Parts can be deployed to the bin folder or the solution gallery too.
If you retract the feature the *.webpart and *.dwp files will remain in the Web Parts Gallery.
If you change properties in the Web Part definition *.webpart upgrading the solution won’t show the changes. You need to retract, remove, install and deploy the solution.
If you add new Web Part definitions to the feature upgrading the solution won’t upload the new definition to the Web Parts Gallery. You need to deactivate and activate the feature or retract, remove, install and deploy the solution again.

The guide was an excerpt from my popular book:

Learn SharePoint 2010 - Development
100 pages focused step-by-step guide
6 Visual Studio solutions

SharePoint Tutorial

What is SharePoint - SharePoint Product Overview

SharePoint 2010

SharePoint 2010 Licensing

What is SharePoint - Yes you are an Information Worker!

What is SharePoint - The Solution called SharePoint

What is SharePoint - Way Too Much Information!

Information Overload

SharePoint 2010 - Create Site Definitions and Site Templates with Visual Studio

Summary

SharePoint Master Pages and Page Layouts - Deployment Process

What is deployed?

Where is deployed?

Things to know!

SharePoint Publishing vs. Collaboration - The difference in basic words

SharePoint Publishing

SharePoint Collaboration

Learn SharePoint 2010 - Branding

Your Guide to Learn SharePoint 2010 Branding

Learn SharePoint 2010 in days Without Weeks of Self-Study, Headaches, Saving You Money AND Time

A Word from the Author

What’s Inside the SharePoint 2010 Branding Guide

Learning Backgrounds

Concepts

Practice

Troubleshooting & Tools

Buy now for just $37 USD and get:

Frequently Asked Questions

Will this guide show me exactly how to brand SharePoint 2010?

Does this guide show me how to use SharePoint Designer to create HTML and CSS?

Buy now for just $37 USD and get:

SharePoint Web Parts - Development

SharePoint Web Parts - Deployment Process

What is deployed?

Where is deployed?

Learn SharePoint 2010 in days
Without Weeks of Self-Study, Headaches, Saving You Money AND Time