How to use

• You need to have visual studio 2008 installed in your machine.
• Extract the zip file. It has 2 solutions and 2 xsl files.
• Take a back up of your global datastore directory
• In vista this is "C:\Users\All Users\Microsoft\corecon\1.0"
• In non-vista this is  "c:\documents and settings\All users\Application Data\Microsoft\corecon\1.0"
• Copy the xsl files to "addons" directory inside the Global datastore directory.
• Build the solutions. Copy the RemoteAgent.exe to d:\temp\Armv4i directory. If you are keeping the file in different directory then you need to modify the RemoteAgent.xsl file accordingly (modify the RootPath property)
• Execute the FileViewer.exe - you have the fileviewer ready.

I have created the RemoteAgent.xsl package for Armv4i architecture only. If you want to work in any other architecture then you need to build the RemoteAgen.sln in the required architecture. Add a Packagetype entry in the Remoteagent.xsl for that architecture. In case you want to add support for X86, then add the following inside the Packagetypecontainer (in RemoteAgent.xsl)

<PACKAGETYPE Name="x86" ID="x86" Protected="True">
  <PROPERTYCONTAINER>
    <PROPERTY ID="RemotePath" Protected="True">%CSIDL_WINDOWS%</PROPERTY>
    <PROPERTY ID="RootPath" Protected="True">D:\temp\x86</PROPERTY>
    <PROPERTY ID="CommandLine" Protected="True"></PROPERTY>
    <PROPERTY ID="CPU" Protected="True">x86</PROPERTY>
    <PROPERTY ID="Host" Protected="True">RemoteAgent.exe</PROPERTY>
  </PROPERTYCONTAINER>
  <FILECONTAINER>
    <FILE ID="RemoteAgent.exe" />
  </FILECONTAINER>
</PACKAGETYPE>

Place the remoteagent.exe built for X86 in D:\temp\X86 directory.

--

Anand R

fileviewer.zip

Writing Device Agent

What do I get if I write an my own agent?

• You can reliably start your agent. When the start call is completed you are guaranteed that your agent has started running in device.
• You can create stream independent of the underlying transport mechanism. You need not worry about whether DMA or TCP is the underlying transport.
  • You can use the streams for your device-desktop interaction
• You need not worry about serializing and de-serializing the data you send.
  • We provide a packet class which could be used to send and receive most of the basic data types.

Let’s see how we can write a device agent.

When an agent is started in device, it should call ‘AcknowledgeLaunch’.

Calling AcknowledgeLaunch signifies 2 things.

• Agent conveys that it has done with all its initialization and ready to accept connections from desktop
• It also registers the set of Ids that will be used to create streams.

Here is the code snippet to do AcknowledgeLaunch

HRESULT (*pfnGetDeviceService)(IDeviceAgentTransport**);

hMod = ::LoadLibrary(L "DeviceAgentTransport.dll");

if(hMod == NULL)

{

//Error Handle…

}

pfnGetDeviceService = (GetDeviceAgentTransportFunction) ::GetProcAddress(hMod,L"GetDeviceAgentTransport");

if( NULL == pfnGetDeviceService)

{

//Error Handle…

}

hr = pfnGetDeviceService(out_pTransport);

if(FAILED(hr))

{

//Error Handle…

}

//We got the DeviceAgentTransport. Call acknowledgelaunch to indicate all initializations are done.

hr = out_pService->AcknowledgeLaunch(count,lpServiceIds);

if(FAILED(hr))

{

//Error Handle…

}

Now, the Device agent is ready to accept connections…

IDevicePacketStream* out_pStream;

out_pService ->AcceptConnectionEx(lpServiceId ,&out_pStream);

AcceptConnectionEx is analogous to TCP accept call. This is a blocking call and will wait till a Connect (CreatePackaetStream) call is made from desktop with the same serviced. Note that this serviced has to be one among the registered service Ids (in AcknowledgeLaunch).

Send receive Packets

Let’s send some packets to desktop.

We need to create a packet, write the info into the packet and send the packet in stream.

GetNewPacketFunc packFunc;

HINSTANCE hMod = ::LoadLibrary(L "DeviceAgentTransport.dll");

packFunc = (GetNewPacketFunc) ::GetProcAddress(hMod, L"GetNewPacket");

if( NULL == packFunc)

{

//Error Handle…

}

IPacket *writePacket;

packFunc(&writePacket);

writePacket->WriteString(szSendString); //Some string to be sent to desktop

