Search results matching tag 'Infragisticsgistics Grid control'

Using Infragistics Components for SharePoint Data in Silverlight Applications

mmateev — Tue, 21 Feb 2012 17:42:00 GMT

Today developers often need to use data from SharePoint in their applications.

When talking about Silverlight and SharePoint data we have two cases:

Silverlight application in the context of SharePoint (as a part of ASP.Net Web Part).
Silverlight application outside the context of SharePoint (such as blankets application that simply accesses SharePoint data).

This post is about the second approach (Silverlight application outside the context of SharePoint). Often in today's Line of Business applications applications access the SharePoint sites, and other resources in them as lists and libraries.

In general developers could use several data access technologies to maintain SharePoint data:

SharePoint web Services
Silverlight Client Object Model
Data Services Client Model
OWSSRV.DLL (The ISAPI extension that implements SharePoint Team Services functionality)

Understanding the Client Object Model

The Client Object Model fundamentally is a new Windows Communication Foundation (WCF) SharePoint service called Client.svc and three proxies: .NET CLR, Silverlight, and JavaScript. You program against the client proxies just as you do with any service. Calls to and from the server are sent in batches to increase network efficiency.

The Client Object Model is really three separate object models, one for the .NET CLR, one for Silverlight, and one for JavaScript. The .NET CLR version is used to create applications such as WinForms, Windows Presentation Foundation (WPF), and console applications, as well as PowerShell scripts. The Silverlight version works with both in-browser and out-of-browser Silverlight applications. The JavaScript version enables your Ajax and jQuery code to call back to SharePoint.

SharePoint 2010 ships with Silverlight Object Model that simplifies working with SharePoint data within Silverlight components. Thanks to the new object model you no longer have to create and deploy custom services to retrieve data from SharePoint. Out of the box the Silverlight Object Model encapsulates calling standard SharePoint WCF Services which makes it extremely easy for you as a developer to create Silverlight components that communicate with SharePoint. Although working with the Silverlight Object Model is pretty easy, there is one thing that you have to keep in mind while developing for anonymous users.

In this article, we will see how to use the Silverlight Client Object Model with SharePoint 2010 data and how visualize this data with Infragistics Silverlight components (XamGrid and XamDataTree).

Prerequisites

1. Client side:

Visual Studio 2010 SP1
Microsoft Silverlight Tools for Visual Studio 2010 SP1
SharePoint 2010 Client Object Model Redistributable
NetAdvantage for Silverlight Vol.11.2

2. Server side:

SharePoint Foundation 2010 or a higher license
SharePoint settings:
User credentials. Silverlight applications runs under user rights. We should have for these users permissions in SharePoint
ClientAccessPolicy.xml

If you need to use cross domain calls (Silverlight application is running in your domain but calling a service on other domain) then you must have to use clientaccesspolicy.xml file. Because, cross domain communication requires protection against multiple security threats. To elaborate a little, let assume that your Silverlight application is running on http://abcintranet.com/som and this application is trying to call a service on http://xyzintranet.com/pom/service.svc. This request will be prevented as there may be malicious Silverlight controls which are trying to perform an unauthorized operation by calling the service. Silverlight 4 supports two kinds of policy files for cross domain access: Place a ClientAccessPolicy.xml file at the root location of the domain where the service is hosted to configure the service to allow cross-domain access. Place a CrossDomain.xml file at the root location of the domain where the service is hosted. The file must mark the entire domain as public. In our case, we have to add a ClientAccessPolicy.xml file at the root location of the domain. Create the file with the following xml:

<?xml version="1.0" encoding="utf-8" ?>  

<access-policy>   

      <cross-domain-access>

            <policy>       

                  <allow-from http-request-headers="*">

                         <domain uri="*" /> 

                  </allow-from>

                  <grant-to>

                         <resource path="/" include-subpaths="true" /> 

                  </grant-to>

           </policy>

     </cross-domain-access>

