Then you should give those right click whatever instructions. The other
thing just sounded weird I had no idea what it meant.


On Thu, Mar 6, 2014 at 1:29 PM, Toland Hon <notifications@github.com> wrote:

> In InnerFence.ChargeDemo.Phone/README.md:
>
> > +to see how the user experience flow will be like.
> > +
> > +INTEGRATION CHECKLIST
> > +=====================
> > +
> > +* Add the following files to you Visual Studio project:
> > +  * ..\InnerFence.ChargeAPI\ChargeException.cs
> > +  * ..\InnerFence.ChargeAPI\ChargeResponse.cs
> > +  * ..\InnerFence.ChargeAPI\ChargeResponse.cs
> > +  * ..\InnerFence.ChargeAPI\ChargeUtils.cs
> > +  * ChargeAPI\ChargeUriMapper.cs
> > +  * ChargeAPI\ChargeUtilsPhone.cs
> > +
> > +* Make sure your application is registered to handle a URL scheme:
> > +
> > +  * Using the XML (Text) Editor, open your app manifest file: `WMAppManifest.xml`
>
> The thing is when you double click the WMAppManifest.xml, Visual Studio
> opens it up in a manifest editor which doesn't expose the Protocol ability.
> You have to open it in Notepad to modify it. Here's what the MSDN arrticle
> says:
>
>  To register for a file association, you must edit WMAppManifest.xml
> using the XML (Text) Editor. In Solution Explorer, right-click the
> WMAppManifest.xml file, and then click Open With. In the Open With window,
> select XML(Text) Editor, and then click OK.
>
>  --
> Reply to this email directly or view it on GitHub<https://github.com/innerfence/chargedemo-windows/pull/2/files#r10361797>
> .
>