Site pages vs Application pages

Site pages are pages that are created, edited, and customized by end users. They are primarily used for the content in a site. Site pages come in two types—a standard page and a Web Parts page. A standard page contains text, images, Web Parts, and other elements. A Web Parts page contains Web Parts in Web Part zones. They have a predefined layout that uses Web Part zones. Both types of site pages are edited using a Web browser or Microsoft SharePoint Designer.

Site pages are provisioned from a template page that is stored on the file system of the front-end Web server. When a site is provisioned, SharePoint Foundation creates a pointer to the instance of the page template on the file system. This allows SharePoint Foundation to avoid repeatedly creating copies of the pages, which are provisioned each time a site is created.

When a user customizes a site page, the template for the page is then stored in the content database. The page is retrieved from the content database every time it is requested by a user. A customized page can, however, be reset to the original template page through the Web browser or a tool such as SharePoint Designer.

Application pages are used to support application implementations in SharePoint Foundation. Application pages are stored on the file system of the front-end Web server in the %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\TEMPLATE\LAYOUTS directory and exist for every site in a Web application. This folder is mapped to an Internet Information Services (IIS) virtual directory called _layouts. Every site and subsite will have access to the application pages by using the _layouts virtual directory. For example,http://myserver/_layouts/settings.aspx and http://myserver/subsite/_layouts/settings.aspx access the same application page on the front-end Web server unlike site pages, which are an instance for the specified site.

Application pages are not subject to the same restrictions as site pages. They allow in-line code without restriction. They cannot, however, use dynamic Web Parts or Web Part zones or be modified using SharePoint Designer. Modifying the default application pages is not supported in SharePoint Foundation. Custom application pages can be added to a subdirectory inside the _layouts folder.

Calendar view for a list

Create a calendar view for an existing list

SharePoint 2007

SharePoint 2007 

Calendar Overlay & Color Options

David Lozzi.com

Overlay and Color Options

SharePoint cool sites...

Resultado de testes na imagem abaixo:

Calendar Reminder

How to : Add Reminder to SharePoint 2010 Calendar

http://kmlsp.wordpress.com/2012/03/13/how-to-add-reminder-to-a-calendar/

LINQ to SharePoint Provider

The gateway class for the LINQ to SharePoint provider is Microsoft.SharePoint.Linq.DataContext which represents the data of a SharePoint Foundation Web site. 

It is parallel in use and function to the System.Data.Linq.DataContext class in the LINQ to SQL provider. 

Just as the latter class has a GetTable() method that returns a Table<TEntity> object that implements System.Linq.IQueryable<T>, so too, the Microsoft.SharePoint.Linq.DataContext class has a GetList<T>method that returns an EntityList<TEntity> class that implements System.Linq.IQueryable<T>. 

It is objects of type EntityList<TEntity> that are queried.

The following is an example of the use of LINQ to query SharePoint Foundation.

// Get DataContext from page context
DataContext data = new DataContext(SPContext.Current.Web.Url);

// Get the SharePoint list
EntityList<Customer> Customers = data.GetList<Customer>("Customers");

// Query for customers from London
var londonCustomers = from customer in Customers
                      where customer.City == "London"
                      select customer;

foreach (var londonCust in londonCustomers)
{
    Console.Writeline("id = {0}, City = {1}", 
                      londonCust.CustomerId, 
                      londonCust.City);
}

The following is an example of using LINQ to add an item to a SharePoint Foundation list.
// Get DataContext from page context
DataContext data = new DataContext(SPContext.Current.Web.Url);

// Get the SharePoint list
EntityList<Customer> Customers = data.GetList<Customer>("Customers");

// Create the item to be added
Customer newCustomer = new Customer() { CustomerId=36, City=”Madrid” };

// Mark the item to be added on the next call of Submit
Customers.InsertOnSubmit(newCustomer);

// Submit all changes
data.SubmitChanges();

SharePoint 2010

Todo material foi compilado em palestras e são informações valiosas sobre SharePoint 2010.

Sharepoint :: Ações do Site

Sharepoint :: Recursos do Site

Sharepoint :: Configurações do Site

SharePoint 2010 :: Treinamento de Introdução

Sharepoint :: ListInstance create new Contacts list

