Hodentek Mobile

Wishing you all a Happy New Year 2019. Thank you for reading my blog. See you in 2019

Ractive.JS consists of a UI library that works with templates. Ractive JS library transforms style, logic to highly interactive apps. It has out of the box support for, Powerful and extensible components, two-way binding, scoped CSS, SVG support and animations. There are also plugins if the above are not sufficient. It does not have a very steep learning curve like other frameworks. It's origins are in the News media company, the Guardian . Originally used for producing News related applications where the demands and interactivity are very high. Nice thing is,  you are not locked to it like other frameworks. Here is the script reference to Ractive.JS If you want to download there are many references: # jsDelivr https://cdn.jsdelivr.net/npm/ractive # CDNjs https://cdnjs.com/libraries/ractive # unpkg https://unpkg.com/ractive # npm npm install --save-dev ractive # Bower bower install --save ractive Just go to the cdnjs.com above and click. When y

This error appears when you try to deploy the project to the Local Machine (x64). There are no errors during build or deploy stages. However, when you try to run the machine you come up with this message after the App shows up momentarily and disappears immediately. Trying to deploy to an emulator such as Mobile Emulator 10.0.14393.0 WVGA 4 Inch 512MB comes with the following errors. The emulator is running: However when you deploy it to a device (in this case Lumia 925) the app gets deployed with no errors. In order to proceed to package it for uploading to the Windows Store I am not sure just deploying it to the device is good enough. Is there a fix?

I faced quite a bit of downtime due to the wrong choice of the target version working with UWP Projects. Web search to find a cure sent me searching for answers I could not find. I am using Microsoft Visual Studio Community 2017 Version 15.8.1. The Dell alptop is running Evaluation copy of Build 17733.rs5_release(18083-1525). [ This OS has a problem in that when you shutdown and restart the OS, it will reinstall the OS afresh wiping out some of the folders; saved passwords; saved items in Microsoft Edge. Visual Studio also gets reset. ]. Now coming back to the right Target version for working with UWP projects, there are three options for the Target version shown in this image. RightTargetVersion_0 Of the three options only one of them allows the Desgin editor in Visual Studio come up without this error - The app did'nt start(HRESULT:0x8027025B) . This is the only one that works: Windows 10 Creators Update (10.0; Build 15063) . Regarding the choices for

Visual Studio's combo program Blend 2017 seems to have the C# templates missing in Visual Studio Community 2017, Version 15.7.5. Here is a New Project window open in Blend 2017. There are C# Windows Universal Project templates. It allows you create a new project, a UWP, C# Blank Project as shown but with errors. For the above these (default) were chosen. The design area of XAML displays System.Exception but the project builds alright. It fails to deploy and this is the error message: The package deployment operation is blocked by the "Allow deployment operations in special profiles" policy.    at Microsoft.VisualStudio.DesignTools.UwpDesignerHost.UwpHostPlatform.<>c__DisplayClass31_0. b__0()    at System.Threading.Tasks.Task.InnerInvoke()    at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown ---    at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

Recently installed Visual Studio Community 2017 with the following details: Microsoft Visual Studio Community 2017  Version 15.7.5 VisualStudio.15.Release/15.7.5+27703.2042 Microsoft .NET Framework Version 4.7.03062  I tried to run a previously well designed project by loading the project and failed. I noticed a number of errors such as these: The UI elements can still be seen in the XAML view in the MainPage.xaml and the same elements in the MainPage.xaml.cs are getting to be unrecognized by red wiggly (does not exist in the current context). some fifty errors CS0103 error Also the CS1061 error that the MainPage does not contain a definition for 'initialize Component' accepting first argument of type 'MainPage' could be found. I could not fathom the reason and spent about 6 hours. Then I resorted to recreate the app from scratch by creating a new C# project and noticed that the C# language related templates were missing. I am not sue if my errors are re

The Simulator for testing apps is not working. It can be launched but you cannot exit. You may exit the development environment by closing Visual Studio but the simulator hangs around. Apps open in the simulator does not work, or work sporadically. Here are details of OS and the Visual Studio versions in which this was noted: Here is the abandoned Simulator: I will be upgrading to the next version of Visual Studio Community 2017 shown here:

This error may show up if one chooses an image file that does not comply with the enumeration. Here is the description of the error: Severity Code Description Project File Line Suppression State Error  Validation error. error C00CE169: App manifest validation error: The app manifest must be valid as per schema: Line 26, Column 25, Reason: '' violates enumeration constraint of 'badge badgeAndTileText'. The attribute 'Notification' with value '' failed to parse. XXXXXX C:\Users\Owner\source\repos\xxxxxx\bin\ARM\Debug\AppxManifest.xml   I chose a resource for Badge in the Assets and Visual Studio spawned this error. The only way to get out of this was to comment out (or better remove) the following line in the AppManifest .xml Make sure you save the file after the removal as every time you Build, the AppManifest.xml gets recreated.

You can find this information using the Windows.System as shown here: Device_000 We can find the device to which the UWP is deployed using the above information. Here is a Blank UWP Project's MainPage.xaml. Device_0 I have a button and a text box. Button's click event finds the device information and writes to the text box using the click event shown here: Device_00 When deployed to the machine (Windows 10 Pro Desktop), the response is as shown. Device4.jpg When deployed to an emulator: The display shows the device info: You can get the DeviceFamilyVersion as well. The code is inside the image. On the emulator this is displayed.

You can store and retrieve composite application data in a UWP project using the Windows Storage. Specifically you will be using the Windows.Storage.ApplicationDataCompositeValue sealed class shown in the Object Browser. ObjBrowser.png In this post a project is described where in a pair of values are stored in the Windows Storage's local folder and retrieved. The values are stored using a button click event of a button and retrieved into text boxes in the click event of a second button. The MainPage.xaml for the project is as shown. MainPageXaml.png The code for storing and retrieving is shown in the MainPageXAMLCs. You first define the local settingss using the Windows.Storage.ApplicationDataContainer and the local folder . The composite values are set to the local settings. The retrieving is by extracting the values in the local settings and reading it into a text box. The result of running the application is shown here. The code can be simplified as