</access-policy>

Anonymous user credentials for some methods

Silverlight Object Model uses anonymous users to access SharePoint data. Unfortunately SharePoint needs to remove restrictions on some methods, called under anonymous user from Client Object Model API. Here you could find the the solution : http://blog.mastykarz.nl/inconvenient-silverlight-object-model-anonymous-users/

GetItems method has been enabled by the administrator

Preparations:

Lets create a Silverlight project and add a few references to the following libraries:

Microsoft.SharePoint.Client.Silverlight.dll.
Microsoft.SharePoint.Client.Silverlight.Runtime.dll.

You can find these APIs under: “C:\Program Files\Common Files\Microsoft Shared\SharePoint Client\”

Add a references to NetAdvantage for Silverlight libraries:

InfragisticsSL5.v11.2.dll
InfragisticsSL5.Controls.Grids.XamGrid.v11.2.dll
InfragisticsSL5.Controls.Menus.XamDataTree.v11.2.dll

Add in the main Silverlight page Infragistics XamGrid and XamDataTree. Silverlight Data Tree is used do display all SharePoint items in specified URL. Infragistics Silverlight Grid is used to display items from a specific SharePoint list.

<Grid>

     <Grid.ColumnDefinitions>

         <ColumnDefinition Width="400"/>

         <ColumnDefinition/>

     </Grid.ColumnDefinitions>

     <ig:XamDataTree x:Name="xamSpListTree" NodeLineVisibility="Visible" ActiveNodeChanged="XamSpListTreeActiveNodeChanged">

         <ig:XamDataTree.SelectionSettings>

             <ig:TreeSelectionSettings NodeSelection="Single" />

         </ig:XamDataTree.SelectionSettings>

         <ig:XamDataTree.ExpandedIconTemplate>

             <DataTemplate>

                 <Image Source="/AccessSharePoint;component/Images/country.png"/>

             </DataTemplate>

         </ig:XamDataTree.ExpandedIconTemplate>

         <ig:XamDataTree.CollapsedIconTemplate>

             <DataTemplate>

                 <Image Source="/AccessSharePoint;component/Images/country2.png"/>

             </DataTemplate>                    

         </ig:XamDataTree.CollapsedIconTemplate>

         <ig:XamDataTree.GlobalNodeLayouts>

             <ig:NodeLayout Key="ItemsLayout" TargetTypeName="ListInfo" DisplayMemberPath="Title">

  

             </ig:NodeLayout>

             <ig:NodeLayout Key="CreateDateLayout" TargetTypeName="ItemDetails"  DisplayMemberPath="Created">

                 <ig:NodeLayout.ItemTemplate>

                     <DataTemplate>

                         <StackPanel Orientation="Horizontal">

                             <Image Source="/AccessSharePoint;component/Images/News.png"/>

                             <TextBlock Text="Created:"/>

                             <TextBlock Text="{Binding Data.Created}"/>

                         </StackPanel>

                     </DataTemplate>

                 </ig:NodeLayout.ItemTemplate>

             </ig:NodeLayout>

         </ig:XamDataTree.GlobalNodeLayouts>

     </ig:XamDataTree>

     <ig:XamGrid Grid.Column="1" x:Name="xamSpListItemsGrid" Margin="10"></ig:XamGrid>

 </Grid>

Add a button and attach an event handler, that receives all list in the specified SharePoint site.

<Button Content="Load Data from SharePoint"  Height="23" 

HorizontalAlignment="Left" Name="btnLoadData" VerticalAlignment="center" 

Width="165" Click="BtnLoadDataClick" />

Display SharePoint lists

C# code: add several variables used to maintain the SharePoint data.

private ClientContext _clientContext = null;

private ListCollection _collList;

private List _oList = null;

private ListItemCollection _oListItems = null;

private Web _oWebSite = null;

private const string Url = http://[SharePointSiteUrl];

Create a hierarchy of viewmodels that will use to place SharePoint data.

