InfoPath Designer 2010:Using Views to Add a Confirmation Screen on Form Submit

The InfoPath Form Web Part is pretty handy, but its options for behavior upon submitting are less than ideal. The only options available are leaving the form open, closing it, or opening a new one. Luckily, InfoPath Designer 2010 offers a fairly painless solution. Let’s start with a basic form.

This is going to be our default view, but we’ll need two more to handle the submit and cancel actions. Select the Page Design tab on the ribbon and click New View. Name the new view “Submit,” and add some kind of message to the blank page that has appeared.

Next, create another view named “Cancel” and add an appropriate message there.

Now we need to create a few rules to display these views when appropriate. Navigate back to your default view using the View dropdown menu on the Page Design tab and click your submit button. On the Home tab, click Manage Rules. Add a new action rule with the type Switch views. Select “Submit” from the view list and click OK. Add a similar rule for your cancel button.

Before you publish the form, you’ll need to take a look at the Submit Options from the File tab. Make sure that After submit is set to “Leave the form open.”

Finally, publish the form, add it to your InfoPath Form Web Part, and change the Submit Behavior setting for the web part to “Leave the form open.” Now, your form will display your custom message instead of something confusing like this:

Of course, you could also use this for more complex scenarios, like creating multi-page forms. If you added conditions to your buttons’ rules, you could even display context-dependent views, displaying different forms based on data the user entered on the default page.

Create viso diagram webpart Sharepoint 2010 – Tutorial

Visio has some great "mash-up" capabilities, which enable it to easily be integrated into SharePoint 2010. To create a simple Visio Web part diagram, follow these steps:

1. Open Visio 2010. Click File ➪ New and then select the ITIL Diagram.

2. Create a diagram.

3. When you finish building the diagram , click the Backstage tab (the tab on the upper-left part of the Visio document) and then click Share. At the bottom of the Backstage view, select Web Diagram. Note that, after you've finished, when you click Save As, there is an Options button that you can click to see
what pages (if you have multiple pages in your Visio diagram) will be published to Visio Services.

4. Next, upload the Visio diagram to a document library.

5. Click the drop-down menu beside the uploaded document and select View Properties.

6. Select Copy Shortcut.

7. Navigate to the location where you want to add the diagram on your SharePoint site, and then click Site Actions ➪ Edit Page.