<ListInstance
TemplateType="105"
FeautureId="00bfea71-7e6d-4186-9ba8-c0727181919191"
Title="Clientes"
Description="Lista de Clientes"
Url="Lists/Customers"
OnQuickLaunch="TRUE" >
</ListInstance>

Sharepoint :: List Templates

Template Name	Template Type	Template Type ID
Custom List	GenericList	100
Document Library	DocumentLibrary	101
Survey	Survey	102
Links List	Links	103
Announcements List	Announcements	104
Contacts List	Contacts	105
Calendar	Events	106
Tasks List	Tasks	107
Discussion Lists	DiscussionBoard	108
Picture Library	PictureLibrary	109
Form Library	XMLForm	115
Wiki Page Library	WebPageLibrary	119

What Is a Workflow?

SharePoint, a workflow is a series of steps - some automatic, some manual - that must be performed as part of a business process for a document or a list item.

What Does Check-in/Check-out Mean?

Check-in and check-out are common terms in many document management systems, including SharePoint.

Their purpose is to prevent conflicts in an environment where multiple people might want to edit the same piece of content (in SharePoint, list items or files) at the same time. The term check-in describes the process of adding a new or modified item or file to a document library or a list to replace the previous version.

The term check-out describes the process of getting a version of a document or list item in a list or library. By checking out an item or a file, a user can prevent others from editing that content. By checking in the item, the user can allow others to edit the content, without needing to worry about overriding changes that others have made.

What Are Versions?

Document libraries and lists in SharePoint have an option to track versions.

This option stores old versions of files or items each time a change is made. For example, if a user What Does Check-in/Check-out Mean? 27 uploads a document, and then another user edits the document and saves it, SharePoint saves the original document as a version of the file. Later, users can look at the version history of the file and choose to open a specific version or restore it (that is, make that version the current one).

SharePoint supports two types of versioning. In the first type, each change is regarded as a major change, and the version numbers go from 1 (the first time a document was uploaded) to 2 (after the first change) and then 3 and 4 and so on.

In the second type, each change is regarded as a minor change, unless the user specifies that it is a major one. The version numbers go from 0.1 (the first time a document was uploaded) to 0.2 (the first change) and so on, until a user selects the option to perform a major change, and the version number changes to 1.0, and subsequent changes raise it to 1.1, 1.2, and so on.

What Is Managed Metadata?

Available only through Microsoft SharePoint 2010 Server (not SPF), managed metadata is a mechanism that enables administrators to create hierarchical term sets that can then be used in document libraries and lists as columns.

A term set is similar to a list that contains items, except that these items can contain more items under them in a hierarchy. For example, if you have a term set called Products, you could have a term for each product that you have in the organization.

By using managed metadata, you can create the list as a hierarchical list, grouping the products into categories (creating terms for the categories and then terms for the products under them) or into product groups;

What Is Tagging?

Tagging is a social web mechanism available in Microsoft SharePoint 2010 Server (not in SPF) that enables you as the user to tag a document or a list item or a even a page - in the SharePoint site or outside it.

You can tag something to help remember it and find it more easily later on.

One tag that SharePoint comes with is the I Like It tag. This tag enables you to signify that you like a document or a page, and then other people can see that you liked it.

You  can easily find that document or page again by looking at the list of items you’ve tagged as things you like (usually from your personal site).

What Is a Content Type?

Lists and document libraries can store different kinds of content, known as content types. A site manager can create and manage the content types in a site. The content types are then available in that site and in all the
sites under it. The different types of content may have different site columns and/or different settings, such as policies and workflows, associated with them.

Content types can use site columns only for column definitions. This means that to create a content type, you must choose what site columns should be included in that content type.

A simple example of a content type is a list of contacts that stores two types of contacts—an internal contact and an external contact. The Internal Contact content type is used for a contact inside the company—and as such does not need the company property because all internal contacts are from the same company. However, the External Contact content type does require the company property because every contact may be from a different company. Hence, a single list has two different column requirements.

What Is a Site Column?

A site column is a column for a list or a document library that can be used in all document libraries or lists in the site in which it is created, as well as in the subsites for that site.

A site manager can define a specific column of data once and manage it from a central location instead of creating that column many times in many lists and libraries. In addition, content types can only use site columns. (In lists and libraries, on the other hand, columns can be created separately.)