#region public class BaseViewModel

/// <summary>

/// Base view model. Contains implementation of the INotifyPropertyChanged interface

/// </summary>

public class BaseViewModel : INotifyPropertyChanged

{

  

    #region INotifyPropertyChanged Members

  

    public event PropertyChangedEventHandler PropertyChanged;

  

    #endregion

  

    protected void OnPropertyChanged(string propertyName)

    {

        PropertyChangedEventHandler handler = PropertyChanged;

        if (handler != null)

            handler(this, new PropertyChangedEventArgs(propertyName));

  

    }

}

#endregion //public class BaseViewModel

  

#region public class ListInfo

public class ListInfo : BaseViewModel

{

    //public string Title { get; set; }

  

    #region Title

  

    private string _title;

  

    public string Title

    {

        get { return _title; }

        set

        {

            if (_title != value)

            {

                _title = value;

                OnPropertyChanged("Title");

            }

        }

    }

    #endregion //Title

  

    #region Description

  

    private string _description;

  

    public string Description

    {

        get { return _description; }

        set

        {

            if (_description != value)

            {

                _description = value;

                OnPropertyChanged("Description");

            }

        }

    }

    #endregion //Description

  

  

    #region ItemDetails

  

    private IEnumerable<ItemDetails> _itemDetails;

  

    public IEnumerable<ItemDetails> ItemDetails

    {

        get { return _itemDetails; }

        set

        {

            if (_itemDetails != value)

            {

                _itemDetails = value;

                OnPropertyChanged("ItemDetails");

            }

        }

    }

    #endregion //ItemDetails

} 

#endregion //public class ListInfo

  

#region public class ItemDetails

  

public class ItemDetails : BaseViewModel

{

    #region Created

  

    private string _created;

  

    public string Created

    {

        get { return _created; }

        set

        {

            if (_created != value)

            {

                _created = value;

                OnPropertyChanged("Created");

            }

        }

    }

    #endregion //Created

}

 #endregion public class ItemDetails

Implement an event handler that creates a ClienContext instance and gets all list from the specified SharePoint page.

#region BtnLoadDataClick

 private void BtnLoadDataClick(object sender, RoutedEventArgs e)

 {

     using (var clientContext = new ClientContext(Url))

     {

         _oWebSite = clientContext.Web;

         _collList = _oWebSite.Lists;

         clientContext.Load(_collList);

         clientContext.ExecuteQueryAsync(OnQuerySucceeded, OnQueryFailed);

     }

 }

 #endregion //BtnLoadDataClick

#region OnQuerySucceeded

private void OnQuerySucceeded(object sender, ClientRequestSucceededEventArgs args)

{

    //DisplayLists method converts the List items to Class Properties

    //and binds them to the Silverlight User Interface.

    Dispatcher.BeginInvoke(new Action(DisplayLists));

}

#endregion //OnQuerySucceeded

Note: Silverlight query model is asynchronous and must pass delegates for callback methods as parameters in the ExecuteQueryAsync(OnQuerySucceeded, OnQueryFailed) method.
Also to update the Silverlight UI use delegate using the Dispatacher object of the thread that created the UI by calling BeginInvoke() method.

Create a collection that implements IQuerable<ItemDetails> interface and set it to the XamDataTree ItemsSource property:

#region DisplayLists

private void DisplayLists()

{

  

    var list = _collList.ToList().Select(s => new ListInfo 

    { Title = s.Title, Description = s.Description, 

        ItemDetails = new ObservableCollection<ItemDetails> { new ItemDetails { Created = s.Created.ToShortDateString() } } 

    });

  

    xamSpListTree.ItemsSource = list;

}

#endregion

Run the application

Click the “Load Data from SharePoint” button to receive all SharePoint lists in the requested page.

Now you have in the Infragistics Silverlight DataTree all lists from the specified URL.

Display SharePoint list items

