Derik Whittaker : HowTo

Setting up Unit Testing w/ Jasmine, Chutzpah and Typescript

Derik Whittaker — Sun, 23 Dec 2012 12:49:46 GMT

Recently I got back into writing html/javascript code as part of my day job and boy-o-boy have things changed since the last time i did any of this. One thing that has not changed for me however was my belief in unit testing, so it was very painful for me to be writing hundreds of lines of javascript (ok really TypeScript) code with NO tests supporting them. At first I was able to live with this feeling because I was too busy trying to relearn how to do javascript development. However, I have not reached a comfort level where the lack of tests is killing me again.

No of course in client/server land of .Net development getting started testing is dead simple, however in the Javascript/html world things are still in the toddler stage, IMO, and there are many, many options to testing and I had no idea which is the best. After doing some searching and asking on twitter I settled on Jasmine as my test runner.

Now that I picked Jasmine, how did I get started? Here is what I did (this post is a merging of many, many posts I looked at to get me pointed in the right direction)

Step 1: Create a new test project

Open up Visual Studio 2012 and create a basic MVC 4 application (empty)

Step 2: Get Jasmine

Install the Jasmine NuGet Package

Step 3: Run your application in order to validate that jasmine is running correctly

Yup, we are good

Step 4: Get Chutzpah

I wanted a way to run my tests inside of Visual Studio and this plugin seemed to do the trick. I opted to install the test adapter which can be found here

Step 5: Validate that Chutzpah adapter was setup correctly

As you can see from above, it is setup correctly.

Now I wanted to be able to author my tests in Typescript and have them run as well.

Step 6: Download the Jasmine typescript definition file. I put this inside my scripts folder as seen below

Step 7: Create my Test Spec

The trick to getting this to work of course is that I need to include the jasmine-1.2.d.ts definition file inside my .ts file as below

I also need to reference my class under test file inside my .ts file as below

Once I did both of these I could write my first test as below

Bam, now I have a jasmine test written via Typescript and runnable via the Chutzpah test running. Of course I am sure there are other ways to get this to work, this is just what worked for me.

Till next time,

Deploying Asp.Net 4.5 site to IIS Error: ManagedRuntimeVersion to v.45

Derik Whittaker — Tue, 18 Dec 2012 14:28:46 GMT

Today I was trying to publish a Asp.net 4.5 site to our server and I received the following error;

The Application pool that you are trying to use has the ‘managedRuntimeVersion’ property set to v4.0. This application requires ‘v4.5’

I thought this was odd so I went to change the App pool, only to see there is no v4.5 option. After a bit of Goggling my suspicions about v4.5 not having an app pool as v4.5 of .net is inplace update and does not have a new ‘version’.

After a bit more Goggling and looking at StackoverFlow answers I found the solution, although it was not the ‘selected’ solution but oh well.

See I am doing my deploy via a powershell script using pSake and my deploy looked something like this

&$msBuildpath /verbosity:m $projectFileAndPath /T:Rebuild /T:Package /p:"Configuration=$buildMode;Packagelocation=$packageFolder"
/p:DeployOnBuild=True /p:DeployTarget=MsDeployPublish /p:CreatePackageOnPublish=True
/p:MSDeployPublishMethod=RemoteAgent /p:MSDeployServiceUrl=$deploymentServer /p:DeployIisAppPath=$deploymentAppPath
/p:UserName=$deployuser /p:Password=$deploypassword

What I needed to add was the /P:VisualStudioVersion=11.0 switch to force the right compiler. Once I added this switch my deploy was right as rain.

Till next time,

Sending In-Application Toast Notifications in WinRT for C#

Derik Whittaker — Wed, 14 Nov 2012 23:52:35 GMT

