itaysk

This is the fist post of a series about SharePoint 2010 Data Services: Part 1 (this one), Part 2, Part 3.

There a lot of confusion surrounding this topic of Data Services in SharePoint 2010. I think it’s mainly because of 2 reasons:

• SharePoint 2010 Beta 2 used the CTP version of Data Services, so there’s irrelevant documentation that don’t apply to SharePoint 2010 RTM.
• The Data Services platform itself was changed in the past few months.

In this post I will try to make some order by clarifying  the terms, and addressing some questions I have been getting lately.
I have to thank Gil Fink for helping me catch up with the Data Services world.

What are SharePoint 2010 Data Services?

SP2010 Data Services is about accessing data in SharePoint lists via REST services. It is based on the “WCF Data Services” technology.

What Are these “WCF Data Services”?

WCF Data Services is the technology that provides the ability to expose data from your application’s data source (not just SharePoint), via REST services, supporting all CRUD operations.

What is the difference between “WCF Data Services”, “ADO.net Data Services” and “Project Astoria”?

There is no difference. The project began under the name “Project Astoria”, Later, the project changed name to “ADO.net Data Services”. Now, with the finale release of Data Services, it is called “WCF Data Services”.

Why is the latest version called “ADO.net Data Services”, and not “WCF Data Services”?

In order to keep consistency with the current naming in .NET 3.5 and in the documentation, it is called “ADO.net Data Services”, But in future releases of .NET it will be called “WCF Data Services”. The point is that both terms are referring to the same thing.

Do I still need to install it if I have the latest .NET Framework?

Yes. Although “ADO.net Data Services 1.0” is integrated into .NET 3.5 SP1 (which is already installed on your machine), SharePoint support (along with other features) requires an update to the Data Services platform. That update used to be called
ADO.net Data Services 1.5 which is now just called “ADO.NET Data Services Update for .NET Framework 3.5 SP1”.

I found several articles and blog posts telling me to download and install ADO.net Data Services 1.5 CTP2

That’s probably because these articles are referring to SharePoint 2010 Beta 2, and not RTM. SP Beta 2 works ONLY with “ADO.net Data Services 1.5 CTP2”. SP RTM works ONLY with “ADO.net Data Services update to .NET 3.5 SP1”.

So, everything that was written for Beta 2 is not relevant for RTM?

Not necessarily. The usage is pretty much the same. What’s different are the installation guides pointing to the wrong version of Data Services.

Does these Data Services replace the services we used to know from SharePoint 2007?

Not quite. They are just another way to access data in SharePoint. You can still use Web Services, or Client Object Model to access SharePoint data. You still need those other services because Data Services are limited to SharePoint lists data only.

What is oData, And how does it relates here?

oData is a protocol developed by Microsoft for exchanging data in scenarios like this. It is being used in Data Services, and in other products as well. Sometimes you will hear people calling this “oData Services”

So how do I use this with SharePoint 2010?

The next posts in the series will guide you through installing, using and developing using SharePoint 2010 Date Services.

Office Web Apps are now fully functional and available on SkyDrive – Finale version – For free – To everyone.

I’m especially super exiting about One Note. I am using One Note a lot on my laptop, and now hopefully I can take my notes on the go with my mobile.

A very common scenario is to setup a SharePoint 2010 site to use both Windows Authentication, and Forms Based Authentication.

When a user opens your site, and click the “sign in” link, it get this page:

In this screen, the user needs to select “Forms Authentication” from the drop down list, and then it is being redirected to the FBA login page.

This step of choosing the authentication provider is not needed for everyone who is not the administrator, which is 99% of the users. Moreover, it might confuse the average user who doesn’t know, and doesn’t need to know, what is Windows and Forms Based Authentication.

A better solution would be to get the users directly into the FBA login page in the first place.

To do that, follow these steps:

1. Open Central Administration, and click “Manage web applications”.
   
2. Select the “Default” Zone.
3. Find the setting “Sign in Page URL”.
4. Select Custom Sign in page, and enter the address of the FBA sign in page: “/_forms/default.aspx”.
   
   
5. Confirm, and exit.

Now if you click the “Sign In” link, you are taken directly to the FBA sign in page.

There’s only one thing to consider here: what if you wanted to log in using Windows Authentication? This is usually relevant only for administrators, so they can manually browse to the windows login form using this URL: “/_windows/default.aspx”.