Source Error:

Line 1:  <%@ Page Language="C#" AutoEventWireup="true" %>
Line 2:
Line 3:  <%@ Register Assembly="System.Web.Silverlight" Namespace="System.Web.UI.SilverlightControls"
Line 4:      TagPrefix="asp" %>
Line 5:

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

Training URI

WPF vs. Surface
WPF On Project Creation – Contains 2 types of XAML files:
1. App.xaml contains an Application.Resources section. Any resources declared here are available at the application scope.
An App.xaml.cs code-behind file. This contains an empty class that can hold any interaction logic for App.xaml.
2. A Window1.xaml file that contains a Window element. By default, this is the main window for the application and contains a Grid element as the layout root.
A Window1.xaml.cs code-behind file that contains an empty class to hold any interaction logic for Window1.xaml.
3. A References section that contains any external assemblies your application is using.
4. A Properties section that contains all of the application settings including AssemblyInfo.cs, Resources.resx, and Settings.settings.
Surface

  APP.XAML This file provides the same functionality as the WPF App.xaml file. However, the file that Visual Studio generates for Surface projects includes markup to merge the Surface control templates with the application, by using the Microsoft.Surface.Presentation.Generic assembly.

SurfaceWindow1.xaml. This file provides similar functionality to the Window1.xaml file in the HelloWPF project, but there are several differences:

 · There is a reference to a new Surface-specific namespace.

· The main Window element is now a SurfaceWindow element. The SurfaceWindow element provides similar functionality, but also runs the application at full screen with the user interface oriented toward the user. · There is a SurfaceWindow.Resources section that contains an ImageBrush element with the Key property set to  WindowsBackground. This also has the ImageSource property set to a Pack URI pointing to the WindowsBackground.jpg resource.

 · The layout root is a grid that has the Background property set to the WindowsBackground resource by using the StaticResource markup extension.

Application Type Overview

There are three basic types of applications.

1. Windows application – Pure Windows Desktop application, except driven by WPF (xml).

2. Navigation application – a windows application, yet has the look and feel of web browser based application.

3. XBAP – which is an application that runs only in internet Explorer’s Browser. are also page-based and run in Internet Explorer under limited permissions.

2. Go to the training page and do the Training, do the labs at the bottom.(DevelopmentQuickStart(WPF).xps)

Module 2 Training

Microsoft Surface has four key capabilities that make it such a unique experience:

• Direct interaction. Users can grab digital information with their hands and interact with content on-screen by touch and gesture – without using a mouse or keyboard.
• Multi-user experience. The large, horizontal, 30 inch display makes it easy for several people to gather and interact together with Microsoft Surface – providing a collaborative, face-to-face computing experience.
• Multi-touch. Microsoft Surface responds to many points of contact simultaneously – not just from one finger, as with a typical touch screen, but from dozens of contact points at once.
• Object recognition. Users can place physical objects on the screen to trigger different types of digital responses – providing for a multitude of applications and the transfer of digital content to mobile devices.

WPF

Windows 7 API’s Support Multi Touch at the Operating System Level

Support is in part through a message WM_Touch. Hardware support is an evolving market. Already at this level, the operating system provides a promotion of multitouch messages to mouse messages. The promotion is present so that multitouch users can use touch and gestures to substitute as mouse moves or mouse clicks. This is useful when interacting with applications that may not be touch-aware, and the application does all its sspatial input processing through mouse events and messages. Windows 7 also coalesces the messages when appropriate, so that applications do not have to process an overflow of intermediate messages that all generate incremental events.

Internet Explorer version 8 as a browser host is also multitouch aware. Internet Explorer version 8 forwards platform multitouch messages to plug-ins such as Silverlight that are running within Internet Explorer, such that Silverlight applications can interact with multitouch input.

starting at about 900 – Lots of laptop hp/dell/… Lenovo ThinkPad X200 Tablet Multi-Touch is 2k, best

Database – Alfrecso java based data base – too much , large, java
Dot Net Nuke – too slow – old technology
Could use a starter application like Baloonshop, it has the microsoft
Cloud Computing – azure, amazon, lots — heavy duty…

TOOLS – Visual Studio 2008, 2010, Expression Blend 2 – Expression Blend 2 may have problem with .netFramework 4.
Replace Complex Server Controls
Javascript control – ugh!
Service – like calendars from yahoo, google…
RIA – Rich Internet application where controls replaced by Silverlight app( or maybe flash, …)

Had to configure .php and fcgi in properties.

had it add php=PHP under TYPE in the fcgiext.ini

[Types]
php=PHP

added :

[PHP]
ExePath=C:\Program Files\PHP\php-cgi.exe
;Protocol=NamedPipes
;QueueLength=1000
;MaxInstances=10
;InstanceMaxRequests=1000
;IdleTimeout=300
;ActivityTimeout=30
;RequestTimeout=90
;ResponseBufferLimit=4194304
;FlushNamedPipe=0
;UnhealthyOnQueueFull=0

Had to down grade to cgi. configured  .php extension as /program files/php/php.exe

   After the above, the solution built fine. I compiled it in both debug and release configurations as described in the docs.

The sample command line that they suggested didn’t work,  but this “C:\Program Files\Google\Google Data API SDK\Samples\Calendar.exe” worked(Surrounding Quotes were  needed).  That worked fine.  But… – I can’t fine the source code for the Calendar.exe ….
Well, I always need a starting point when I begin a programming project.
The docs show that the sample client code is online at  http://google-gdata.googlecode.com/svn/trunk/, and the sample calendar code is at http://google-gdata.googlecode.com/svn/trunk/clients/cs/samples/calendar/Calendar.cs.
I started fresh, Created a new c# Windows project, removed all existing .cs files.
Next I added a new windows form, then copied all the code from the web page above and replaced all generated code in the form.

References to 4 .dlls from the redist directory from the Google DATA api sdk solution.
then complile and all is OK!