When building a Windows RT application (based on C#) it is pretty common that you will want to notify your user of an event. It is more common that you are going to want to do this in a way which is not intrusive, aka does not get in the way of the user. Luckily for you the WinRT team has built a great toast notification engine into the framework.

In fact this notification engine allows for toasts to be both in-application as well as remote notifications. It also allows for notifications to be real time (sent when at the time you create them) as well as scheduling them to be sent at some predetermined date/time in the future.

In this post I am only going to show how to do in-application toasts, I will focus on cloud base toasts in a future posts. Before we dive into the code, take a second to look at the Toast Template Catalog for all the various ways we can layout/format the toast.

Getting started.

What does a toast look like?

How do create toasts?

You must enable toasts via the Package.appxmanifest

If you do not enable toasts you will NOT get a toasts, nor will you get an error, it will simply NOT WORK.

Check to see if toasts have been enabled

            
var notifier = ToastNotificationManager.CreateToastNotifier();
if (notifier.Setting != NotificationSetting.Enabled)
{
	// do something here
}

In the above we are first creating the notifier, then we simply check the Setting property. If it is not enabled you may want to punt or alert the user.

Create the code to create the toasts – Real time toasts
```
            
var notifier = ToastNotificationManager.CreateToastNotifier();
var template = ToastNotificationManager.GetTemplateContent(ToastTemplateType.ToastText02);
            
var element = template.GetElementsByTagName("text")[0];
element.AppendChild(template.CreateTextNode("Line 1 goes here"));

var toast = new ToastNotification(template);
notifier.Show(toast);
	
```
If you look at the code above one thing should jump out at you right way, the fact you have to drop down to raw XML. Yea, it sucks. The toast team decided to NOT wrap this in the same way as the Tile team, but oh well.

In the above we are first creating the notifier, then we will chose the template we want. Once we do that we just start updating the values as expected.

Create to code to create scheduled toasts

            
var notifier = ToastNotificationManager.CreateToastNotifier();
var template = ToastNotificationManager.GetTemplateContent(ToastTemplateType.ToastText02);
            
var element = template.GetElementsByTagName("text")[0];
element.AppendChild(template.CreateTextNode("Line 1 goes here"));

// Schedule the toast to appear 10 seconds from now
var date = DateTimeOffset.Now.AddSeconds(10);
var scheduledToast = new ScheduledToastNotification(template, date);
notifier.AddToSchedule(scheduledToast);

If you look at the code above about the only thing that has changed is that we are now creating a ‘ScheduledToastNotification’ instance and adding this to the ToastNotifiier.

As you can see doing in-application toast notifications is very easy and only requires a few lines of code.

Till next time,

How we handled our branches during our TFS to Git migration

Derik Whittaker — Sat, 10 Nov 2012 18:02:03 GMT

In my prior post I documented the steps and processes that OUR team took to move from hosting our source in a TFS solution to Git/Github (remember, these are SIMPLY our steps). However, one thing I did not mention is how we moved our feature branches from TFS to Github.

Given the fact that TFS and GIT treat branches treated 100% differently at the lowest level, we knew we would NOT be able to clone/convert our features branches in any reasonable manor and push those into Git. However, these branches were still active and did need to get them out of TFS and into Git.

So how did we migrate/push our feature branches from TFS to Git? Simply xCopy :)

What we did was the following

Did a pull from our TFS root into each of the feature branches and resolved any merge issues.
Created the feature branch in Git via the Windows Github client
Switched context on our git repository to be that of the new branch
xCopied our TFS branch files from TFS into the folder of our Git repository
Let the Windows Github client pick up the changes (I had to restart the Windows client in order for changes to get noticed, but that may not be required for everyone)
Committed the changes locally
Synced the changes to Github
Deleted my old branch
Had a beer.

As you can see from above, there were a few steps involved, and there may have been a better way. However, this just worked for us.

Till next time,

Code Contracts tab in VS2012 – Odd way to get it enabled

Derik Whittaker — Fri, 07 Sep 2012 10:38:19 GMT

I am a huge fan of the Code Contracts library which is now part of .net, in fact when I setup a new instance of VS it is one of the first plugins I install by default. However, I was having some issues because even though I had installed the .msi I was not able to get the settings tab to show up in VS2012, in fact it was not in VS2010 either. This was a bit odd to me because I had never had this issue.

In order to try to resolve this I decided I should uninstall the .msi and re-install it, so I set out to do this. However, after doing this I still did not have the tab in either IDE, now I was perplexed. Of course the first thing I did was to go out and search for the solution for this issue but nothing really popped out as ‘this is how to fix this issue’, however a few people did mention that they had to do a VS Repair install. I thought this to be a bit extreme so I was not too keen to give this a try.

However, as fate would have it I was kinda forced to do a Repair a few hours after tabling my efforts to get the tab to show in the IDE (I had some really odd VSMon debugger attachment issues and the error dialog actually suggested I do a repair). Given that I had 2 different issues both suggesting I do a repair install I figured WTF might as well do it.