8. Click "Add a web part" (or, if you're on a wiki page, click the Insert tab and select Web Part).

9. Navigate to the Office Client Applications, and select Visio Web Access Web part.

10. Once it is added, you can edit the Web part using the tool pane. Specifically, you want to copy the shortcut to the Visio diagram into the Web Drawing URL file and then click Apply. The Visio Web drawing will now be rendered in your SharePoint site.

Create infopath form in Sharepoint 2010 -Tutorial

InfoPath forms are easy to create and deploy to SharePoint. To create an InfoPath form, follow these steps:

1. Create a Custom list called "Customers" in your SharePoint site. Create three columns entitled Contact Name, Email, and Phone Number. Make all of the fields of type "Single line of text."

2. Open InfoPath 2010 and click File.

3. Double-click the SharePoint List template.

4. In the Data Connection Wizard, enter the URL for the SharePoint site and click Next.

5. Click the Customize an Existing SharePoint List radio button, and then select the Customers list.

6. Accept the default name for the connection on the next step of the wizard, and click Finish.

7. When complete, InfoPath will generate a form that maps to the fields you created in your Customers list.

8. You can click Preview to preview the form, or you can click the Quick Publish button (to the right of the Save icon) to publish the form to SharePoint. When it is published, InfoPath will prompt you with a successful publish message.

9. To use the form in SharePoint, navigate to your SharePoint site and click Site Actions ➪ Edit Page.

10. Click "Add a web part." Click the Office Client Applications category, and select InfoPath Form Web Part. Click Add.

11. SharePoint exposes the default InfoPath capabilities, but you need to map it to a particular form. To do this, select "Click here to open the tool pane."

12. In the "Lists or Library" drop-down, select the Customers list and leave all of the other default options. Click OK. SharePoint renders the InfoPath form you created in the SharePoint Web part.

13. To use the InfoPath form, click the Forms Edit tab. Add some data to the form and click Save. The data you enter into the form will be saved in the Contacts list.

Taking the BCS list offline in Sharepoint 2010

After you've created and secured your external list, SharePoint supports taking the list offline so that you can program against the cached data on the client from your external data source. BCS also offers a client-side object model to allow you to program against the cached data once you've taken it offline. in this post we'll take the external list MyCustomers that we created offline and expose the list in SharePoint Workspace.

Here are few easy steps for how to do that

1. Open the MyCustomers list external list.
2. Click the List tab on the SharePoint ribbon. Note that in the "Connect & Export" group, you have different options available to you (for example, to sync with Outlook or SharePoint Workspace) to take the external list offline.
3. Click the "Sync to SharePoint Workspace" button, and you'll be prompted to accept the Installation of a file to your local machine. Click Install to initiate the VSTO Package installation on your machine.
4. After the client-side package is installed, you will be prompted with a dialog that indicates the Office Customization was successfully installed. You can then open SharePoint Workspace to view the external list offline in SharePoint Workspace.

Create dataview webpart in sharepoint 2010 – Tutorial

A Data View Web part can be a great way for both developers and end users to provide some automatic and dynamic formatting for a list. To create a Data View Web part, follow these steps:

1. Open your SharePoint site and click Site Actions ➪ Edit in SharePoint Designer.
2. After SharePoint Designer 2010 opens, click Site Pages( if you want to create a new page or else just open the page where you want to add the dataview webpart go to step 4).
3.(optional) You now want to create a new Web part page. To do this, click the Web part page down-arrow on the ribbon and then select one of the predefined templates. Replace the default filename (for example Untitled_1.aspx) with your own filename (for example, myDataViewPage.aspx). Press Enter when done.
4. To edit the file, first click the file and then click Edit File in the main Web part page properties window.
5. Click one of the Web part zones, and then click the Insert tab on the ribbon and select Data View. Then select the List you want to add.
6. After SharePoint Designer updates the view with the most recent data in the list, you can add some automatic formatting.
7. For e.g. Under Conditional Formatting, select Format Column and under the Field Name, select YouNumberField. Make the Comparison value Equals. Then, add the value of 1 in the Value field. Click the Set Style button to change the background of the cell to be green. This way you can add filtering and Conditional Formatting for fields in the webpart.
8. Save the Web part page.
9. Open SharePoint, and navigate to the Web part page. You should see your new webpart.

Understanding Resource files in SharePoint 2010 – Tutorial

SharePoint defines two kinds of resource files: runtime resources (also called application resources) and provisioning resources. Application resources are used within the normal execution of a SharePoint application. SharePoint also distinguishes between application resources used in normal web applications and those used in Central Administration. Provisioning resources, on the other hand, are used when provisioning elements. You use them within features, site definitions, and list definitions. This means you need to be aware of the deployment and usage scenarios.

Provisioning Resources
Provisioning resources are used to localize solutions. This includes
• Descriptions for solutions, features, Web Parts, lists, sites, and so on
• Options presented in choice fields (SPFieldChoice controls)
• Base names of files used in the solution, such as "images" and "template"
• String resources used in the definition files

Resources encapsulate and abstract data from logic and design. This makes sense in larger projects involving many developers. Resources are mainly, but not exclusively, used for localization.

Resource Locations
Resource files in SharePoint are located in different folders, including these:
• C:\Inetpub\wwwroot\wss\VirtualDirectories\\App_GlobalResources\
• $SharePointRoot$\14\Resources\
• $SharePointRoot$\14\CONFIG\Resources\
• $SharePointRoot$\14\CONFIG\AdminResources\
• $SharePointRoot$\14\TEMPLATE\FEATURES\\Resources\

The target folder you use depends on what kind of resource you want to deploy. Every type of resource has its own folder. Provisioning resources are part of either a solution package or a feature and they land in these folders:

• $SharePointRoot$\14\TEMPLATE\FEATURES\\Resources\Resources..resx
• $SharePointRoot$\14\TEMPLATE\FEATURES\\Resources\
• $SharePointRoot$\14\Resources\

Every feature uses the resources file located in its Resources folder. You can, however, use another resource file or even shared resources. To share resource files you have to put them in the 14\Resources\ folder. This is the default option that is used when you add an item of type Global Resource File to your current solution. Site definitions and list definitions also get their resources from this folder.

Application resources can appear in these folders:
• $SharePointRoot$\14\CONFIG\Resources\
• C:\Inetpub\wwwroot\wss\VirtualDirectories\\App_GlobalResources\

Application resources are located in the CONFIG\Resources folder. For a web application to use those resources, they must be copied to their own App_GlobalResources folder. This is standard practice for global resources in any conventional ASP.NET project. On creation of the web application, the resources are initially copied to the App_GlobalResources folder. When you add new resources to the CONFIG\Resources folder, the resources need to be copied to existing web applications. You can do this
manually or use the stsadm command copyappbincontent. Alternatively, you can automate this by including the following in your FeatureActivated event in your feature receiver.

Spquery in Sharepoint 2010 – Tutorial

There are many ways to pull data out of SharePoint. You can use the object model and get hold of the SPList object, and run a for/each over SPListItems or you can create a CAML query and pass a SPquery object to retrieve the filtered list items from the SPListItems object.

CAML, the Collaborative Application Markup Language, is used for many purposes within SharePoint, one of which is extracting the very data you need and striking an excellent balance between speed, dependability, and accuracy. SharePoint Developers can write a CAML query specifying the fields they want and the filter condition for the items to be retrieved, and can assign that query to query property of the SPQuery object. This SPQuery object is then passed to the GetItems method on the list items, to retrieve the desired result. Lets looks at an example for writing a basic query using SPquery object.

Basic Query – Query to get all the Items from a list where SPVersion field is equal to "2010″

using (SPSite curSite = new SPSite(SPsiteUrl))
{
SPWeb curWeb = site.OpenWeb();
SPQuery curQry = new SPQuery();

//Write the query (I suggest using U2U Query Bulider Tool)
curQry.Query = "<Where><Eq><FieldRef Name='SPVersion' /><Value Type='Text'>2010</Value></Eq></Where>";

//Get the List
SPList myList = myWeb.Lists["ListName"];

//Get the Items using Query
SPListItemCollection curItems = myList.GetItems(curQry);

SPQuery enhancements in SharePoint 2010 - With the Introduction of Referential integrity implemented by Lookup columns in SharePoint 2010, developers now also have the ability to use some new fancy properties of the SPQuery object.
The new added enhancements in CAML and SPquery are :

1. <Joins> element in CAML and the SPQuery.Joins property
2. <ProjectedFields> element in CAML and the SPQuery.ProjectedFields.

Joins - Joins in SharePoint are driven off of lookup-based columns.

For e.g. if we a have List1 with following column. City being the Lookup column.
Name
Address
City <strong>-> Lookup Column</strong>

and List2 with following columns
City
ZipCode

and if we have to access the Zipcode column from List2 along with the name and address from our List1 we will use a Join element in Our CAML to specify the our foreign key column i.e. City and will assign the CAML to SPquery.query property. We will then create the ProjectedFields element for specifying the ZipCode column (the column we need from List2) and assign it to the SPquery.ProjectedFields property.

ProjectedFields - These are fields in the List2, which you can access using CAML's ProjectedFields element tag.

Let's look at an example. In the below query i am trying to retrieve all the items from List1 where name ="isha" and the related zipcode field from the List2.

using (SPSite site = new SPSite(SPsiteUrl))
{
SPWeb web = site.OpenWeb();
SPQuery query = new SPQuery();
query.Query =
@"<Where><Eq>
<FieldRef Name='Name' /><Value Type='Text'>Isha</Value>
</Eq></Where>"

query.Joins =
@"<Join Type='LEFT' ListAlias='List2′>
<Eq>
<FieldRef Name='City' RefType='Id'/>
<FieldRef List='List2′ Name='ID'/>
</Eq>
</Join>";

query.ProjectedFields =
@"<Field
Name='Zipcode'
Type='Lookup'
List='List2'
ShowField='Zipcode' />";

SPListItemCollection items = web.Lists["List1"].GetItems(query);

Content Deployment Step-By-Step

Step 1: Create a source site collection

First you will need a site to serve as the source for the content deployment job. So lets create the source site collection first.
1. On the SharePoint Central Administration Web site, in the Application Management section, click Create site collections.

Step 2: Create a new Web application – As I have explained in my previous post that you cannot copy your source site into a destination site, which resides in the same content database as source, you must first either create a new Web application to hold the destination site or create a new content database in the current web application. To Create a new webapplication see the steps below.

1. On the Central Administration Web site, in the Application Management section, click Manage web applications.
2. On the Web Applications Management page, click New.
3. In the IIS Web Site section, in the Port box, type 8888.
4. In the Application Pool section, in the Application pool name box, type Destination Site.
5. Accept all other default values, and click OK. The Application Created window appears.
6. In the Application Created window, click OK.

Step 3: Create a destination site collection

The next step is to create an empty site collection to hold the deployed site. Remember, you must not specify a template for the site collection. If a template is used to create the site collection, the content deployment job will fail. You can create the destination site collection by using the Select template later option when you create an empty site in the Central Administration Web site. Or, you can create the destination site collection by using the PowerShell cmdlet to create an empty site without specifying a template.

Step 4: Enable incoming content deployment jobs

By default all incoming deployment jobs are rejected by the destination server. Before you can create a content deployment path, you must enable incoming jobs on the destination server. In this walkthrough, the source and destination servers are the same.

1. On the Central Administration Web site, click General Application Settings.
2. On the General Application Settings page, in the Content Deployment section, click Configure content deployment.
3. On the Content Deployment Settings page, select Accept incoming content deployment jobs.
4. Click OK.

Step 5: Create content deployment path

The next step is to create the content deployment path which will enable you to select the source site collection and the destination site collection.
To Create one follow the below steps:

1. On the Central Administration Web site, in the General Application Settings section, click Configure content deployment paths and jobs.
2. On the Manage Content Deployment Paths and Jobs page, click New Path.
3. On the Create Content Deployment Path page, enter the url's for Source and destination site collection and also the Authentication Information.
Note : you might also need to provide Central Administration Web Application url for the Destination server. In our case since we are copying the content to the same server, but different web application, we can provide the central administration path that we locally use on our server.

Step 6: Create a content deployment job

Now that you have created a content deployment path along which to deploy content, you can create a job to do the actual deployment. The job will contain the schedule along with other settings.
1. On the Manage Content Deployment Paths and Jobs page, click New Job.
2. On the Create Content Deployment Job page, specify the Name and Description of the deployment job and the Path.

Step 7: Deploy the source site

Next, you will deploy the source site so that the source and destination sites will be in sync.
1. On the Manage Content Deployment Paths and Jobs page, on the Deployment Job menu, click Run Now.
2. Refresh the page until the job Status is Completed.
3. Browse to http:///sites/target, where is the name of your server, to view the destination site. Notice that the title of the site is the same as the source site, and even though you initially applied the empty site template, there is now content in the site.

Thats it!

Also See : Introduction to Content Deployment

How to Copy files from one sitecollection to other in sharepoint 2010

Copying files from one site collection to other can be done using Content deployment feature of SharePoint 2010. You can do this either manually or on a predetermined schedule.

Some Important things to Note :
1. Content deployment is a one-way process – Content is copied from a source site collection to a destination site collection.The content deployment feature does not support round-trip synchronization from source to destination and back again.

2. Creating new content or changing existing content on the destination site collection can cause content deployment jobs to fail.

3. You cannot deploy(copy) a site to the same content database as the source site – This is because all the GUIDs that are used to define sites, Web pages, lists, and items are transferred with the site when it is deployed to the destination. For this reason, you cannot deploy a site to the same content database as the source site.

4. The destination site collection must exist before you can deploy content to it, and it must be an empty site collection.You must not specify a template for the site collection. If a template is used to create the site collection, the content deployment job will fail.

5. Before you start any process, you must first configure the destination server for receiving incoming requests or to accept content deployment jobs. This can be done using Content deployment Settings Page.

6. Lastly, Content deployment paths and jobs are created and managed on the Manage Content Deployment Paths and Jobs page in Central Administration.

Now lets talk about the main components

Content deployment paths and jobs – There are two main components of content deployment.

1. The first is a content deployment path, which is a relationship between a source site collection and a destination site collection.
2. The second part is a content deployment job, which is associated with a path and is a collection of settings that are related to the schedule and scope that are followed in deploying that content.

In short, A job is associated with a path, and it defines the specific content that is to be deployed from the source to the destination and the schedule on which the deployment should occur. After you have created the content deployment path, you can specify jobs to run on that path.

The Overall Steps that you need to follow are :

1. Create a source site.
2. Create a new Web application.
3. Create a destination site collection.
4. Enable incoming content deployment jobs.
5. Create a content deployment path.
6. Create a content deployment job.
7. Deploy the source site.
8. Update the source site.
9. Deploy changes.
10. Check the destination site for changes.

Powershell for sharePoint 2010 Tutorial - Dig SharePoint

Some of the Important links that will help you learn PowerShell in SharePoint 2010.

Introduction – After installing SharePoint 2010 Products, the applicable Windows PowerShell cmdlets are available by using the SharePoint 2010 Management Shell, or by using the Windows PowerShell console. With the management shell, you can manage every aspect of SharePoint 2010 Products. You can create new site collections, Web applications, user accounts, service applications, proxies, and more. The commands from the management shell output SharePoint objects based on the Microsoft .NET
Platform. These objects can be applied as input to subsequent commands or stored in local variables for later use.

Permissions - Before you can use the management shell and the Windows PowerShell cmdlets, verify that you meet the following minimum requirements :
If you do not have membership in the SharePoint_Shell_Access role or WSS_Admin_WPG local group, use the Add-SPShellAdmin cmdlet. When the Add-SPShellAdmin cmdlet is used, the user is added to the WSS_Admin_WPG group in all front-end Web servers and is added to the SharePoint_Shell_Access role. If the target database does not have a SharePoint_Shell_Access role, the role is automatically created. Once the Add-SPShellAdmin cmdlet has been run, the user can run SharePoint 2010 Windows PowerShell cmdlets in a multiple-server farm environment.

Now lets come to our main topic the references!
Learning Windows PowerShell - There are several Windows PowerShell learning resources for SharePoint IT professionals who are not
familiar with Windows PowerShell.

Windows PowerShell Documentation on TechNet - This section of the TechNet Library contains Web copies of the core Windows PowerShell Get-Help topics. The section also has Web copies of the Windows PowerShell Getting Started document, the PowerShell.exe help, and a Windows PowerShell primer.

Scripting With Windows PowerShell -The home page for Windows PowerShell scripting learning resources.

Windows PowerShell Owner's Manual - Web-based guide for getting started with Windows PowerShell.

Windows PowerShell Quick Reference – Downloadable copy of the Quick Reference document installed with Windows PowerShell.

As you read these resources, consider that the following concepts and cmdlets are useful ones to learn
before using Windows PowerShell for SharePoint 2010 Products:
• Get-Command
• Get-Member
• Get-Help
• Aliasing
• Piping and the Pipeline in Windows PowerShell
• Cmdlet Parameter Sets
• Foreach-Object
• Where-Object

Hhow to Export\Import a webpart in Sharepoint 2010

To save the web part and use it again, you must export the web part and then import it to the other page. Following is the process to do that.

Export a Web Part -
Exporting a web part involves saving the web part's settings as a file to your computer. Not all web parts support this option, and in some web parts, the owner of the page
may choose to disable this option. In those cases, you should look in the options in that web part's properties tool pane to see whether the option to allow the web part to be exported is enabled.

Note – Not all web parts have this option; some web parts cannot be exported.

Steps are -
1. To export a web part that allows exporting, switch the page that has the web part to editing mode.
2. Once done, hover your mouse over the web part's title row.
3. Doing so exposes a small black triangle on the right corner of the title row. Click this triangle and expose the web part's drop-down menu.
4. If the web part allows exporting, the Export option appears on the menu.
5. After you select the Export option, a File Download dialog appears, allowing you to save the web part to your computer. You can save the file anywhere on your computer so that you can import it later.

Import a Web Part –

1. To import a web part that you have previously saved to your computer, open the page in editing mode and click the web part zone where you want the web part to be added, as if you were adding a new web part.
2. When the dialog with the list of web parts appears, instead of selecting a web part from the list, click the Upload a Web Part link shown under the Categories box.
3. When you click this link, you see a button to browse and a button to upload the file you have exported.

Query Web Service FAST serach sharepoint 2010 – Tutorial - Dig SharePoint

Query Web Service is the integration point for applications outside your SharePoint environment, such as standalone, non – web – based applications or Silverlight applications running in a browser. The Query web service is a SOAP – based web service and supports a number of operations, including:
Querying and getting search results Getting query suggestions Getting metadata (managed properties) The same schema is shared by SharePoint Search and FAST Search, and both products support the same operations. For querying, clients can easily switch the search provider by setting a ResultsProvider element in the request XML. A number of extensions are available for FAST Search, for example, refi nement results, advanced sorting using a formula, and issuing queries using the FAST Query Language.

Some other important things you need to know are  –
The Query RSS Feed –
Certain scenarios, such as simple mash – ups, may need only a simple search result list. The RSS feed is an alternative, lightweight integration point for supplying applications outside of SharePoint with a simple RSS result list. The Search Center — the default search frontend in SharePoint 2010 — includes a link to a query – based RSS feed. Switching the engine to the RSS format is done simply by setting a URL provider. Because it was designed to be simple, there are some limitations to what
can be returned and customized in the Query RSS feed. The user object models or web service integration scenarios are recommended for more advanced applications.

The Query Object Model
This is the lowest – level object model, used by the Federation Object Model, the Query web service, and the Query RSS feed. Both SharePoint Search and FAST Search support the KeywordQuery object in this object model. While the Federation OM returns XML (to web parts), the Query OM returns data types.

Sharepoint 2010 development tutorial videos - Dig SharePoint

If your looking for beginner level Tutorial Videos for sharePoint 2010. Please see Sharepoint 2010 Tutorial Videos. This post only contain links to advanced level SharePoint 2010 Tutorial video.

Display data using SPgridview in SharePoint 2010 -

Display data using SPgridview in SharePoint 2010

Retrieve data Using REST Sharepoint 2010 -

Retrieve data Using REST Sharepoint 2010

Create Custom Site column in Visual Studio 2010  in SharePoint 2010 -

Create Custom Site column in Visual Studio 2010  in SharePoint 2010

Create Custom Content Type using Visual Studio 2010 in SharePoint 2010 -

Create Custom Content Type using Visual Studio 2010 in SharePoint 2010

Create Custom Field Types using Visual Studio in SharePoint 2010 -

Create Custom Field Types using Visual Studio in SharePoint 2010

Sharepoint 2010 Tutorial Videos - Dig SharePoint

SharePoint 2010 Development Introduction Video
- In this video Paul Andrew talsk about whats new in SharePoint 2010 for
developers and also tells you about new solution and packaging methods in
sharePoint 2010.

SharePoint
2010 Out-of-box Webparts - In this Video you will see how to use
Out-of-Box Sharepoint 2010 webparts.
See the Video at SharePoint
2010 build-in Webparts


Create
Visual WebPart in SharePoint 2010 - In this Video presenter will show you
how to create a simple Visual WebPart in SharePoint 2010. If you need the
Introdcution to the WebParts in SharePoint 2010, please see  @ Sharepoint 2010 WebPart Tutorial
See the video at Visual
WebPart for SharePoint 2010.


Create a Sandbox Soltuion WebPart - In this
Video you will learn how to create a new
custom webpart as a Sandboxed
solution.
See the Video Sandbox
Soltuion in SharePoint 2010


Application Pages, Ribbon and Silverlight in
SharePoint 2010 - In this Video you will learn what are the changes in
application pages or _layouts pages in sharepoint 2010 and also how do you
customize the Ribbon.
See Video at : Application
pages and Ribbon in SharePoint 2010


Creating BCS solutions With SharePoint 2010 -
This will talk about BCS (Business Connectivity Services) solutions, What they
are and how do make the BCS VS solutions.
See the video : BCS
in SharePoint 2010

Sharepoint 2010 WebPart Tutorial - Dig SharePoint

Webparts as you know are Reusable components that can be deployed and added to
many different sharepoint site pages. In this post we will talk about custom and
Out-of-box webparts in SharePoint 2010.

In sharePoint 2010 we can create
two kind of custom WebParts :

1. Visual
WebPart - While creating a Visual webpart you will have a design
interface available with you, where you can simply drag and drop checkboxes,
labels or your own custom controls to make up the webpart UI. To add the
business logic, a code behind file is also attached to the
webpart.

Technically, a Visual webpart in SharePoint 2010 is a ascx User
Control that is hosted inside a standard asp.net webpart. If you notice that the
webpart class does not now inherit form a
Microsoft.SharePoint.webpartpages.webparts or System.Web.UI.WebControls.WebParts
instead it inherits from UserControl namespace.

2. Standard AsP.NET WbeParts - Here you will
have to build uo your user interface and logic in a class file. Unlike, visual
webpart standad asp.net webparts in SharePoint 2010 does not gives you any drag
and drop design surface for developing WebPart UI. This type of webpart Inherits
from Standard ASP.Net webpart instead of UserControl or
SharePoint.webpart.


WebPart Packaging
- Visual Studio 2010 package and deploy webparts when you press Clt + F5.
It has a packaging and deployment processor which will create the needed
solution package for your webpart and will deploy it in your sharepoint site.
You can then add the webparts on any sharepoint site page from webpart
gallery.

See WebPart examples at this Video :
SharePoint
2010 webparts

Lets talk about Out-of-Box webparts - In sharePoint
2010 many new Out-of-Box webparts are available for better representation of
SharePoint data. You will initially see few categories in the Add Webpart pane
but if you go to Site Actions->galleries and WebParts, you can add various
other webparts available into your categories.

How to Create scorecard in dashboard designer sharepoint 2010 - Dig SharePoint

Scorecards are dashboard items that show performance for one or more metrics. Scorecards compare actual results to specified goals and express the results by using graphical indicators. A scorecard resembles a table that usually has Target and Actual value columns and one or more key performance indicators (KPIs).
When you create a scorecard by using Dashboard Designer, you can select from several different methods:

* You can use a wizard to set up a basic scorecard. This is useful when you are new to Dashboard Designer and you do not have many existing dashboard items that you can reuse. This method is also useful when want to quickly and easily create a scorecard.When you use a wizard to create a scorecard, you start by selecting the kind of data source that will be used by at least one KPI in the scorecard. You use the wizard to create the scorecard, and then you finish configuring the scorecard in the workspace.

* You can create a blank scorecard and then manually add the KPIs and other items that you want to use in the scorecard. This is useful when you or other dashboard authors have already created one or more KPIs.

Method 1 -
When you use a wizard, you begin by selecting a template. The template that you select corresponds to the kind of data source that you plan to use for your scorecard.

To select a scorecard template
1.  Identify the kind of data source that you want to use for your scorecard. The data source that you want to use will help you determine which scorecard template.
2.  Make sure that the data source that you want to use is available. Do this by using the following procedure:

1. In Dashboard Designer, click the Home tab, and then click Refresh.
2. In the Workspace Browser, click Data Connections.
3. In the center pane of the workspace, review the list of data sources on the Server and Workspace tabs.
4. Confirm that the data source that you want to use is available. If it is not listed, then you might have to create a data connection.

5. Create a blank scorecard by using Dashboard Designer -When you create a blank scorecard by using PerformancePoint Dashboard Designer, you create an empty scorecard that has no key performance indicators (KPIs) or other information. Then, you configure the scorecard to add the KPIs and other items that you want to display in the scorecard. You would typically create a blank scorecard when you and other dashboard authors have already created KPIs.
To create a blank scorecard

1. In Dashboard Designer, in the Workspace Browser, click PerformancePoint Content.
2. On the Create tab, in the Dashboard Items group, click Scorecard.
3. Depending on whether Dashboard Designer is configured to use a wizard to create scorecards, one of the following actions occurs:
* The Select a Scorecard Template dialog box opens.  If this occurs, select the Blank Scorecard template. Do this by using the following procedure:
1. In the Select a Scorecard Template dialog box, in the Category section, click Standard.
2. In the Template section, click Blank Scorecard.
3. Click OK to close the Select a Scorecard Template dialog box, and then proceed to Step 4.
A blank scorecard opens for editing.
If this occurs, proceed to Step 4.
4. In the center pane, click the Properties tab.
5. In the Name box, type the name that you want to use for the scorecard.
6. (This step is optional.) To specify a location for the scorecard, click the Display Folder button, and then select or create a folder.
7. In the Workspace Browser, right-click the scorecard, and then click Save.
8. After you and other dashboard authors have created scorecards by using PerformancePoint Dashboard Designer, you can then edit those scorecards to display information in a particular way. For example Add items, such as key performance indicators (KPIs) or dimension members to a scorecard.

Related Post - How to Create KPI in Dashboard Designer sharepoint 2010

How to Create KPI in Dashboard Designer sharepoint 2010

In continuation with my earlier post about How to create a blank scorecard in this post i will detail some steps about how to create a KPI.

In PerformancePoint Services in Microsoft SharePoint Server 2010, a key performance indicator (KPI) is a scorecard element that shows at a glance whether performance is on- or off-target for a particular metric. KPIs can vary greatly in their appearance and complexity, but KPIs typically calculate how actual values compare to target values and indicate performance by using a graphical indicator.A PerformancePoint scorecard can include one or more KPIs.

There are two ways to create a KPI –

Import a KPI - When you import a KPI, you use the Create a Scorecard wizard in Dashboard Designer. The wizard enables you to copy one or more KPIs from the database server into Dashboard Designer and then configure those KPIs. Select this method when you are creating a scorecard by using the wizard or when you want to import existing KPIs from a data source.
Create a KPI – When you create a KPI, you use the Create a KPI wizard in Dashboard Designer. Select this method when you want to create a KPI separate from creating a scorecard or when you want to create and configure a new KPI that you define.

To import a KPI by using the Create a Scorecard wizard -

1. In Dashboard Designer, in the Workspace Browser, click PerformancePoint Content.

2. In the ribbon, click the Create tab.

3. In the ribbon, in the Dashboard Items group, click Scorecard. The Select a Scorecard Template dialog box opens.

4. In the Category pane, click All. Then, in the Template pane, click one of the following templates:
* Analysis Services
* Excel Services
* Excel Workbook
* SharePoint List
* SQL Server Table
The template that you select corresponds to the kind of data source that you plan to use for the scorecard. For example, if you want to import a KPI that is stored in an Analysis Services database, select the Analysis Services template. After you have selected the template that you want to use, click OK.

5. In the Select a data source page, review the list of data sources on the SharePoint Site and Workspace tabs. Select the data source that you want to use, and then click Next.

6. If you selected the Analysis Services scorecard template, the Select a KPI Source page opens. (Otherwise, proceed to step 7.)
Select the Create KPIs from SQL Server Analysis Services measures option, and then click Next.

7. In the Select KPIs to Import page, select the KPI (or KPIs) that you want to use by following these steps:
Click Add KPI. A KPI from the data source that you selected for the scorecard appears. Continue clicking Add KPI until you see the KPI (or KPIs) that you want to use. To remove any KPIs from the list, select a KPI and then click Delete Selected KPIs.Click Next.

8. On the Add Measure Filters page, click Next.

9. On the Add Member Columns page, click Next.

10. On the Locations page, confirm that the correct location is specified in the Create KPIs in list, and then click Finish.

To create a KPI by using the Create a KPI wizard -

1. In Dashboard Designer, in the Workspace Browser, click PerformancePoint Content.
2. In the ribbon, click the Create tab.
3. In the ribbon, in the Dashboard Items group, click KPI.
4. The Select a KPI Template dialog box opens.
5. In the Template pane, select either the Blank KPI or Objective template, and then click OK.
* Select Blank KPI to create a single KPI.
* Select Objective to create a KPI that serves as a heading for a group of other KPIs.
The KPI that you have created opens for editing in the workspace where you can configure it.

How to Create viso diagram webpart Sharepoint 2010 – Tutorial - Dig SharePoint

Visio has some great "mash-up" capabilities, which enable it to easily be integrated into SharePoint 2010. To create a simple Visio Web part diagram, follow these steps:

1. Open Visio 2010. Click File ➪ New and then select the ITIL Diagram.

2. Create a diagram.

3. When you finish building the diagram , click the Backstage tab (the tab on the upper-left part of the Visio document) and then click Share. At the bottom of the Backstage view, select Web Diagram. Note that, after you've finished, when you click Save As, there is an Options button that you can click to see
what pages (if you have multiple pages in your Visio diagram) will be published to Visio Services.

4. Next, upload the Visio diagram to a document library.

5. Click the drop-down menu beside the uploaded document and select View Properties.

6. Select Copy Shortcut.

7. Navigate to the location where you want to add the diagram on your SharePoint site, and then click Site Actions ➪ Edit Page.

8. Click "Add a web part" (or, if you're on a wiki page, click the Insert tab and select Web Part).

9. Navigate to the Office Client Applications, and select Visio Web Access Web part.

10. Once it is added, you can edit the Web part using the tool pane. Specifically, you want to copy the shortcut to the Visio diagram into the Web Drawing URL file and then click Apply. The Visio Web drawing will now be rendered in your SharePoint site.

How to Create infopath form in Sharepoint 2010 -Tutorial - Dig SharePoint

InfoPath forms are easy to create and deploy to SharePoint. To create an InfoPath form, follow these steps:

1. Create a Custom list called "Customers" in your SharePoint site. Create three columns entitled Contact Name, Email, and Phone Number. Make all of the fields of type "Single line of text."

2. Open InfoPath 2010 and click File.

3. Double-click the SharePoint List template.

4. In the Data Connection Wizard, enter the URL for the SharePoint site and click Next.

5. Click the Customize an Existing SharePoint List radio button, and then select the Customers list.

6. Accept the default name for the connection on the next step of the wizard, and click Finish.

7. When complete, InfoPath will generate a form that maps to the fields you created in your Customers list.

8. You can click Preview to preview the form, or you can click the Quick Publish button (to the right of the Save icon) to publish the form to SharePoint. When it is published, InfoPath will prompt you with a successful publish message.

9. To use the form in SharePoint, navigate to your SharePoint site and click Site Actions ➪ Edit Page.

10. Click "Add a web part." Click the Office Client Applications category, and select InfoPath Form Web Part. Click Add.

11. SharePoint exposes the default InfoPath capabilities, but you need to map it to a particular form. To do this, select "Click here to open the tool pane."

12. In the "Lists or Library" drop-down, select the Customers list and leave all of the other default options. Click OK. SharePoint renders the InfoPath form you created in the SharePoint Web part.

13. To use the InfoPath form, click the Forms Edit tab. Add some data to the form and click Save. The data you enter into the form will be saved in the Contacts list.

Sandbox Vs Farm level solutions Sharepoint 2010 - Dig SharePoint

Farm Level Solutions -
Farm-level solutions are scoped at the SharePoint farm level, so they have full-trust access to all the resources and functionality in SharePoint.

Application build using Farm level –
All SharePoint applictaions can be deployed with Farm level scope.

Sandboxed Solutions  –
Sandboxed Solutions are solutions that run in the context of a site collection. Sandboxed solutions are restricted.

Application build using Sandboxed Solutions –
They cannot connect to resources that are not on the local server, access a database, call unmanaged code, write to the system disk, or access resources in a different site collection. Sandboxed solutions, though,do have the capability to monitor and shut down applications, should they have any performance issues.