Monday, April 04, 2011

Unable to start Debugging. The Silverlight Developer Run time is not installed. Please install a matching version

If you have enabled the automatic updates to Silverlight , then you might face this issue if you download and update the version of Silverlight to the latest version.

Now when you will start your Silverlight application it will complain to you that it can’t start debugging as a matching version of Silverlight Developer Runtime is not installed.

This is not a big trouble its just that you have updated the copy of your Silverlight but the silverilght developer runtime also needs to be updated, microsoft should have given or mentioned it clearly somewhere while updating the Silverlight version but it hasn’t i.e why its difficult to find.

The simple solution is to go to www.silverlight.net and scroll down to the home page you will find a heading where you have “Developer runtime for Windows and OSX”. Under this section go and download the Windows developer runtime and install this runtime.

This will do the trick for you after installing that when you restart your visual studio you will find that you are able to debug your applications as you were doing earlier.

developerruntime

Also given below is the direct link to download the Silverlight Developer runtime http://go.microsoft.com/fwlink/?LinkID=188039

Happy Programming !!!!!!!!!!!!!!!!!!!!!!!!

Submit this story to DotNetKicks

del.icio.usSave Total0 users

Tuesday, March 15, 2011

Nuget Package Manager a very useful Visual Studio 2010 Extension

Sorry folks i have not penned any article since a long time as i was busy with life and wasn’t able to spare out much time for blogging, but from now i will try to post useful things as soon as i find a little time.

For today i found out this very useful Visual Studio 2010 Extension called Nuget Package Manager.

The beauty of this application is that you get a whole lot of third party dlls at your disposal to use in your application.

It will add the references to your application directly and there is no need to download the dlss and include in the project and secondly it will modify your web.config files also automatically.

So you just have to click like you did traditionally as “Add Service Reference” and you are ready to go…

For installing Nuget Package Manager Extension go to the link http://visualstudiogallery.msdn.microsoft.com/27077b70-9dad-4c64-adcf-c7cf6bc9970c

 

nugetpackagemanager

After installing nuget you will find it inside the Extension Manager in Visual Studio

nugetextensioninstalled

Now in whichever project you want to add any third party assembly you can right click on Reference and do an “Add Library Package Reference”. It will open the Library Package Reference manager for you.

 libraryreference

This manager will display all the available libraries and third party assemblies on Nuget, you can selecte any of those to be added into your project.

nuget

Just select the assembly which you want to add as an example i have added the ELMAH assembly for giving the project an error logging mechanism.

Similarly you can add a lot of other assemblies with the help of Nuget. All in all its a very good extension and you need not code anything to add those references and also you needn’t make any changes in your web.config manually, everything is done for you automatically by Nuget.

elmahadded

 

Its a very good tool which .net developers can leverage to generate cleaner and quick code.

Happy Programming !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

del.icio.us Tags: ,

Submit this story to DotNetKicks

del.icio.usSave Total0 users

Wednesday, May 05, 2010

Silverlight Spy: A must have tool for any Silverlight Developer

I have been using up Silverlight Spy from many months now, i do a lot of Silverlight development and believe me its a must have tool for every Silverlight developer it gives a feeling that a lot of developer tools have been combined for a Silverlight Developer you have a lot of things in Silverlight Spy, it can be compared to what firebug is to general web development , Silverlight Spy is to a Silverlight Developer. I will show you various different features of Silverlight Spy just as the write-up progresses.

Silverlight Spy Features List discussed in the write-up :-

1.Browser Feature

2.Explorer Feature

3.Output Log

4.Properties Window

5.Code View /XAML/C#

6.Statistics

7.Performance Monitor

8.Event Monitor

9.Network Monitor

10.Application Analyzer

11.DLR Shell

12.Cross Domain Access Policy Validator

13.Advanced Settings and Options

Now lets start analyzing every single feature of the Silverlight Spy.

1.Browser Feature

Silverlight spy comes with inbuilt browser feature you can just give the url to any of  Silverlight application and the silverlight spy will open that application for you in the inbuilt browser facility.

2.Explorer Feature

Explorer feature is used to navigate to each element in the Silverlight tree , you can go inside each and every element tree to look into what is the xaml used to build up that application.

Explorer feature combined with various other inbuilt features will let you do in depth analysis and study of the code.Explorer feature is very useful while you are stuck in small UI issues like your canvas or stack panel or grid are not positioning correctly, silverlight spy will be savior for you at those moments.

