Jerry Huang apps and developing apps

1. Global floating camera view, you can keep an eye on your camera while doing other things. The floating window can be dragged to anywhere you want.

2. Share camera access with friends and family, you can share the access of your camera with a encrypted hyper link. On click on that link the app will open the camera view directly without going though any setup work. 

3. Share the snapshot of your camera with one click

1. Copy all files and sub folders in "Microsoft Games" from old system backup, which in my case locates at: C:\Windows.old\Program Files\Microsoft Games
   to C:\Program Files\Microsoft Games
2. copy old backup C:\Windows.old\Windows\System32\CardGames.dll to
   C:\Program Files\Microsoft Games\FreeCell
   C:\Program Files\Microsoft Games\Solitaire
   C:\Program Files\Microsoft Games\SpiderSolitaire
   C:\Program Files\Microsoft Games\Hearts
3. Download the Microsoft Games Patcher 1.2 from http://rghost.net/37573001 (please ignore any warning from anti-virus software such as Windows Defender)
4. Run and apply the patch

Ref: http://forums.mydigitallife.info/threads/33214-How-to-use-Microsoft-Games-from-Windows-7-in-Windows-8

The new version (BTW Microsoft finally support 4 digits version number) contains a new function - to share your camera's snapshot to social networks (Facebook and Twitter at the moment). How to do it? Pretty simple...

1) tap the share button (the 4th button at the bottom)

2) Choose which social network you would like to share

3) One off: if this is the first time you choose the social network, you will need to input your username and password of Facebook (in this case) and authorized my app to post update on behalf of you

4) then input the message (a.k.a status update), and share

WP

[code language=C#]
byte[] frameBuffer;
BitmapImage.SetSource(new MemoryStream(frameBuffer, 0, frameBuffer.Length));
[/code]

Win8

[code language=C#]
 var ms = new Windows.Storage.Streams.InMemoryRandomAccessStream();
                        ms.AsStreamForWrite().Write(frameBuffer, 0, frameBuffer.Length);
                        ms.Seek(0);
                        BitmapImage.SetSource(ms);
[/code]

it looks to me that Win8 just making thing complicated:(

As I mentioned previously, I'm trying to develop a Win8 Metro version of IP CAM Coontroller, so I'm basically translating the WP coding into Win8. I'm going to post a series of blog post to record (and so benefit those googler with same problem) some of the interesting issue and topic.

WP coding:

[code language=C#]
Deployment.Current.Dispatcher.BeginInvoke(() =>
                        {
                            //do something here
                        }
                        );
[/code]

WIN8

[code language=C#]
 Windows.ApplicationModel.Core.CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(
                Windows.UI.Core.CoreDispatcherPriority.Normal,
                new Windows.UI.Core.DispatchedHandler(() =>
                {
                    //do something here
                }));
[/code]

This is not end of the story, by using the RunAsync like above, you will get a compiler warning from VS2012, and it's interesting that if you assign the returning result (of RunAsync) to a variable, the warning goes away. So the final version is like:

[code language=C#]
 var dummy = Windows.ApplicationModel.Core.CoreApplication.MainView.CoreWindow.Dispatcher.RunAsync(
                Windows.UI.Core.CoreDispatcherPriority.Normal,
                new Windows.UI.Core.DispatchedHandler(() =>
                {
                    //do something here
                }));
[/code]

Every upgrade from Microsoft is a nightmare! more or less...

I'm currently investgating the possibility of making a Windows 8 Metro version of my IP CAM Controller app. And what it turns out is not so pretty. Some developer already found out the issue a while back this year:

https://connect.microsoft.com/VisualStudio/feedback/details/737000/the-server-committed-a-protocol-violation-is-unoverridable-in-metro-style-apps

I'm encounterring the same and it's much much worse in my case, because what I'm dealing with is a bunch of HTTP servers implemented by various manufacturers that don't give a shit about Windows 8's world and they have their reasons - this has been working all the time, why just win8 can't?

Without enabling the useUnsafeHeaderParsing somehow, I don't think we can make any IP camera app unless we write our own HTTP component with raw socket, but Microsoft really expect us to do that? seriously?