Support for new desktop app authorization process?

Oct 28, 2009 at 10:03 AM

Facebook now recommend a new authorization process for desktop apps (http://wiki.developers.facebook.com/index.php/Authorization_and_Authentication_for_Desktop_Applications). In particular, they say "When you configure an application with the Facebook Developer application, you are given an API key and an application secret. You can disregard the application secret and you should never include it in your desktop application's code, as it can be decompiled and used maliciously."

Are there plans to support this? The latest tip (37335) doesn't seem to. Using:

FacebookService1.ApplicationKey = "<<key>>" 
FacebookService1.IsDesktopApplication = True
FacebookService1.ConnectToFacebook()

gets a "104 Incorrect Signature" response, whereas using:

FacebookService1.ApplicationKey = "<<key>>" 
FacebookService1.Secret = "<<(deprecated) application secret>>" 
FacebookService1.IsDesktopApplication = True
FacebookService1.ConnectToFacebook()

works fine.