Long story short, I did the repair install and BOTH my issues were resolved. I had the tab in the IDE and my VSMon debugger issues were gone. Now I don’t know if the issues were related or if it was just a really good coincidence but either way my issues were resolved.

So if you find yourself unable to get the Code Contracts tab showing in your IDE after installed the .msi try doing a VS repair install and see if that does the trick.

Till next time,

P.S. I have both VS2010 and VS2012 on my box and I installed VS2012 first. This may have caused some of the issues, not sure.

Help my Secondary Tile will not navigate correctly in my Win Phone Application

Derik Whittaker — Sun, 26 Aug 2012 01:15:21 GMT

When you are adding the ability to have a Secondary tile to your Windows phone application you may from time to time find the need to debug or mimic the launching of the application via the Secondary tile w/ the correct query string values. Sadly, debugging this via the debugger is not something that I have found out how to do, if it is possible please let me know. However, I have found another way to get the same result and here is how.

Get the exact tile uri used for the secondary tile.
Example: “/views/events/Landing.xaml?Id=1”
Open up the WMAppManifest.xml page under resources
Find the line that looks like this:
<DefaultTask Name="_default" NavigationPage="MainPage.xaml" />
Replace it w/ the URI of your secondary tile like this:
<DefaultTask Name="_default" NavigationPage="/views/events/Landing.xaml?Id=1" />
Launch the application

If you are wired everything correctly your page should load, but if you are trying to debug this it is likely you did not have everything correct. If you did not do things correctly you should get some sort of runtime error.

Hope this helps

Till next time,

FileLoadException: Could not load file for Version 2.0.5.0, Portable Class Library

Derik Whittaker — Mon, 23 Jul 2012 10:13:33 GMT

Recently while trying to deploy a service to a clean VM (moving this off our main production server onto its own server) I ran into the error below”

Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'System, Version=2.0.5.0, Culture=neutral,
PublicKeyToken=7cec85d7bea7798e, Retargetable=Yes' or one of its dependencies. The given assembly name or codebase was invali
d. (Exception from HRESULT: 0x80131047)

At first glance I thought it was saying that I did not have .net 2 installed on the server which was odd as it had .NBet 3.5 (which is a superset of 2) and .Net 4. Of course I quickly set out to Bing the hell out of the message but that did not really lead me to an immediate solution. However, what I did notice was that v 2.0.5.0 was always referred to in the context of Silverlight, this got me thinking. Was i referencing a Silverlight based assembly in my project? To find this out I turned to my handy decompiler from Telerik.

Sure enough I did have a silverlight assembly being referenced in .Net (I did not have the silverlight SDK installed on my box). I removed the reference and redeployed, but nothing changed. I still received the error above. Now I was getting pissed. I went back to the decompiler and started looking again through my reference tree to see if I missed something, and I did, kinda. Turns out one of our assemblies is using the Portable Class Library and it is targeted towards the client profile and Silverlight profile, but this should not have caused an issue, but clearly it did.

After a bit more digging the answer showed up. As it turns out the solution to my problem was buried deep on the Portable Class Library documentation page (as seen below), and it pointed me toward the setup file which solved my issue.

Turns out that when you use the Portable Class Library it will actually upgrade/update your .net assemblies on disk in order to use this, which makes sense, and with out running the installed mentioned above you will not be able to use any .net assembly which is based off the Portable Class Library.

The moral of the story is that if you are use PCL then make sure you install the update above on your servers in order to get everything to work.

Till next time,