out_pStream->write(writePacket);

Just like in TCP, Read is a blocking call. Below call will wait till some data is sent from the desktop.

IPacket *packet;

packFunc (&packet);

hr =out_pStream->Read(&packet);

Desktop Side

So far we are discussing about how the device agent will look like. We will look at the desktop counterpart for this.

//PackageId is the Guid corresponding to the package we want to deploy

RemoteAgent mRemoteAgent = Device.GetRemoteAgent(new ObjectId(packageID));

//This will start the agent. This call will be blocked till AcknowledgeLaunch is called in device side.

mRemoteAgent.Start(“”);

//This is the connect call. 

//This will unblock the AcceptConnectionExe in device

DevicePAcketStream mStream = mRemoteAgent.CreatePacketStream(streamId);

Packet pkt = new Packet();

Pkt.WriteString(“hai”);

mStream.write(pkt);

pkt = mStream.Read();

string msg = pkt.ReadString();

Below is the sequence diagram for the desktop and device interaction

In next post we will look at actual File Viewer written using CoreCon API's.

--

Anand R

<?xml version="1.0" standalone="no"?>

<xsl:stylesheet xmlns:xsl="https://www.w3.org/1999/XSL/Transform" version="1.0">

  <xsl:template match="/">

    <ADDONCONTAINER>

      <ADDON>

        <PACKAGECONTAINER>

          <PACKAGE ID="0695ABA4-6A85-484d-8C07-5E67FE44D6BC" NAME="FileList">

            <PACKAGETYPECONTAINER>

              <PACKAGETYPE Name="ARMV4" ID="ARMV4" Protected="true">

                <PROPERTYCONTAINER>

                  <PROPERTY ID="RemotePath" Protected="true">%CSIDL_PROGRAM_FILES%</PROPERTY>

                  <PROPERTY ID="RootPath" Protected="true">%CSIDL_PROGRAM_FILES%\MyUtility\ARMV4</PROPERTY>

                  <PROPERTY ID="CommandLine" Protected="true"/>

                  <PROPERTY ID="CPU" Protected="true">ARMV4</PROPERTY>

                </PROPERTYCONTAINER>

                <FILECONTAINER>

                  <FILE ID="FileList.exe"/>

                </FILECONTAINER>

              </PACKAGETYPE>

              <PACKAGETYPE Name="ARMV4I" ID="ARMV4I" Protected="true">

                <PROPERTYCONTAINER>

                  <PROPERTY ID="RemotePath" Protected="true">%CSIDL_PROGRAM_FILES%</PROPERTY>

                  <PROPERTY ID="RootPath" Protected="true">%CSIDL_PROGRAM_FILES%\MyUtility\ARMV4I</PROPERTY>

                  <PROPERTY ID="CommandLine" Protected="true"/>

                  <PROPERTY ID="CPU" Protected="true">ARMV4I</PROPERTY>

                </PROPERTYCONTAINER>

                <FILECONTAINER>

                  <FILE ID="FileList.exe"/>

                </FILECONTAINER>

              </PACKAGETYPE>

              <PACKAGETYPE Name="X86" ID="X86" Protected="true">

                <PROPERTYCONTAINER>

                  <PROPERTY ID="RemotePath" Protected="true">%CSIDL_PROGRAM_FILES%</PROPERTY>

                  <PROPERTY ID="RootPath" Protected="true">%CSIDL_PROGRAM_FILES%\MyUtility\X86</PROPERTY>

                  <PROPERTY ID="CommandLine" Protected="true"/>

                  <PROPERTY ID="CPU" Protected="true">X86</PROPERTY>

                </PROPERTYCONTAINER>

                <FILECONTAINER>

                  <FILE ID="FileList.exe"/>

                </FILECONTAINER>

              </PACKAGETYPE>

            </PACKAGETYPECONTAINER>

            <PROPERTYCONTAINER/>

          </PACKAGE>

        </PACKAGECONTAINER>

      </ADDON>

    </ADDONCONTAINER>

  </xsl:template>

</xsl:stylesheet>

       fileDeployer.SendFile("FileList.exe", @"%CSIDL_PROGRAM_FILES%\FileList.exe");

With the below 2 lines

ObjectId packageObjID = new ObjectId("0695ABA4-6A85-484d-8C07-5E67FE44D6BC");

fileDeployer.DownloadPackage(packageObjID);

Device myDevice = GetPPC05Emulator();

myDevice.Connect();

