Search

Picturize.me is a Silverlight Based Facebook application developed by Monir Abu Hilal, inspired by the new profile look and the way ‘tagged’ pictures appear in it. What Picturize Me does is basically take one (or more) picture and split them between the profile picture and the pictures bar on the right so the overall look eventually is one big picture for the whole profile.

Revamp your Facebook profile with Picturize.me now!

András Velvárt discusses how basic Facebook features (such as logging in, posting to a user’s wall, etc) can be accessed from within your Silverlight application.

Source: Dotneteers

Social networks have grown to be a really important factor to consider when you are building any sort of publicly available application - and the biggest one out there is almost certainly Facebook. According to some of its own statistics, it has more than 500 million (yes, that's no exaggeration) active users, half of which log on to Facebook every day. Those 500 million users each have 130 friends on average. That means, that getting any one of those 500 million to use your application, might lead to 130 more learning about it, 130 more people each having 130 more friends they can bring and so on. You will probably agree with me, that this alone is a pretty strong argument for connecting your application to Facebook.

We are happy to announce that SilverlightShow just moved to a new page on Facebook. SilverlightShow is always up-to-date with the most interesting and helpful information. Our main purpose is to provide you with quality content and be as useful as we can. Join our page on Facebook in order to:

• get notified for all news and articles
• get invited to new webinars
• see announcements on webinar recordings
• learn about new books
• monitor our upcoming contests (our next Eco contest is coming up soon!)

If you don't want to miss something important, take a look at the other ways in which you can keep an eye on the content published here at SilverlightShow:

Source: Method ~ of ~ failed

In introducing the concept of plugins, it was made clear that the Seesmic Desktop Platform (SDP) would be leveraging the Managed Extensibility Framework (MEF) that was to be included as a part of Silverlight. Seesmic would define MEF contracts that as long as developers adhered to them (and of course implemented any required interfaces for actual functionality) then the plugin would be able to extend the platform. The most grandiose idea can be simply stated as if you don’t like how Twitter is represented in Seesmic, fine…change it. Of course, I suspect most people will be just fine with their implementation and choose to extend in other areas as I’ve done.

For quite some time now, .NET developers have been left out in the cold without official support from Facebook. No more, my friends! Today, Andrey Goder announced the first release of Facebook’s official C# SDK in his blog post.

If you are developing applications for Facebook, then you know that the old Facebook REST API has been replaced with the new Graph API. To make sure that my Facebook applications keep working, and considering the uncertain future of the Facebook Developer Toolkit, I decided to write my own Graph SDK - GraphLight.

Play ittiGator on Facebook and challenge your friends with your high score. 

Play Now!!!

The best part?  It’s built on Silverlight 4 and the Managed Extensibility Framework (MEF)!  This is awesome news for those of us who have been using various clients that have been locked down to specific use scenarios.  There always is a few things I want/need/etc in software and it’s great now that (at least in this space) I can change things I don’t like.

That’s right, Seesmic Desktop is moving more toward a “shell” concept (my words, not theirs) where they provide some defaults but also extensibility points for anyone to replace and/or extend.  Don’t like the way they implemented Twitter?  Fine, change it (or search for a better plugin).

With Silverlight 4 trusted applications, the update mechanism requires that your applications be signed in order to use the auto-update APIs.  We wanted to wait until SL4 released in order to provide a signed version (and our internal signing process didn’t allow signing the beta).  Now that we have a signed version, you’ll be prompted when an update has been installed for the app.