Skip Ribbon Commands
Skip to main content

Data View Plus demo site

 Image Slideshow


A nice artistic picture of a suspension bridge


A close up macro photo of a dried leaf


A low view close up of the road ahead


Calm sea and rocks shot


Open field photo featuring a wooden shelter


Show on an ever green tree branch

 News Accordion

Want to add a new great-=looking view to your ebsite?

It's now easier than ever!

Simply copy its HTML source and paste it to the Data View Plus' Display Layout list, and that's it!​


No need to buy multiple web parts!

The Data View Plus web part includes out-of-the-box display layouts such as: Images Slideshow, Blog Spotlight, Task Accordion and many others!


Welcome to Data View Plus demo site!

Check-out this new super-flexible web part that enables you to create great-looking views without any need for XSL or SharePoint Designer!

Simply use standard HTML + Javascript and easilly share your custom-tailored views with other sites.​


to run this demo:
User: sb2013\testreader1
Password: pass@word1


Check-out the Data View Plus web part:
This page includes some examples of Data View Plus' built-in display layouts (which are fully customizable).
The display layouts are simply HTML templates, stored in a S.C shared list.
You can customize the existing templates and add new ones by simply editing/adding items to that list.
No need for messy XSL, just HTML and javascript (if you want).
This way you can implement any fancy display layout for your website or portal!
For more details visit the Data View Plus web part product page.
Got any questions?
Contact us at

 Blog Spotlight

2013-09-02 02:03:00

One solution to rule them all

My prezi is ready for SharePoint Saturday LA!

This session will be heavy on the visual studio live demo, hope that part goes well :)

But for the first part of the talk I thought I could use prezi to explain the challenge in building a solution that can be deployed on both SharePoint 2010 and 2013, without doubling the R&D efforts, QA efforts and overall maintenance.

We had a very long discussion about this in house, and we are still not entirely convinced this is the best solution to this problem, but it is the best we’ve got so far.

In the past we used to have 2 different solutions for each version of the product. This forced us to constantly sync code between the two versions, having to fix and retest every issue on both versions, which of course wasn’t done perfectly so we ended up with bugs that were fixed in one version only, features that were missing from the other version and basically it was very hard to maintain them.

Now, with the introduction of versioned root folders in SharePoint 2013 this have become a bit more challenging since the code would be different and target different folders in 2010 and 2013. While in server code its rather simple to test the version and use the right path, doing it in config xml files (like web part gallery icon, feature icon for example) is not something we can change in runtime.

This is why we came up with a set of tools that allows us to keep working on one solution, and producing 2 packages from the same source code in one build. One for SharePoint 2010 and the other for SharePoint 2013.

It didn’t take a long time before we then learned about the challenges in trying to debug this code on the SharePoint 2013 machine. Since it wasn’t build on that machine, and didn’t target the .NET framework 4 – this proved to be a bit more complex than what we expected.

0 commented on this post, click to open post in popup.

2013-09-01 21:59:52

Welcome to my blog!

This is where I'll be sharing my thoughts on topics that matter to me. Who knows... I might even share pictures, videos and links to other interesting stuff.

If I catch your interest, let me hear from you.

1 commented on this post, click to open post in popup.

2013-07-02 02:02:00

Upgrading SharePoint 2010 VS2010 solution to VS2012


I *was* going to write a long post on how to upgrade a SharePoint 2010 project and solution from VS2010 to VS2012,

based on past experience, we all know upgrading visual studio was a bit of a pain…

Well, it turns out the guys at Microsoft did such a great job – I have nothing to write about!!!

You open your VS2010 solution in VS2012, it runs a short upgrade and shows you the results, and boom – you got yourself an upgraded solution, everything works beautifully – and the best part is: the upgraded solution works on both VS2010 and VS2012 with no problems!

After upgrading about 10 different solutions, I am confident to say I have nothing else to say.

So… It’s snowing outside… Nice… Ok, ok – its not that kind of a blog…

Coming up soon: Upgrading your full trust solutions to SP2013 – here I do have some insight!

Have a wonderful week!

0 commented on this post, click to open post in popup.

2013-05-02 02:04:00

Fixing JavaScript Intellisense completion

If you are doing a lot of JavaScript development, especially if you are doing SharePoint Apps development, you have come to love the great script IntelliSense feature in visual studio.

This gives you great auto-completion on client side objects and members and makes your development experience much better, especially if you are used to all this goodness from working with other rich languages like C#:


This auto-completion is easy to achieve, all you need to do is add a “_references.js” file and reference all script libraries in it:


Now, once you do some real JavaScripting – you will soon start working with prototypes, defining classes and instances and so on.

Once inside a method, you will notice that if you define a member inside the method it will keep the autocomplete working:


But once you start declaring and using class members, you will see a strange warning message and autocomplete will show you all known objects instead of just the relevant members for this variable type:


“IntelliSense was unable to determine an accurate completion list for this expression.
The provided list contains all identifiers in the file.”

The reason for that is, that if you define the variable member before this point, in the class level, and set it’s value later on in a constructor or other init method – Visual Studio does not know the type of object this variable is going to be set to, so it cannot build the correct auto-complete list.

The fix is simple, you can tell visual studio what type of variable you are creating by adding a ///<field> comment just above it’s definition:


And now, when we try to access this member again – auto-completion will work as expected:


The tricky part is finding out the exact type name for each variable. here are a few that I found, hope it would come in handy:

/// <field name="context" type="SP.ClientContext">Current client context</field>
/// <field name="web" type="SP.Web">Parent web hosting the app</field>
/// <field name="webInfo" type="SP.WebInformation">Parent web info hosting hte app</field>
/// <field name="lists" type="SP.ListCollection">current web lists</field>
/// <field name="list" type="SP.List">selected list (by _ListName)</field>
/// <field name="view" type="SP.View">selected view (by _ViewName)</field>
/// <field name="defaultView" type="SP.View">default list view</field>
/// <field name="query" type="SP.CamlQuery">caml query to run</field>
/// <field name="listItems" type="SP.ListItemCollection">result list item collection</field>
/// <field name="listItem" type="SP.ListItem">current list item</field>

if you want to find out the type name of other returned objects, you can alert() their “.constructor.getName()” value.

Have a wonderful scripting day!

0 commented on this post, click to open post in popup.