If you need to sign a piece of code - eg. a Silverlight application, like I did with Sesame, an EXE, a DLL, an AIR application, a JAR applet - you need a code signing certificate.
A code signing certificate must be bought from a certificate authority, for example GoDaddy, VeriSign, Thawte, and Comodo. Note: a code signing certificate and an SSL certificate are not the same thing.
Be aware that not all providers allow you to sign everything with a single certificate. Some sell separate certificates for Microsoft Authenticode (that's what you need for Silverlight XAPs, for DLLs, for EXEs, and more), for Java, for AIR, and so on. Given that a code signing certificate is not exactly cheap, you may prefer to buy a single certificate that will allow you to sign files in different file formats.
I chose to buy my certificate from K Software, a reseller of Comodo certificates. It was much cheaper and moreover there isn't the restriction the other vendors impose on what you can sign.
Once you have your code signing certificate, you'll use SignTool.exe, which is a command-line tool part of the Windows SDK and installed with Visual Studio, or simply use Visual Studio 2010.
A new version of Sesame has been uploaded. It contains several fixes and adjustments. The fixes concern mainly the filtering row.
This new version also introduces client-side paging, signed bits, and auto-updates.
A new client-side paging feature has been activated. Sesame will now retrieve 15 items by default for each query, and 15 more each time you press "Load more".
This will result in improved speed.
For example, now that Netflix returns 500 items by default instead of 20 previously
, the new client-side paging is even more important. To give you an idea: 500 Netflix titles weight more than 3MB, while 15 titles is just about 95KB. No need to say that there's a big difference in speed and resource consumption between the two!
15 items is enough in most cases. In the future, the size of the data pages will be customizable.
Previously, when you tried to install Sesame on your desktop, you saw a confirmation dialog that looked like the following:
Not very engaging...
Starting with this new release, Sesame binaries are signed. This results in this new dialog box:
Less frightening than the "unverified" message, isn't it? This proves also that you'll be using genuine software.
Another advantage of having Sesame signed is that it allows Sesame installed on the desktop to automatically update when a new version becomes available.
Note: To get the current release, however, you'll have to use the "Remove this application" command in the context menu of the desktop app and then "Install on desktop" again in your web browser.
Next time a new version of Sesame is published, you'll see the following dialog box appear:
And next time, for even more exciting features
That's it for today. Next time I'll introduce the provider model on which Sesame relies, and I'll show how this will allow you to browse more than just OData.
You'll see that this will enable a whole new set of possibilities!