Social Stream for Microsoft Surface 2.0 posted

  • Article

As part of our SDK we have some samples that help developers understand Microsoft Surface development concepts. The goal of the samples that we post on our SDK is to show how to use a given API. In those samples we favor simplicity and clarity sometimes at the expense of how useful the application itself may be. For instance, we have our RawImageVisualizer sample that does a great job showing how to use our Core APIs to query the raw image and show it on the screen; on the other hand all it does is, well, show the raw image.

We also think it is useful to share with the developer community how to write complete functial applications. I am happy to share with you one of these applications. It is called Social Stream for Microsoft Surface 2.0, and it just got posted to code.msdn.microsoft.com.

Social Stream for Microsoft Surface is a sample application created in collaboration between Microsoft and Stimulant, Inc. It is an interactive way for businesses to engage their customers face-to-face using the most recent and relevant Twitter™, Flickr®, and RSS newsfeeds.

More information on it at code.msdn.microsoft.com

Comments

  • Anonymous
    October 06, 2011
    The comment has been removed

  • Anonymous
    March 01, 2012
    It seems the social streaming is no longer available, keeps prompting to login with the developer credentials, is this true?

  • Anonymous
    March 09, 2012
    I am getting an error telling me that (.wixproj) is not supported by this application when I tried to open this sample in VS 2010. I have the surface 2.0 SDK installed and did not see any other requirements needed for this app to run. Did you guys test this before releasing it?

  • Anonymous
    March 31, 2012
    running into the same .wixproj issue as Chekib.  what does that mean?

  • Anonymous
    March 31, 2012
    ok multiple issues, but got it to work:

  1.  remove the installer project.  don't need it if you running locally on local machine.
  2.  make sure resources directory is available where it is looking for it.
  3.  In the SocialStream.ConfigTool project, modify AssemblyInfo.config //[assembly: AssemblyVersion("1.0.$WCREV$.0")] //[assembly: AssemblyFileVersion("1.0.$WCREV$.0")] REMOVE $WCREV$ and replace with 0 - looks like some build related variable. After this all was well.
  • Anonymous
    March 31, 2012
    also remove the <Import Project="$(ProgramFiles)MSBuildMicrosoftStyleCopv4.4Microsoft.StyleCop.targets" /> from .csproj files, as someone earlier mentioned.  thanks