Argument Exception when Working with Secondary Tiles in WinRT (C#)

Derik Whittaker — Sat, 14 Jul 2012 18:28:43 GMT

If you are attempting to work with or create secondary tiles and you are getting the following exception you may want to check your title id.

System.ArgumentException: The parameter is incorrect.

When trying to do a SecondaryTile.Exists(tileId) with the value as seen in the picture below

I was getting the ArgumentException, at first I was stumped but then it dawned on me the ID cannot contain spaces or special characters. When I removed the spaces as seen below my errors went away.

The take away from here is if you are getting exceptions when working with tileId’s check that the ID does not have whitespace or special characters.

Till next time,

Playing a embedded media file (mp3) in WinRT (not via Xaml)

Derik Whittaker — Sat, 14 Jul 2012 17:39:30 GMT

When building WinRT applications it is going to be pretty common to want to play some sort of embedded audio file. It may also be common to want to play this file but via a ViewModel (or simply not in a view). In this post we are going to take a quick look at how to play an MP3 file by using the MediaElement control, but we will NOT be doing this via XAML, we will be doing via straight up code. The reason I am not using XAML here is because i don’t want to limit the places or times I can play audio, also I want to trigger the playing of the file via my ViewModel.

Before we get coding lets assume we have an audio file embedded in our application under the /Assests/SoundFiles folder and the file name is ding.mp3

private MediaElement _mediaElement;
public async Task Play( string fileName)
{
    var packageLocation = Windows.ApplicationModel.Package.Current.InstalledLocation;
    var assetsFolder = await packageLocation.GetFolderAsync("assets");
    var soundsFolder = await assetsFolder.GetFolderAsync("soundFiles");
    var myAudio = await soundsFolder.GetFileAsync(fileName); // would be ding.mp3
 
    _mediaElement = new MediaElement();
            
    var stream = await myAudio.OpenAsync(FileAccessMode.Read);
    _mediaElement.SetSource(stream, myAudio.ContentType);

    _mediaElement.Play();
}

In the code above you can see that we are doing the following things.

Getting the StorageFile reference to Ding.mp3
Creating a new instance of the MediaElement (this is class level because I found the audio would not play if it were a local instance)
Open the StorageFile and get the Stream reference of the file
Set the Stream reference as the source for the MediaElement
Call Play

Now in theory you should be able to set the ‘source’ property to the file path, but i was not able to get this to work. This may have been my error or could be an issue with the MediaElement.

As you can see this is not too complicated and requires almost no code

Till next time,

Creating an IStorageFile out of a Local Resource in WinRT (C#)

Derik Whittaker — Tue, 26 Jun 2012 13:52:35 GMT

When working with a C#/XAML WinRT application it is common that you will include resources such as images, files, audio recordings, etc inside your deployment package. It will also be common that you may want to access these resources as native storage files in order to do things like share them between applications. Accessing these files is actually pretty easy and is only about 3 lines of code.

Before we get started assume that we have a directory structure inside our application as follows

root/Images/Image1.png
root/Images/Image2.png
root/Images/Image3.png
root/Images/Image4.png

When accessing our local files we will first want get the StorageFolder of the InstalledLocation of our package. This can be done as follows

var packageLocation = Windows.ApplicationModel.Package.Current.InstalledLocation;

Now that we have the StorageFolder (packageLocation) we want we can get the “Images” folder as follows

var imagesFolder = await packageLocation.GetFolderAsync("Images");

Once we have our images folder it is simple as asking for the given file as follows

var image = await imagesFolder.GetFileAsync(“Image1.png”);

Now that we have our Image we also have our IStorageFile. This allows us to pass this file to another application via the Share Contract, or to create a stream reference out of via the RandomAccessStreamReference.CreateFromFile(image) method.

Here is all the code in one block

var packageLocation = Windows.ApplicationModel.Package.Current.InstalledLocation;
var imagesFolder = await packageLocation.GetFolderAsync("Images");
var image = await imagesFolder.GetFileAsync(“Image1.png”);

// if you want the file as a stream (say to put into a Bitmap control
var imageStreamRef = RandomAccessStreamReference.CreateFromFile(image);

As you can see from above, this is pretty easy as well as pretty powerful.

Till next time

Parsing Twitter Date format to .Net DateTime

Derik Whittaker — Thu, 24 May 2012 12:53:17 GMT

Recently when I needed to parse the twitter datetime format into a .Net DateTime I found this post on the web showing how to do it. However, the format string in the post is setup for non-us format so I thought I would share how to do it for US formatted datetime.

const string format = "ddd MMMM dd HH:mm:ss zzzz yyyy";

var d = DateTime.ParseExact("Thu May 24 11:43:52 +0000 2012", format, System.Globalization.CultureInfo.InvariantCulture)

Hope this helps.

Till next time,

Entity Framework Error–New Transaction is not allowed because there are other threads running in the session

Derik Whittaker — Wed, 14 Dec 2011 01:13:39 GMT

Recently when I was working with Entity Framework inside one of our RIA Services end points I ran into the errors below while trying to save my changes. Of course at first this error caused me to stop and scratch my head

To give a bit of background on what I was doing. Inside one of our RIA calls (Off Topic, not a big fan of RIA but this is not the time or the place) we were doing a bit of background processing. In this background processing we needed to query the database for some data (as seen below), update the data and then save the data. However, when I called ObjectContext.SubmitChanges() I would get the error above. what was really odd was that I was saving on the EXACT same ObjectContext instance as the instance the data was queried from so I was a bit stumped.

Here is the original code which was causing the problems

var socialLinks = ObjectContext.SocialMediaLinks.Where( x => x.ClientID == clientId )

As you can see from the line above the code appears to be pretty harmless. I am simply reaching into my ObjectContext and grabbing all the items which match for a given client. Later on in the code I am doing a ForEach loop over the list and changing various values based on rules. However, it is this code which is causing me errors when I try to save.

After a bit of searching and staring it finally occurred to me what the issue was. Because I had never actually ‘completed’ my query the original transaction was still opened and when I called save it was trying to create and use another transaction.

To get around this issue (there may be better ways and if so please let me know) I changed my code to be the code you see below.

var socialLinks = ObjectContext.SocialMediaLinks.Where( x => x.ClientID == clientId ).ToList()

By adding the .ToList() to my query I am forcing the fetch to take place at one time, thus closing the underlying transaction to the database. Now when I saved the data (I literally did not change another line of code) everything worked just fine.

If you find your self in this situation make sure you have actually finished executing your EF queries before you save your changes. BTW this is done inherently when going across the wire which is why I have never seen this before.

Till next time,

Using MVVM with the AutoCompleteTextBox in Silverlight 4

Derik Whittaker — Fri, 18 Nov 2011 22:25:00 GMT

The AutoCompleteTextBox is a great tool in Silverlight to allow you to provide relevant information to your users as they are typing as seen below:

But there are a few issues with this control

Pretty much every sample on the net uses the code behind to do the heavy lifting and not binding
It will not update the VM text box in real time, which is needed if you want to do on the fly filtering

In this post I will walk you though how to setup your AutoCompleteText box and we will learn how to do 3 things

Use MVVM to populate and use the control
Use a custom Behavior to allow the property backing the control to be updated in real time
Use a command to trigger background searches on the fly

Using MVVM to populate your control:

In order to populate your AutoCompleteTextBox you will need to bind something to the ItemSource property of the control as such:

ItemsSource="{Binding KeywordSearchSource}"

I am sure you are wondering what the KeywordSearchSource is? Well it is simple a property which returns a IEnumerable<string>

       public IEnumerable KeywordSearchSource
        {
            get
            {
                return SomeListOfValues.Select( x => x.TextValue );
            }
        }

The next thing you will want to do is setup a property in your view to handle the current value inside the control. This is needed because we are binding and not using the code behind. You can do this as below:

Text="{Binding KeywordSearchText, Mode=TwoWay}"

The trick to above is to remember to mark this as being TwoWay or you will not get the results you are expecting

        private string _keywordSearchText;
        public string KeywordSearchText
        {
            get { return _keywordSearchText; }
            set 
            {
                _keywordSearchText = value; 

                NotifyOfPropertyChange(() => KeywordSearchText); 
            }
        }

That does it for the MVVM portion of the setup. However, you may already know that when binding to a text box the actual binding does not trigger until AFTER the user leaves the control, in many cases this is good but not in our case. In our case I want to start the filter process as the user types (which is fine as I have all the filter data local, this is NOT fine if I have to do any type of remote call to filter the data as this will cause a bad user experience).

Triggering the binding in real time:

As I stated above the binding of a text box (or autocomplete text box) does not fire until you leave the control and this is not the desired action for us. In order to get around this we are going to create a custom behavior to allow the text box binding to push the value into our property in real time.

Our custom behavior is going to be called the ImmediateUpdateBehavior and the code can be found below.

    public class ImmediateUpdateBehavior : Behavior
    {
        protected override void OnAttached()
        {
            AssociatedObject.TextChanged += OnTextChanged;
        }

        void OnTextChanged(object sender, RoutedEventArgs e)
        {
            AssociatedObject.GetBindingExpression(AutoCompleteBox.TextProperty).UpdateSource();
        }

        protected override void OnDetaching()
        {
            AssociatedObject.TextChanged -= OnTextChanged;
        }
    }

In the behavior above you can see that all we are pretty much doing is listing for the TextChanged event and forcing the binding to fire. This is a nice way to do it when developing with MVVM.

Once we have our behavior created we need to attach it to our AutoCompleteTextBox and that can be found below.

Triggering the filtering to fire as we type:

I am going to chose to do this via a Command. I guess you could have the changing value of the property do the same thing but I typically am against doing this as I feel it is hiding the implementation details of the filtering. I also feel that this can cause unwanted side effects in your code if you are not careful.

In order to use the command I am going to use the EventTrigger behavior in silverlight to call my command. You can see this XAML below.

In the XAML above you see I am calling the KeywordSearchFilterCommand. This command will end up calling the code below

        private void KeywordSearchFilter()
        {
	    // Key here is i am simply notifying to rebuind these values and allowing the underlying methods to filter the data
            NotifyOfPropertyChange(() => SomeListOfValues);
            NotifyOfPropertyChange(() => PagedSomeListOfValues);
        }

As you can see from the above I am not doing anything special in the filter method I am simply notifying of property change and letting the various properties doing their own filtering. The code below is the filtering for my PagedSomeListOfValues property (we are doing client side paging here)

        public ObservableCollection PagedSomeListOfValues
        {
            get
            {
                var skipCount = PageIndex > 0 ? PageIndex * PageSize : 0;
                var takeCount = PageSize;
                var tempItems= SomeListOfValues.Skip(skipCount).Take(takeCount).ToList();

                var observableLinks = new ObservableCollection();
                observableLinks.SetContents(tempItems);

                return observableLinks;
            }
        }

Once you have your 2 properties (list and search field) bound to the AutoCompleteTextBox you are almost there, but not quite. In order to make this fully work you will want to also you the custom behavior and the filter command.

Hope this helps.

Till next time,

Help, my MVC Ajax requests are not rendering and there is no exception being displayed

Derik Whittaker — Mon, 10 Oct 2011 22:38:27 GMT

***** If there is any type of built in MVC support for helping find these issues please let me know *****

Ok, this may be common sense to everyone else on the net and if so… Oh Well.

Tonight I was working on the MVC3 rewrite of the Dimecasts.net website and after a bit of refactoring my search feature was not working….Well it was hitting the controller action just fine and returning the data out of the controller with NO issues. However my search result div was not being updated dated correctly.

Fortunately for me I just happened to already have Fiddler up and running so I simply popped over to see what it had to say. I immediately noticed that Fiddler was giving me a 500 error on my controller action result:

When I took a look at the response output I noticed the following:

In case you cannot read the above let me summarize for you. Basically I had changed the response object I was returned back out of my controller but I did not change my partial view.

Once I changed my partial view to expect the correct data type as the result model everything was right as rain.

The moral of the story is 2 things

Fiddler is your friend and WILL help you debug and diagnosis any errors you may have when doing anything http related
When doing some refactoring remember to make the correct changes to your razor views or you may not get the results you expected.

Till next time,

How to setup a clean error message when your Metro Application does not support Data Sharing

Derik Whittaker — Sun, 09 Oct 2011 11:54:00 GMT

When building a WinRT/Metro application one of the key integration points between your application and others is to allow Data Sharing via the Sharing Contracts. By default applications DO NOT support sharing and when a user taps on the Share Charm they will see an error similar to the following.

This message is NOT that user friendly and should be avoided. Besides what good does a screenshot of your application really do anyone .

If you are explicitly not going to support sharing from a given view in your application you should provide the user a little better message telling them this, fortunately setting this up is a piece of cake.

To setup this clean user friendly message we simply need to do 3 things

Grab the DataTransfer Context for the current view

Add the following using clause : using Windows.ApplicationModel.DataTransfer

Grab the context as : var dtm = DataTransferManager.GetForCurrentView();

Setup the event to handle the DataRequested event

Wire up the DataRequested event as: dtm.DataRequested += OnDataRequested;

Populate the failure message in the Share Panel with our user friendly message

Inside your event handler do the following:
args.Request.FailWithDisplayText( "Data Sharing Not Supported at this time" );

The args object is of course the EventArgs which is passed into your event handler.

One thing to pay attention to is that the amount of text which can be displayed is very short. If you provide a value which is too long the value will be truncated and the … will be appended to the end.

Now that we have enabled our view to display a friendly error message when someone tries to invoke the share we should see something like the following;

(please not the … added to the message. This is what I was referring to above when I said it will truncate long messages)

Till next time,