Hi,

As you might have noticed, I've posted quite a lot of blog posts regarding REST, OData & SharePoint and this, for a few years now! Since the REST API has been strongly extended in 2013, I've decided to build a demo SharePoint-Hosted App that you can deploy on a Office 365 environment or onpremise. This application is currentlhy handling quite a lot of operations:

Hi,

Update 04/2013 download my demo App at http://sptoolbasket2013.codeplex.com/

Similarly to my previous post, here is how to create a new hashtag inside of a microblog using the REST API from a SharePoint-Hosted App. Basically, you also have to address the ContentItems

Hi,

Update 04/2013 download my demo App at http://sptoolbasket2013.codeplex.com/

As I've struggled a lot to get this working and since I coudln't find the information anywhere, I've decided to create this blog post that shows how you can create a microblog entry in SharePoint 2013 for the connected user (from a SharePoint-Hosted App) using mentions.

Hi,

Update 04/2013 download my demo App at http://sptoolbasket2013.codeplex.com/

I've been facing a quite strange issue when using the new search REST API of SharePoint 2013 and you might be facing the same kind of issue so as it took me a while to figure out the problem, I thought it was a good idea to share both the problem and the fix.

Double quotes

First, the problem! When trying to pass double-quotes into the querytext parameter. If you do not use the KQL syntax, you don't have any problem. So, if I transmit this:

Hi,

Since I couldn't find any example on the web showing how to use CSOM from an App Part and since it's actually a bit more tricky than using CSOM from the App itself, I thought it could be a good idea to blog about that!

Hi,

If like me, you have several Office 365 accounts, you might be annoyed when deploying Apps from Visual Studio if you checked the option "Maintian my connection" when Visual Studio prompts you for credentials.

As soon as you do that, if you switch to another Office 365 instance, Visual Studio keeps sign in you with the previously entered credentials which results in a failure since you are not a member of this new instance and it does not you offer the option to sign in as a different user.

Hi,

One technique to localize InfoPath forms is explained on MSDN at the following address. Basically, the idea is to embed your resx files into the form, associate a default one with a XML data connection and then, dynamically load the right resx file corresponding to the current locale of your SharePoint site.

However, what this article doesn't mention and what I couldn't find anywhere is that there is a small trap when using this technique. Indeed, if you do as specified in the article, you'll be facing a silly error and switching from one language to another will just not work.

It will work from the InfoPath Designer previewer but not from Forms Services (once published to SharePoint). This problem is because the path determined by the FileLocation property is not the same...In InfoPath Designer, it contains only the name of your resx file, say myfile.en-US.resx while in Forms Services, this path is prefixed by x-soln:///...

Therefore, in your code, say the loading event, you'd better add this check and adjust the path accordingly:

if (Application.Environment.IsBrowser)
                    ResxFilePath = "x-soln:///";

dc.FileLocation = string.Concat(ResxFilePath,"your file","the dynamic locale",".resx");
dc.Execute();

Happy Coding!

Hi,

A while ago, I wrote a blog post about OData and recorded a video that shed some light on how to use one of the most unused built-in factory of SharePoint 2010.

This example was explaining how to leverage OData to query data stored in memory but it only demonstrated the "R" of CRUD operations. Before reading further this post, if you're not familiar with hosting WCF Data Services in SharePoint, I'd really recommend you to read my previous post since I won't go into details anymore.

In SharePoint 2010, this was quite difficult to implement because in many scenarios, the authentication providers associated with the web applications are still based on windows integrated security. When coming to data update. As described on MSDN, the article on WCF Services in SharePoint Foundation explains that the authentication scheme (anonymous/ntlm/kerberos) is added by SharePoint Foundation 2010 to the URL (and to the ID of the returned entities) to uniquely identity resources when multiple authentication protocols are enabled for a single webapp...(example anonymous/kerberos).

So far so good but what MSDN doesn't explain is that because of this, only the R of CRUD is working....To illustrate that, I've written a very basic service that is exactly the same between 2010 and 2013 but you'll see that the behavior is slightly different. This demo service allows to handle a list of courses with the support of CRUD operations. I'll share the code a bit later but first let's see how this service reacts on SharePoint 2010.

Hi,
I'll be writing a series of blog posts about leveraging .NET 4 within SharePoint 2013. As you might know already, SharePoint 2013 is now based on this .NET runtime version v4.0.30319 which actually allows developers to benefit from .NET 4 features. You couldn't do that with SharePoint 2010 which was still based on .NET runtime v2.0.50727.

AspNetCacheProfile

Hi,

I'll be writing a series of blog posts explaining how to develop mobile applications for SharePoint. Here is what is planned:

Mobile development for SharePoint - Part I

In this blog post, I'll be talking about the various possibilities to design mobile apps for SharePoint. You'll also see what's my preferred framework and I'll give some input on what are the key factors to take into account in order to make a choice. Of course, the choice will always be yours, my goal is just to give some tips.

Mobile development for SharePoint - Part II

In this blog post, I'll be talking about how to integrate the Sencha framework with SharePoint. I'll build a small app and will give the necessary explanations to understand the interactions between Sencha & SharePoint.

Mobile development for SharePoint - Part III (to be written)

I'll go a little bit further and show how to build a production ready Sencha Package and how to deploy it properly into SharePoint. I'll also go a little bit further regarding the interactions (read/write) operations from a mobile app and custom server-side components that are more suitable for communications purposes.

Mobile development for SharePoint - Part IV (to be written)

In this blog post, I'll be talking about how to integrate PhoneGap together with Sencha & SharePoint.

Mobile development for SharePoint - Part V (to be written)

In this blog post, I'll be talking about SharePoint 2013 specific features with regards to mobile development

Happy Coding!