The next step is to display items from a specified SharePoint list.

Add an event handler that gets all items form a SharePoint list and attach it to the DataTree event, named ActiveNodeChanged.

#region XamSpListTreeActiveNodeChanged

private void XamSpListTreeActiveNodeChanged(object sender, Infragistics.Controls.Menus.ActiveNodeChangedEventArgs e)

{

    var info = e.NewActiveTreeNode.Data as ListInfo;

    if (info != null)

    {

        var list = ((ListInfo)e.NewActiveTreeNode.Data);

        ShowListItemTitles(list.Title);

  

    }

}

#endregion //XamSpListTreeActiveNodeChanged

#region ShowListItemTitles

private void ShowListItemTitles(string listName)

{

    _clientContext = ClientContext.Current;

    if (_clientContext == null)

    {

        _clientContext = new ClientContext(Url);

    }

    using (_clientContext)

    {

        _oWebSite = _clientContext.Web;

        _oList = _oWebSite.Lists.GetByTitle(listName);

        _oListItems = _oList.GetItems(CamlQuery.CreateAllItemsQuery());

        _clientContext.Load(_oListItems);

        _clientContext.ExecuteQueryAsync(OnListItemsQuerySucceeded, OnQueryFailed);

    }

}

#endregion //ShowListItemTitles

#region OnListItemsQuerySucceeded

  private void OnListItemsQuerySucceeded(object sender, ClientRequestSucceededEventArgs args)

  {

      //DisplayListsItems method converts the List items to Class Properties

      //and binds them to the Silverlight User Interface.

      Dispatcher.BeginInvoke(new Action(DisplayListsItems));

  }

  #endregion //OnListItemsQuerySucceeded

Create a collection that implements IQuerable<ListInfo> interface and set it to the XamGrid ItemsSource property:

#region DisplayListsItems

private void DisplayListsItems()

{

    try

    {

        var list = _oListItems.ToList().Select(s => new ListInfo

                                                        {

                                                            Title = s["Title"].ToString(), Description = ""

                                                        });

        xamSpListItemsGrid.ItemsSource = list;

    }

    catch (Exception ex)

    {

        MessageBox.Show("Error:" + ex.Message);

    }

  

}

#endregion //DisplayListsItems

Run the sample application again. When you select the tree node all list items are displayed in the Infragistics Silverlight Grid

Conclusion

In this article, we have seen how to use ‘Silverlight Client Object Model’ to fetch the SharePoint Lists and List data when the Silverlight application runs outside the SharePoint context. In this blog are mentioned required settings to be possible to maintain SharePoint data.

Source code you could download here.

How to Upgrade LightSwitch Applications from NetAdvantage Vol.11.1 to Vol.11.2

mmateev — Sun, 06 Nov 2011 21:42:00 GMT

NetAdvantage for LightSwitch Vol.11.2 is coming next days. This is an innovative product with a new Infragistics Grid control for LightSwitch and improvements for existing controls.

This blog is about how to upgrade existing Visual Studio LightSwitch projects with NetAdvantage Vol.11.1 extensions to new 11.2 release components.

Procedure for upgrade

To be possible to upgrade your LightSwitch project you should follow these steps:

1. Install correctly NetAdvantage for LightSwitch 11.2

Uninstall NetAdvantage for LightSwitch 11.1
Install NetAdvantage for LightSwitch 11.2

2. Upgrade to release 11.2 the existing LightSwitch projects with NetAdvantage for LightSwitch 11.1

Create a new “dummy” LightSwitch project where to include new Infragistics LightSwitch Extensions from 11.2 Release.
Upgrade ExtensionEsseblies section in all Config.xml files in “ClienGenerated” project from existing LightSwitch solution with the same section from the new “dummy” project.
Delete all existing “obj” folders in “Client”, “Common” and “Server” project from existing LightSwitch solution

3. Run the updated LightSwitch application.

Install correctly NetAdvantage for LightSwitch 11.2