FileDeployer fileDeployer = myDevice.GetFileDeployer();

fileDeployer.SendFile("foo.txt",@"%CSIDL_PROGRAM_FILES%\foo.txt");

This deploys the foo.txt (present in current directory) to “\Program files” folder in device. Note that you can use CSIDL paths in the both source and destination file names. CSIDL  values provide a unique system-independent way to identify special folders used frequently by applications, but which may not have the same name or location on any given system. Similarly there are APIs to do receive file and deploy bunch of files (using package) at a time. I will be discussing about the packages in detail in following blogs.

 RemoteProcess class gives us a way to start/stop process. Below code snippet starts a new process. Waits for some time (5 seconds), List all the process running and kills the started process.  

Device myDevice = GetPPC05Emulator();

myDevice.Connect();

//Start the calculator process in device

RemoteProcess remoteProc = myDevice.GetRemoteProcess();

bool bStarted = remoteProc.Start(@"%CSIDL_WINDOWS%\calc.exe", " ");

//List all running process

Collection<RemoteProcess> remoteProcCollection = myDevice.GetRunningProcesses();

int num = 0;

foreach (RemoteProcess rproc in remoteProcCollection)

{

num++;

      System.Console.WriteLine(num.ToString() + ". " + rproc.FileName);

}

//Kill the process

if (remoteProc.HasExited() == false)

{

remoteProc.Kill();

}

Let’s put all these together and write a small utility to do file listing in device. We will have a native app(FileList.exe) in device which will iterate the specified directory and print file names in a log. Our app will deploy this filelist.exe, run it with various parameters, get the log file and print in the console.

Create a Smartdevice console app targeting PPC 05. Copy paste the below code.

Source for FileList.cpp

/*

 * Gets the list of files/directories present int the path specified in cmd line argument.

 */

int _tmain(int argc, _TCHAR* argv[])

{

      int iRetVal = 0;

      if(argc <=1)

      {

            //No args passed

            return -1;

      }

      DeleteFile(L"\\foo.txt");

      HANDLE hLog = CreateFile(L"\\foo.txt",GENERIC_WRITE,0,NULL,OPEN_ALWAYS,FILE_ATTRIBUTE_NORMAL,NULL);

      if(hLog == INVALID_HANDLE_VALUE)

      {

            //Error in creating log file

            return -1;

      }

      //Search the Directory

      TCHAR* szPath = new TCHAR[_tcslen(argv[1]) + 4];

      _tcscpy(szPath, argv[1]);

      _tcscat(szPath, L"\\*");

      WIN32_FIND_DATA findData;

      HANDLE hSearchFiles = INVALID_HANDLE_VALUE;

      hSearchFiles = FindFirstFile(szPath, &findData);

      if(hSearchFiles != INVALID_HANDLE_VALUE)

      {

            do

            {

                  TCHAR* szBuffer = new TCHAR[_tcslen(findData.cFileName) + 4];

                  _tcscpy(szBuffer, findData.cFileName );

                  _tcscat(szBuffer,L"\r\n");

                  DWORD numBytes;

                  WriteFile(hLog, szBuffer, _tcslen(szBuffer)*sizeof(TCHAR), &numBytes, NULL);

                  delete[] szBuffer;

            }while(FindNextFile(hSearchFiles, &findData)) ;

      }

      else

      {

            iRetVal = -1;

      }

      //Clean up

      if(szPath != NULL)

      {

            delete[] szPath;

            szPath = NULL;

      }

      if(hLog != INVALID_HANDLE_VALUE)

            CloseHandle(hLog);

      if(hSearchFiles != INVALID_HANDLE_VALUE)

            CloseHandle(hSearchFiles);

      return iRetVal;

}

Create a C# console application. Copy paste the below code in program.cs.

Place the FileList.exe in the same directory as output directory.

using System;

using System.Collections.Generic;

using System.Text;

using Microsoft.SmartDevice.Connectivity;

using System.Collections.ObjectModel;

namespace sample1

{

    class Program

    {

        static void Main(string[] args)

        {

            Device myDevice = GetPPC05Emulator();

            //Connect to the device.

            myDevice.Connect();

            FileDeployer fileDeployer = myDevice.GetFileDeployer();

            fileDeployer.SendFile("FileList.exe", @"%CSIDL_PROGRAM_FILES%\FileList.exe");

            //Start FileList process in device

            RemoteProcess remoteProc = myDevice.GetRemoteProcess();

            bool bStarted = remoteProc.Start(@"%CSIDL_PROGRAM_FILES%\FileList.exe", @"\Program files");

            if (bStarted == true)

            {

                while (remoteProc.HasExited() == false)

                {

                    System.Threading.Thread.Sleep(2000);

                }

            }

            int exitCode = remoteProc.GetExitCode();

            if (exitCode == 0)

            {

                fileDeployer.ReceiveFile(@"\foo.txt", "Filelist.txt");

            }

        }

