Alaa Serry on Tue, 12 Apr 2016 14:09:31
I used the article “Windows Universal Apps Reach SDK Integration” to add ME to my Universal Windows App. However, I am having hard time locating the Microsoft.Azure.Engagement.Overlay name space. I guess it was not automatically added when the ME package was installed.
What am I missing here?
PS. Microsoft.Azure.Engagement name space is present
Piyush_MSFT on Wed, 13 Apr 2016 17:27:07
I am assuming this is a Windows 10 project. You have to follow the steps below which would have showed up when you installed the Nuget. This is due to a limitation of Nuget pkg manager that it does not copy the content files anymore and just the binaries.
* Open your File Explorer.
* Navigate to the following location (x.x.x is the version of Engagement you are installing): %USERPROFILE%\.nuget\packages\MicrosoftAzure.MobileEngagement\x.x.x\content\win81
* Drag and drop the "Resources" folder from the file explorer to the root of your project in Visual Studio.
* In Visual Studio select your project and activate the "Show All files" icon on top of the "Solution Explorer".
* Some files may not be included in the project. To import them at once right click on the "Resources" folder, "Exclude from project" then another right click on the "Resources" folder, "Include in project" to re-include the whole folder. All files from the "Resources" folder are now included in your project.
Alaa Serry on Wed, 13 Apr 2016 19:32:23
Hi Piyush and thanks for a prompt reply.
You are right it is a Win10 Universal app.
I have done that already and here are the contents of the resources folder
Piyush_MSFT on Thu, 14 Apr 2016 19:17:10
So are you saying that even after adding the resources you are not able to get the namespace? That shouldn't happen. Maybe try compiling the blank project + SDK in it first and see if the namespace shows up. Also - is it not showing up in intellisense on you get compilation error when you include it?