More information how to do that you could find here:

Upgrade to release 11.2 the existing LightSwitch projects with NetAdvantage for LightSwitch 11.1

Try to run the existing LightSwitch applications, created with NetAdvantage for LightSwitch 11.1.

Open the existing project

Ensure that you still have included Infragistics LightSwitch Extensions.

Run the excising project. You will receive this error message.

Create a new “dummy” LightSwitch project where to include new Infragistics LightSwitch Extensions from 11.2 Release.

Create a new LightSwitch project.

Add to this project Infragistics LightSwitch Extensions (Visual Studio LightSwitch will use the latest (Release 11.2) extensions).

Open the LightSwitch solution folder with Windows Explorer and open “ClientGenerated” project

Upgrade ExtensionEsseblies section in all Config.xml files in “ClienGenerated” project from existing LightSwitch solution with the same section from the new “dummy” project.

Open Config.xml files in “ClientGenerated” and “ClientGenerated\Bin\Debug” folders.

Change the content of “ExtensionAssemblies” section in these files with the content of the same section from Config.xml file from a “dummy” LightSwitch project.

“ExtensionAssemblies” section with 11.1 Release assemblies

<ExtensionAssemblies>

  <ExtensionAssembly>Microsoft.LightSwitch.Extensions.Client, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35</ExtensionAssembly>

  <ExtensionAssembly>Infragistics.LightSwitch.Extensions.Client.Design, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>Infragistics.LightSwitch.Extensions.Client, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>Infragistics.LightSwitch.Extensions.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Charts.XamGauge.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Editors.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Charts.XamDataChart.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Maps.XamMap.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Editors.XamSlider.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Menus.XamMenu.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Menus.XamOutlookBar.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Lists.XamTileView.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.DataVisualization.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>Microsoft.LightSwitch.SdkProxy, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Interactions.XamDialogWindow.v11.1, Version=11.1.20111.1000, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

   <ExtensionAssembly>System.Xml.Linq, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35</ExtensionAssembly>

  <ExtensionAssembly>System.ComponentModel.Composition.Initialization, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35</ExtensionAssembly>

<ExtensionAssembly>Microsoft.LightSwitch.Extensions.Design.Client, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35</ExtensionAssembly></ExtensionAssemblies>

“ExtensionAssemblies” section with new 11.2 Release assemblies

<ExtensionAssemblies>

  <ExtensionAssembly>Microsoft.LightSwitch.Extensions.Client, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35</ExtensionAssembly>

  <ExtensionAssembly>Infragistics.LightSwitch.Extensions.Client.Design, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>Infragistics.LightSwitch.Extensions.Client, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>Infragistics.LightSwitch.Extensions.Common, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Charts.XamDataChart.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Charts.XamGauge.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Grids.XamGrid.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Editors.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Maps.XamMap.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Editors.XamSlider.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Menus.XamMenu.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Menus.XamOutlookBar.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Lists.XamTileView.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.DataVisualization.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>Microsoft.LightSwitch.SdkProxy, Version=10.0.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35</ExtensionAssembly>

  <ExtensionAssembly>InfragisticsSL4.Controls.Interactions.XamDialogWindow.v11.2, Version=11.2.20112.1008, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB</ExtensionAssembly>

  <ExtensionAssembly>System.ComponentModel.Composition.Initialization, Version=2.0.5.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35</ExtensionAssembly>

</ExtensionAssemblies>

Delete all existing “obj” folders in “Client”, “Common” and “Server” project from existing LightSwitch solution

Delete existing folders, shown below.

Run the updated LightSwitch application.

Rebuild and run the updated LightSwitch application.
Enjoy the fully working updated application .

The exciting new NetAdvantage for LightSwitch Vol.11.2 will let you have fun when create LightSwitch applications. You can try it a few days. Follow news from Infragistics in http://infragistics.com/ and twitter: @infragistics for more information about new Infragistics products.