LightSwitch Filter Control For Visual Studio 11 Beta

LightSwitch Filter Control For Visual Studio 11 Beta

  • Comments 8

We’ve released a new version of the LightSwitch Filter control extension that is compatible with LightSwitch in Visual Studio 11. If you were using the previous version of this control and you want to upgrade your LightSwitch project to Visual Studio 11, first install this control. Then open the project in Visual Studio 2010 and unselect the extension from project properties extensions tab. Next open the project in Visual Studio 11 to upgrade your project. At this point you can re-select the Filter control extension.

Download: Filter Control for LightSwitch (Visual Studio 11)

Try it out and let us know if you run into issues by visiting the LightSwitch in Visual Studio 11 Beta Forum.


Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post
  • Hi,

    To build the solution, the lightswitch extensibility toolkit is required.



  • Where can I download the extensibility toolkit for VS11 beta?



  • Hi Markus,

    The VSIX is located in the Binaries folder and is ready to use. The extensibility toolkit for VS11 will be released next week.

  • Nice to hear :)

    Currently I get the information, that I can't install the extension on any installed product. I'm using VS11 Premium beta.

    VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.

  • I have installed the Filter Control for VS 2012 (Visual Studio 11).  I am having the same problem that MANY other people are having.  The error is:

    The data contract type 'FilterControl.Clause' cannot be serialized because the member '_clauseType' is not public. Making the member public will fix this error. Alternatively, you can make it internal, and use the InternalsVisibleToAttribute attribute on your assembly in order to enable serialization of internal members - see documentation for more details. Be aware that doing so has certain security implications

    This page discusses the error:

    I have attempted the suggestions in the page but cannot get past this error.  I have also tried the suggestion to make _clauseType Public, to no avail.  

    This error existed and in V1 of the control, for over 2 years now.  How can it be that it has not be dealt with and corrected in a second version.  I have never been able to get the Save function to work.  Note: It will show the Saved filter in the drop down, but as soon as you close the tab and reopen, it disappears.  

    This is an awesome control.  Please address the deficiencies.



  • Updated: Post 1 - Posting update in multiple parts due to character count restructions per message.

    Having both the _clauseType not public serialization error outlined in other messages  , and the one here where the save options checkbox was not on the Properties panel for the Advanced Filter Term control: , I updated the code as suggested, recreated the FilterControl.vsix, and reinstalled package as instructed.  But then using it in my target project would result in the same issues, as if I had not updated the extension at all.

    Reviewing the references in my target project for the Client and Server projects, I noticed that the references for the FilterControl dlls were being referenced to a subfolder of my target project named: ..\Visual Studio 2012\Projects\<target project>_Pvt_Extensions\FilterControl\Client\Reference for the Client project references, and ..\Visual Studio 2012\Projects\<target project>\_Pvt_Extensions\FilterControl_sav\Server\Reference for the Server project references.

    The updated dlls for the FilterControl are in my Filter Control project folder: ..\Visual Studio 2012\Projects\Filter Control\VB\FilterControl\FilterControl.Client\Bin\Release for the Client project

    \Visual Studio 2012\Projects\Filter Control\VB\FilterControl\FilterControl.Common\Bin\Release for the Common Project

    \Visual Studio 2012\Projects\Filter Control\VB\FilterControl\FilterControl.Server\bin\Release

  • Updated: Post 2

    I have noticed that every time I redeploy the FilterControl.vsix extension, the references in my target project get changed back to the <target project>\_PVT_Extensions subfolder structure which are not getting updated with deployment, so every time I have to change the references to the FilterControl project where the updated dlls are. I don't know why this is happening.  Would be good if someone could shed some light, but at least I know how to deal with it.

    So if you are making changes as described on this page and others to resolve the issues with the FilterControl and you are not seeing your changes, the above may be your issue.

    One last thing. The Save button on the control does save the criteria to an xml file in IsolatedStorage.  This is found under (Win7): C:\Users\<your user>\AppData\LocalLow\Microsoft\Silverlight\is...  Just navigate here and search for .reports.  The criteria is stored in a file named as: <screen name>.<collection name>.<control name>.reports You even view it and see the criteria you had specified.  Problem is that for some reason the extension will not retrieve this info after the screen is closed and reopened, nor does the drop down selection work correctly when you have saved different sets of criteria and try to switch your selection.  When I get a chance I will attempt to review the code and see if I can fix that.  For now I just disable the display of the Save options.

    It would be REALLY NICE if the author would address these issues.  The control is almost a necessity in many projects, fixing these deficiencies would escalate it from great to AWESOME.


  • Thank you for the wonderful filter control, Is there a plan to release a HTML client version?

Page 1 of 1 (8 items)