The markup in the configuration files contains a few placeholders (marked with a $ in front) which Icenium replaces with their correct values during the build process. With the configuration files in place, what's left is the actual code editing. Here's how the App_Resources folder looks like after dragging and dropping the files in the Solution Explorer. (You need to create the xml folder.)Ĭonfig.xml for iOS goes to App_Resources\iOS. To avoid some tedious editing of the project file, drag-and-drop from Windows Explorer to the Solution Explorer does an excellent job.ĪndroidManifest.xml goes to App_Resources\Android.Ĭonfig.xml for Android goes to App_Resources\Android\xml.
Once the files are created, they need to go to their proper places in the file structure of the project. What's next is to copy and paste the following templates (already available in Graphite and Mist) and save the changes.īecause Visual Studio is way more advanced in its code editing features, let's leave the editing for later. So, any not-so-simple text editor is sufficient to create four empty files named AndroidManifest.xml, ist, config.xml, and, guess what, another config.xml. One: Create the files on the local systemĪndroidManifest.xml, ist, and the Cordova config.xml files are all XML files. The long answer is that modifying the configuration files turns out to be as easy as one, two, three. Am I to resort back to the cumbersome workflow of building my app, unpacking it, editing the files, repacking and code signing the app manually? But what about the Icenium Extension for Visual Studio? No sign of the context menus I already know from Graphite and Mist, no indication of the files in the file structure of the project either. In Graphite and Mist, it takes just a right-click to get to AndroidManifest.xml, ist, and the Cordova config.xml files. Now, how do I set a new display name for my app, remove the gloss effect from the icons, use a custom URL scheme, or achieve some other advanced task available only through the configuration files? My custom plugins are working as expected.
The simulator is working fine, code signing is already configured thanks to my previous work in Graphite, my app deploys on devices. I installed the Icenium Extension for Visual Studio, created a new project, and started development.
(This is a guest post by Iva Koevska, a technical writer on the Icenium team at Telerik.)
0 kommentar(er)