Like firebug for html pages silverlight  spy also have this highlighting feature in-built as soon as you select some element it will get highlighted in the UI in the inbuilt browser.

Also there is a cool shortcut to quickly highlight and navigate to a particular element in the application , use Ctrl + Shift to navigate to an element in the silverlight tree.

So you can navigate both ways either selecting an element from the UI to the explorer tree or from the explorer tree to the element in the application.

 

3.Output Log

Output window tells you every minute details which are going on while your app is either loading or running sometime you get really frustrating Ag_Parser errors due to some missing images and many other reasons which you cannot know just by looking into the firebug details of your browser.

So this output window is really helpful in those scenarios as well.

Also the output window lets you know the type of Silverlight application your are using this means the version , prerequisites if any.

 

4.Properties Window

Properties window is a special window where in you can change the properties of the element selected in the explorer window as shown above in the figure. Property window is a great help to find small UI bugs you can adjust margins, padding and height and width and various other properties to reflect changes in the browser so that you know what exactly you need to change in order to get the change in the actual code.

Explorer view also contains various other features such as Object Browser, Isolated Storage Browser, UI Automation , Styles and also the User Interface.

5.Code View /XAML/C#

6.Statistics

Statistics window is also a very important and informative part of the Silverlight spy package it calculates for you the number of objects which have been created under a UI Element , you can get the idea of how many elements are getting created under that UI element and whether so many elements are required or not , it gives you information of the Objects including the UIElements, Geometries and Brushes

7.Performance Monitor

Performance Monitor consists of Memory profiling, process profiling, processor usage, frame rate and isolated storage usage. Performance monitor gives you the real picture of how much memory all your objects and application is taking , how many processes are running and what is the actual load on the processor due to the application, what frame rate is the application running on, and how much isolated storage is being occupied by the Silverlight application

8.Event Monitor

Event Monitor is another important tool built inside the Silverlight Spy , basically Event monitor monitors and reports every event which is getting fired ranging from Mouse Enter to GotFocus and all other events , its very helpful when you want to know why your specific event is not firing or what is causing your event to not fire , its really helpful in those situations.

Another good things is that you can customize which events you want to fire leaving other unnoticed because many times you would not like to fire the mouseEnter event every time because its really irritating.

9.Network Monitor

Network monitor tracks all the traffic passing through the wires it acts like a mini fiddler from within the Silverlight spy, you can get basic network monitoring features for the application  using this Network Monitor tool.

10.Application Analyzer

Application Analyzer consists of two tabs one tab contains the rules and another tab contains the results which are shown after the analyze process is complete.Rules consist of Deployment Rules and Performance Rules

 

11.DLR Shell

We can also execute dynamic languages such as Ruby and Python in the silverlight applications AppDomain , it has a lot of inbuilt samples also for executing with the DLR Shell, its a very powerful and really interesting feature.

12.Cross Domain Access Policy Validator

Cross Domain Access Policy Validator will let you know the status of the cross domain access of the the service files on your server it checks for the correct clientaccesspolicy.xml and crossdomain.xml files if you want to make cross domains call to a server and you want to know whether the server allows cross domains calls or not you can just check the server with the Cross Domain Access Policy Validator tool.

13.Advanced Settings and Options

There are various other advanced settings which you can configure according to your development needs, as mentioned above you can add the code reflection support to look up into the code from the xap file using the reflector you just have to give the path of the reflector.exe and silverlight spy will automatically decompile the Silverlight assemblies for you.

Sometimes if you have a slow internet connection and the xap file size is large then it might take a long time to download for such situations you can increase the xap file download time to any number of seconds otherwise silverlight spy will give a timeout error as soon as the default time is passed.

Silverlight spy gives you an option to turn on the inbuilt ruler to have accurate measurements in the application UI you can look yourself the relative margins and the height and widths of the UI elements.

You can download the latest bits of the Silverlight spy which works for the latest Silverlight 4 build from http://firstfloorsoftware.com/downloads/SilverlightSpy3/SilverlightSpy.3.0.0.11.msi

Happy Programming !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Update : 22 Sept 2010

If you are using Silverlight Spy with your MEF application in Silverlight then you will get a nice little error as soon as you try to open up your application in Silverlight Spy.To rectify this you have to go to Tools –> Options –> Advanced->Enable DLR and uncheck the enable DLR option.

Submit this story to DotNetKicks

del.icio.usSave Total0 users

Thursday, April 08, 2010