        static Device GetPPC05Emulator()

        {

            DatastoreManager dsmgrObj = new DatastoreManager(1033);

            ObjectId ppc05PlatObjID = new ObjectId("4118C335-430C-497f-BE48-11C3316B135E");

            ObjectId PPC05EmuID = new ObjectId("25D984D9-0DFE-4DB1-A5A0-9A4F660BF2CE");

            Platform ppc05Plat = dsmgrObj.GetPlatform(ppc05PlatObjID);

            Device ppc05Emu = ppc05Plat.GetDevice(PPC05EmuID);

            return ppc05Emu;

        }

    }

}

Now, this utility could be used to do file listing of device.

--

Anand R

Datastore is a set of XML files on your desktop computer that contains information about the platforms, devices, emulators, and packages that are installed on the computer. The contents of the Datastore are modified whenever you install an SDK that is based on Windows CE such as Windows Mobile.  Let’s start with an app which looks at the datastore and enumerate list of SDKs and devices installed in the machine.

[Create a new C# Desktop console application. Add reference to Microsoft.Smartdevice.Connectivity.dll which can be found at <systemdrive>:\Program files\Common Files\Microsoft Shared\CoreCon\1.0\Bin ]

If you have not downloaded these Bits yet you could do so from https://msdn2.microsoft.com/en-us/vstudio/aa700831.aspx . It also has details on how to log bugs and suggestions with the Product Team.

or you can just use our Blog to share your feedback.

Thanks

Amit Chopra

Program Manager VSD Team

For the VSD team, unit testing for NetCF(which we blogged about here) is a big-ticket item and we're super excited that you're finally seeing it in its close-to-final form. 

Testing non-public methods in Beta1

If you try to generate unit tests for a non-public method in Beta1, you'll see a comment saying "Generation of unit tests for private methods of device projects not supported". Don't panic - this is a temporary placeholder while we fixed a few issues with the code generation. You won't see this in the the next CTP/Beta for Orcas (as we've already fixed it internally). In the meantime, here's how you can easily work around this by writing a few lines of code and using the Smart Device Unit Test Framework.

In a nutshell, you can use the PrivateType and PrivateObject types found in the unit test framework to get at the ‘privates’ of your code.  Let’s look at a detailed example

Step1: Lets generate some code

First of all lets generate some test code  for below application which contains different kinds of non-public constructs. How to generate code can be found at https://msdn2.microsoft.com/en-us/library/ms364064(vs.80).aspx

using System;

using System.Collections.Generic;

using System.Text;

namespace BankAccountDemo.Business

{

    class BankAccount

    {

        // Properties

        private int _accountno;

        private float _currentBalance;

        private static float _bankAsset;

        private static int _newUniqueAccountno;

        private static int GetUniqueAccountNo

        {

            get {return _newUniqueAccountno++;}

        }

        private float CurrentBalance

        {

            get { return _currentBalance; }

            set { _currentBalance = value; }

        }

        // Constructors for new account

        private BankAccount(float initialBalance)

        {

            this._accountno = GetUniqueAccountNo;

            this._currentBalance = initialBalance;

        }

        // Methods

        private float DepositMoney(float depositAmount)

        {

            this.CurrentBalance += depositAmount;

           _bankAsset += depositAmount;

            return this.CurrentBalance;

        }

        private float WithdrawMoney(float withdrawAmount)

        {

            this.CurrentBalance -= withdrawAmount;

            _bankAsset -= withdrawAmount;

            return this.CurrentBalance;

        }

        private static float BankAsset()

        {

            return _bankAsset;

        }

    }

}

Step2: Add accessor class in Test Project to ease accessing the non-public code

Add a class to the test project (we call it BankAccountPrivateAccess in the example below). This class will contain the private accessor methods which can be used by testmethods to access non-public code

using System;

using System.Collections.Generic;

using System.Text;

using BankAccountDemo.Business;

using Microsoft.VisualStudio.TestTools.UnitTesting;

namespace TestProject2

{

    /// <summary>

    /// Accessor Class for BankAccount

