1. Supported languages:

The SDK supports the following languages and Microsoft Windows* graphical APIs:

• C# for WPF (Windows Presentation Foundation) applications
• C# for WinForms (Windows Forms) applications
• Visual Basic for WPF applications
• Visual Basic for WinForms applications

2. Supported Runtimes:

1. Microsoft* .NET Framework 3.5 and newer is supported.

3. Intel AppUp™ Software Debugger:

The Intel AppUp™ Software Debugger is a utility that emulates the Application Services of the Consumer Client. With the Intel AppUp™ SDK Plug-in 1.0 for Visual Studio 2008 software installed and the Intel AppUp™ SDK code included, you can test and debug your application without requiring the full client or access to hardware.

4. How to add the Intel AppUp™ SDK Plug-In in Microsoft Visual Studio* 2008:

Step 1: In Visual Studio, right click on Reference and use Add Reference from the shortcut menu to add the library to the project.

Step 2: Declare SDK Namespace and Integrate with the .NET SDK:

In the declaration section at the start of the C# source file, define com.intel.adp as a namespace. This frees you from having to add it as a prefix for SDK calls in your application. See the sample below:

/// <ADP> 
using com.intel.adp; 
/// </ADP> 

Below is the sample code for C#. Paste in the Following code in the Initialization section:

 
	{ 
	AdpApplication app = new AdpApplication(new AdpApplicationId(0x11111111, 0x11111111, 0x11111111, 0x11111111)); 
	/// Note: replace "0x11111111, 0x11111111, 0x11111111, 0x11111111" with the actual application ID 
	/// once you obtain it from Intel AppUp(SM) Developer Program web portal 
	} 
	catch (AdpException e) 
	{ 
	if (e is AdpErrorException) 
	{ 
	// TO DO: add your logic to handle the errors during initialization 
	MessageBox.Show(e.Message, "Error"); 
	System.Environment.Exit(1); 
	} 
	else if (e is AdpWarningException) 
	{ 
	// TO DO: add your logic to handle the warnings 
	MessageBox.Show(e.Message, "Warning"); 
	} 
	}

Sample code for Visual Basic Winforms applications:

Declare the SDK namespace com.intel.adp using the Imports Statement shown below.

	/// <ADP>
	Imports com.intel.adp
	/// </ADP> 

Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
        Try
            Dim app As New AdpApplication(New AdpApplicationId(&H11111111, &H11111111, &H11111111, &H11111111))
            ' Note: replace "&H11111111, &H11111111, &H11111111, &H11111111" with the actual application ID
            ' once you obtain it from Intel AppUp(SM) Developer Program web portal
            ' To test Expired ID, use AdpConstants.ADP_EXPIRED_APPLICATIONID
        Catch ex As AdpException
            If TypeOf ex Is AdpErrorException Then
                ' TO DO: add your logic to handle the errors during initialization
                MsgBox(ex.Message)
                System.Environment.Exit(1)
            ElseIf TypeOf ex Is AdpWarningException Then
                ' TO DO: add your logic to handle the warnings
                MsgBox(ex.Message)
            End If
End Try
End Sub

Step 3: Intel AppUp™ Software Debugger:

The Intel AppUp™ Software Debugger is only supported for Visual Studio 2008*. The Intel AppUp™ Software Debugger allows you to test and debug your application without requiring the full client or access to hardware. Below is the screenshot.

Click on “Start the Intel AppUp™ Software Debugger”. You will see the below window:

Debug your application. If the Intel AppUp™ SDK code is included you will see the below window

Step 4:

Replace "0x11111111, 0x11111111, 0x11111111, 0x11111111" with the actual application ID once you obtain it from Intel AppUp(SM) Developer Program web portal and recompile the program.

Step 5: Create an Installation Package:

Create a "silent install" .MSI package that meets the Intel AppUp(SM) Developer Program packaging requirements. These requirements ensure that applications provide a good user experience during installation and Uninstallation. For a list of packaging requirements, refer to (http://appdeveloper.intel.com/en-us/article/packaging-requirements). For tips on packaging applications for Windows*, refer to (http://appdeveloper.intel.com/en-us/article/how-creating-your-msi-installer-using-visual-studio-2008). You must wrap the AdpLibrary.dll library file into your application installer. The installer must copy the .dll file into the same folder where the application’s main executable is copied.

Note for Visual Studio 2010* developers:

Intel AppUp™ SDK Plug-In is tested only against Visual Studio 2008*. However, if you are a Visual Studio 2010* developer you need to make sure your target .NET frame work is set to 3.5. Below are the steps:

1.Change the .NET Target Framework from 4.0 to 3.5
Changing Target .NET Framework for C#:
A.On the Project menu, click ProjectName Properties.
B.Click the Application tab.
C.In the Target Framework list, select .NET Framework 3.5.

Changing Target .NET Framework for VB
A.On the Project menu, click ProjectName Properties.
B.Click the Compile tab.
C.Click Advanced Compile Options.
D.In the Target Framework (all configurations) list, select .NET Framework 3.5.

2.Click on Publish->Prerequisites. Make sure Microsoft .NET Framework 4.0 is unchecked.

3.When creating the MSI using Visual Studio 2010* Setup project make sure you target to .NET framework 3.5. Right Click Setup Project->Prerequisites and uncheck Microsoft .NET Framework 4.0 in the Prerequisites.

Right Click Setup Project->View->Launch Conditions

Click on .NET Framework and change the version to target to .NET Framework 3.5