{"id":1733,"date":"2014-03-13T19:30:00","date_gmt":"2014-03-13T19:30:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/visualstudioalm\/2014\/03\/13\/using-application-insights-for-windows-phone-8-0-direct3d-c-apps\/"},"modified":"2022-07-18T02:12:42","modified_gmt":"2022-07-18T10:12:42","slug":"using-application-insights-for-windows-phone-8-0-direct3d-c-apps","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/using-application-insights-for-windows-phone-8-0-direct3d-c-apps\/","title":{"rendered":"Using Application Insights for Windows Phone 8.0 Direct3D C++ Apps"},"content":{"rendered":"

You can currently use Application Insights to find out how people use your Windows 8.1 Store Apps<\/a> & Managed Windows Phone 8.0 Apps<\/a>. We\u2019ve been asked about Phone 8.0 Direct3D C++ Apps as well, which the NuGet Package currently does not support. Here is a workaround that can enable you to use Application Insights for these apps.<\/p>\n

Download the NuGet Package<\/h3>\n

Download<\/a> the \u201cApplication Insights Telemetry SDK for Windows Phone Apps\u201d NuGet package which contains the reference files we will use for our Direct3D C++ App. Once the package is downloaded, unzip and copy the \u201c\/build\/wp80\u201d folder to the solution directory or anywhere you want to keep the reference files. Open the \u201cwp80\u201d folder and rename \u201cx86\u201d to \u201cWin32\u201d. Here is what you will eventually get:<\/p>\n

\"Pic<\/p>\n

Add Reference<\/h3>\n

Right click your Windows Phone 8.0 Direct3D C++ App project, select Add<\/strong>, Reference<\/strong>, Add New Reference<\/strong>,** Browse** and select Microsoft.ApplicationInsights.Telemetry.WindowsStoreInternal.winmd<\/strong> from either the \u201cArm\u201d or the \u201cWin32\u201d folder.<\/p>\n

\"Pic<\/p>\n

At this stage you will be able to use the Application Insights APIs for one specific platform (ARM or Win32). But you might want to switch the target platform between developing, testing, deploying, and packaging. You can ensure that the correct platform specific reference file gets picked up automatically:<\/p>\n

    \n
  1. Right click the project in Solution Explorer and select Unload Project<\/strong>.<\/li>\n
  2. Right click the project again and select Edit yourProject<\/em><\/strong>.vcxproj<\/strong>.<\/li>\n
  3. In the .vcxproj file, find the \u201cMicrosoft.ApplicationInsights.Telemetry.WindowsStoreInternal\u201d reference.<\/li>\n
  4. In that reference block, edit the \u201cHintPath\u201d by replacing the name of the platform folder (e.g. Arm or Win32) with \u201c$(Platform)\u201d.<\/li>\n
  5. Save the file and reload the project by right clicking on the project name in Solution Explorer.<\/li>\n<\/ol>\n

    For example, in my case, I have the following reference added:<\/p>\n

    \n <<\/span><\/span><\/span>Reference <\/span><\/span>Include<\/span><\/span>=<\/span><\/span>“<\/span>Microsoft.ApplicationInsights.Telemetry.WindowsStoreInternal<\/span><\/span>“<\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    \n \u00a0\u00a0\u00a0 <\/span><\/span><<\/span><\/span><\/span>HintPath<\/span><\/span>><\/span><\/span>……….DownloadsMicrosoft.ApplicationInsights.Telemetry.WindowsPhone.0.6.56.3buildwp80<\/span>Win32<\/span><\/span>Microsoft.ApplicationInsights.Telemetry.WindowsStoreInternal.winmd<\/span><\/<\/span><\/span>HintPath<\/span><\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    \n \u00a0\u00a0\u00a0 <\/span><\/span><<\/span><\/span><\/span>IsWinMDFile<\/span><\/span>><\/span><\/span>true<\/span><\/<\/span><\/span>IsWinMDFile<\/span><\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    \n <\/<\/span><\/span><\/span>Reference<\/span><\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    And I will edit that to get this:<\/p>\n

    \n <<\/span><\/span><\/span>Reference <\/span><\/span>Include<\/span><\/span>=<\/span><\/span>“<\/span>Microsoft.ApplicationInsights.Telemetry.WindowsStoreInternal<\/span><\/span>“<\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    \n \u00a0\u00a0\u00a0 <\/span><\/span><<\/span><\/span><\/span>HintPath<\/span><\/span>><\/span><\/span>……….DownloadsMicrosoft.ApplicationInsights.Telemetry.WindowsPhone.0.6.56.3buildwp80<\/span>$(Platform)<\/span><\/span>Microsoft.ApplicationInsights.Telemetry.WindowsStoreInternal.winmd<\/span><\/<\/span><\/span>HintPath<\/span><\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    \n \u00a0\u00a0\u00a0 <\/span><\/span><<\/span><\/span><\/span>IsWinMDFile<\/span><\/span>><\/span><\/span>true<\/span><\/<\/span><\/span>IsWinMDFile<\/span><\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    \n <\/<\/span><\/span><\/span>Reference<\/span><\/span><\/span>><\/span><\/span><\/span>\n<\/p>\n

    Now the correct reference will be picked up automatically, based on the target platform.<\/p>\n

    Get your Application Insights component ID<\/h3>\n

    The next step is to provide an ID to the SDK that ensures that your data appears under your application component name in Application Insights.<\/p>\n