    /// </summary>

    public class BankAccountPrivateAccess

    {

        PrivateObject m_privateObject;

        static PrivateType m_privateType =

            new PrivateType("SmartDeviceProject2",

                "BankAccountDemo.Business.BankAccount");

        /// <summary>

        /// Constuctor initializing private object to invoke methods

        /// </summary>

        /// <param name="target"></param>

        public BankAccountPrivateAccess(object target)

        {

            m_privateObject = new PrivateObject(target,m_privateType);

        }

        /// <summary>

        /// Return target object of non-public class to be tested

        /// </summary>

        /// <param name="target"></param>

        public static object CreatePrivate(float initialBalance)

        {

            object[] args = new object[] { initialBalance };

            PrivateObject priv_obj =

                new PrivateObject("SmartDeviceProject2",

                    "BankAccountDemo.Business.BankAccount",

                    new System.Type[] { typeof(float) }, args);

            return priv_obj.Target;

        }

    }

}

Step3: Add Private Accessor methods and properties in above class to access non-public methods and properties

Add the following method to access method DepositMoney

        public float DepositMoney(float depositAmount)

        {

            object[] args = new object[] { depositAmount };

            return ((float)(m_privateObject.Invoke

                ("DepositMoney", new Type[] {typeof(float)}, args)));

        }

Add the following method to access static method BankAsset

        public static float BankAsset()

        {

            object[] args = new object[0];

            return ((float)(m_privateType.InvokeStatic

                ("BankAsset", new System.Type[0], args)));

        }

Add following method to access property CurrentBalance

       public float CurrentBalance

        {

            get

            {

                return ((float)(m_privateObject.GetProperty("CurrentBalance")));

            }

            set

            {

                m_privateObject.SetProperty("CurrentBalance", value);

            }

        }

Add following property to access static property GetUniqueAccountNo

       public static int GetUniqueAccountNo

        {

            get

            {

                return ((int)(m_privateType.GetStaticProperty("GetUniqueAccountNo")));

            }

        }

You can use similar code to access any other member you have.

Step4: Modify the Generated Test Code to call methods of accessor class

Add following code to Test Deposit Money Test method

    // TODO: Initialize to an appropriate value

    object param0 = BankAccountPrivateAccess.CreatePrivate(5000);

    // TODO: Initialize to an appropriate value

    BankAccountPrivateAccess target = new BankAccountPrivateAccess(param0);

    // TODO: Initialize to an appropriate value

    float depositAmount = 0F;

    // TODO: Initialize to an appropriate value

    float expected = 0F;

    float actual;

    actual = target.DepositMoney(depositAmount);

    Assert.AreEqual(expected, actual);

    Assert.Inconclusive("Verify the correctness of this test method.");

Modify the other  testmethods to use your accessor class as well.

Voila! Your code is now testable using Orcas. Remember that this workaround is temporary – you won’t need to do any of this the next time you get Orcas bits.

The reason you see this behavior is due to a bug which existed in NetCF v2 RTM's icordbg.dll that we have fixed in SP1.

Check out: https://blogs.msdn.com/anandba/archive/2007/03/13/device-emulator-v2-is-live.aspx for details.

Anand Balachandran

-          ActiveSync not installed

-          Device is not ready

Reason:
In VS 2005 SP1 we did some bug fixes in conman2.dll (desktop side component) and conmanclient.exe (device side component). When you install SP1 both conman2.dll and conmanclient.exe (along with other binaries) get updated. If you have RTM version of conmanclient.exe running in your device then connection from desktop will fail (as the expected version of conmanclient.exe is not present in device).

If desktop component finds that conmanclient.exe is not of the same version it tries to shut it down, bootstrap the device (copy the device side binaries to device and start them).  In case of WinCE devices (e.g. CEPC), bootstrap being manual, will try to use ActiveSync and fails with an error message if the device is not connected through ActiveSync.

In case of emulator saved states this won't be any problem.  Desktop will be able to re-bootstrap the emulator using DMA bootstrap.  Because of the extra bootstrap, time to connect to the emulator saved state will slightly increase.

How to solve this:

If you have wince device with RTM binaries (conmanclient.exe, CMAcept.exe) then replace them with the SP1 binaries. Then run conmanclient.exe and cmaccept.exe from device. Now try the connection from desktop.

In case of emulator, connect to the emulator once using SP1. Now the newer (SP1) binaries will be present in the emulator. Create a fresh saved state out of this.

---

Anand R