Today I was preparing my Windows 8.1 app package with release configuration (x86) to go in production stage, so in Visual Studio I set up the release configuration with x86 CPU and it builds.
Unfortunately when I run the app in release mode the access to DataStorage (and SqlLite) fails throwing exception "Unable to load .... error 0x8007007E".
Any other change in configuration of my solution and project did not help at all.
I've tested also a new blank Universal App project referencing the 2 dll about the Telerik DataStorage as Always. In Debug configuration it works without problems but if I change Platform configuration into Release it gives me the same issue.
I'm using the last release of UI for Windows Universal.
Please can you help me with this issue? I think it's a serious bug/issue since it affects blank projects too.
Thank you in advance.
7 Answers, 1 is accepted
We are aware of this issue and we have fixed it. The fix will be available with our internal build which will be released later today or on Monday.
Thank you for your feedback. Please, let me know should you have any other questions.
thank you for your prompt reply.
I need asap your fix as I have to go in production stage next week on 3 June.
Please advice me when you have your internal build ready and how to get it.
Thanks in advcance.
The build in question is live. You can go to Products & Subscriptions > UI for Windows Universal.
On the right, select Latest Internal Build.
This week's internal build will bi displayed in the list below, look for 2015.1.529.xx
I've really appreciated your effort .
Ves and Allesandro -
Were you able to get this working? I downloaded the hotfix and updated the application to reference the updated SDK. However I am still getting the same error in Release configuration on both the emulator and on the device.
I've attached a screenshot of an app that is reproducing the problem. It is just displaying the version number of the Storage dll and then listing the contents of the install directory.
Any help would be greatly appreciated as we are close to submitting to the store.
Currently we provide automatic installation/replace/upgrade of the existing binaries for official releases only. For hot fixes/internal build releases you should manually replace old binaries with the new ones, exactly as you did.