The property 'Multiple Select' does not exist on the type 'RadGridView' in the XML namespace 'clr-namespace:Telerik.Windows.Controls;assembly=Telerik.Windows.Controls.GridView'

If you have updated from the Q32009 version of Telerik RadSilverlight controls to the latest Q1 2010 release of the RadSilverlight controls and you were using MultipleSelect property in the RadGrid then you will get this error.

Its very simple to resolve this error this property on the RadGrid has been declared obsolete and has been replaced by a new property called “SelectionMode”

If you were using MultipleSelect = False, then now you can use SelectionMode = Single , this is the default value and it says only one item can be selected at a time.

If you were using MultipleSelect = True , then now you can use SelectionMode = Extended. this means that items are added to the collection by combining the mouse clicks with Ctrl or Shift keys

There is one more value to this property and this is like SelectionMode = Multiple this means that items are added to collection on the click of the item and are removed from the collection when you click again on the item.

So above mentioned is the solution to your problem if you have recently upgraded from the older version of RadSilverlight controls to the new version of the controls.

Happy Programming!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Submit this story to DotNetKicks

del.icio.usSave Total0 users

Friday, February 12, 2010

ElementBinding,Binding Modes & UpdateSourceTrigger Property in Silverlight

Silverlight has a great binding syntax and its two way binding approach is a life saver, also it gives room to various new and creative concepts which developers can use to create really cool apps and features.

In this article i will talk a little about the Two Way Silverlight binding and the UpdateSourceTrigger Property.

Consider an example where we have a TextBox and a Silder control, now we want our TextBox to change its numeric text as we move the thumb of the slider control, now doing this is very simple in Silverlight by the element to element binding syntax, you just have to set the textbox text property to bind to the element slider and set its binding path to the value property of the slider control.

<Slider x:Name="slider" Maximum = "40" Value= "10" />
<TextBox x:Name="tbSliderValues" Text="{Binding ElementName = slider,Path = Value}"/>

So by the above code what you can do is as soon as you change the slider value i.e as you move the slider thumb the text in the textbox gets changed to the current value of the slider.

Now what if you change the text in the textbox , will the same thing works in the reverse order as well , meaning changing the text in the textbox will change the slider value , is it possible ????

Yes this is possible with a very simple tweak , just say thanks to the TwoWay DataBinding syntax of Silverlight

Just modify your code as given below and it will work like charm.

<Slider x:Name="slider" Maximum = "40" Value= "10" />
<TextBox x:Name="tbSliderValues" Text="{Binding ElementName = slider,Path = Value,Mode = TwoWay}"/>

Also to make a little point here about the different types of mode available in Silverlight, basically there are 3 types of mode in Silverlight :-

  1. OneWay
  2. TwoWay
  3. OneTime

One way is used when you know that the changes have to take place in only one direction meaning you can use oneway mode with Slider and TextBlock control in a simple case.

TwoWay mode is used when you want both the binding elements to reflect changes when either one is changed.TwoWay binding mode is the most commonly used mode in silverlight.

OneTime mode is used when you already know that you need to perform binding only one time and later the values related to that thing will never change in your application or if ever they are changing you are not reflecting those changes to your UI.

That said you have got the idea about the binding in Silverlight,now consider a situation in which you have a textbox and on the textchanged property you want to perform the binding to the slider, by setting the mode to two way will only work in this case when you loose focus from the text box i mean it will by default not work on the textchanged event.

So here what we have to do is explicitly force an Update to the property value.

private void tbSliderValue_TextChanged(object sender, TextChangedEventArgs e)
{
BindingExpression expression =
tbSliderValue.GetBindingExpression(TextBox.TextProperty);
expression.UpdateSource();
}

Now this will update your property everytime the textchanged event is fired for the textbox.

Now if you know that you will not need to update this using the default behaviour as in the case above you can reduce overhead by specifying the UpdateSourceTrigger = Explicit which tells that you already have set the update behavior explicitly so no need to check for the updates

<Slider x:Name="slider" Value="1" Maximum="100" Minimum="1" Width="300" Height="20" />
<TextBox x:Name="tbxSliderValue" TextChanged="tbxSliderValue_TextChanged" Text="{Binding Value, ElementName=slider, Mode=TwoWay, UpdateSourceTrigger=Explicit}" VerticalAlignment="Top" Width="300"/>

UpdateSourceTrigger property has only two values one is Explicit and another is Default

Happy Programminig!!!!!!!!!!!!!

Submit this story to DotNetKicks

del.icio.usSave Total0 users