I've updated my Windows Phone app from 8 to 8.1. Everything works, no problems testing it in either debug or release modes.
The issue is when I try to certify the app for the Store. I get the following notice about my Nuget package ImageTools:
The binary ICSharpCode.SharpZLib.Phone.dll is built in debug mode.
The binary ImageTools.Controls.dll is built in debug mode.
The binary ImageTools.dll is built in debug mode.
The binary ImageTools.Filtering.dll is built in debug mode.
The binary ImageTools.IO.Png.dll is built in debug mode.
The binary ImageTools.Utils.dll is built in debug mode.
I didn't have this problem in WP8. Perhaps something went wrong in the project upgrade? I've tried reinstalling the nuget package as well as manually placing the DLLs into the project.
I don't know how to build ImageTools in release mode. Any help appreciated!
Universal Apps (And Silverlight 8.1 Apps) have a different certification requirement. You cannot publish assemblies built in debug mode.
You'll need to contact the NuGet authors of ICSharpCode and ImageTools and have them provide you with a version built in release mode.
I modified the IL of the assemblies and removed the [Debuggable] attribute from them. The Windows Phone Store now allows the submission. You can download the patched assemblies here: https://github.com/brianhama/ImageTools-WP81
Related
I have a problem when I use the Windows App Certification Kit with the SharPDF-SL.dll. The test fails and says
The binary SharpPDF-SL.dll is built in debug mode.
I downloaded this library with NuGet so I can't rebuild the dll in release mode. Appreciate any help!
I managed to fix this bug. I compiled it for WP8.1 Silverlight project. If someone have the same problem, I share my solution.
source code : https://mega.nz/#!HhNElRSa!9GJXQvII0p1K3EHK7Y1VeIOPWBBbCE-vUU3UdZNsD5w
release dll : https://mega.nz/#!6g8TmR6I!P3XOfSRLaiCLbgVZ1RHktPxKbUWVE77Z-MojngnSxiE
I am just starting learning "Build 2D games with HTML5" from MVA and in starting i had a problem to configure my visual studio
Here is the link of that package Cordova-Windows package
The instructor shows that the Cordova windows package 3.5.0 contains CreateTemplates.bat file but it didn't work for me
i came up with this problem i dont know how to overcome this,
when i clicked the createTemplates.bat file its popup and off nothing happends so i try to open it up using command prompt and i get this errors , How to overcome?
what should i do now , your help would be highly appreciable !
You should use be using the Cordova CLI for your command line workflow for building Cordova Apps. For Cordova, more information is available here. If you want to use VS, then I strongly urge you to install our VS 2015 RC build which enables you to build Cordova applications for iOS, Android and Windows. More information for VS, is available here.
This question already has answers here:
Gradle build errors with Android Studio
(3 answers)
Closed 9 years ago.
I have just set up Android Studio 0.2.2 and updated my Android SDK to the latest version.
I have exported my Android project (android:minSdkVersion="8", android:targetSdkVersion="15") in Eclipse by 'Generate Gradle Build Files' without (visible) problems. And I can export/compile my app in Eclipse just fine, it also runs fine in the emulator.
However, in Android Studio, when trying to import my project, I am confronted with the above error message. "Gradle Home" is (IMO, correctly) displayed as "D:\Prog\Android-Studio\plugins\gradle".
Any idea how to make Android Studio feel more comfortable on my computer?..
I've encountered a similar problem where I can't import my project. There is at least one answer out there that may help; it requires the creation of a blank project in Android Studio and then copy files over from Eclipse. This ensures the creation by Android Studio of the necessary Gradle files, etc. Here's the link to the full answer: Gradle build errors with Android Studio
Look's like you should try to use the Gradle Wrapper rather than a local Gradle distribution. According to Gradle's website (http://www.gradle.org/docs/current/userguide/gradle_wrapper.html):
The wrapper is something you should check into version control. By distributing the wrapper with your project, anyone can work with it without needing to install Gradle beforehand. Even better, users of the build are guaranteed to use the version of Gradle that the build was designed to work with. Of course, this is also great for continuous integration servers (i.e. servers that regularly build your project) as it requires no configuration on the server.
You'll need to mimic the following structure in your project's directory:
simple/
gradlew
gradlew.bat
gradle/wrapper/
gradle-wrapper.jar
gradle-wrapper.properties
At that point, go to Settings (Windows) Preferences (Mac), click "Gradle" on the left hand side, choose "Use Gradle wrapper (recommended)". If that option isn't available, try restarting Android Studio or closing and reimporting your project. Checking this option should ensure that you always build with the correct Gradle distribution.
I have a native dll that I'd like to use in a WP8 project that I'm working on. I've done some research and have created a C++ Windows Runtime Component (WRC) to wrap the native DLL. The WRC project uses a .lib file, and my WP8 application calls the WRC project.
My solution compiles all fine, but when my application makes a call to a method in the native DLL, I get a The specified module could not be found. (Exception from HRESULT: 0x8007007E) exception.
From reading around it seems like the dll is not being loaded. I've copied all relevant dlls to the output dir of where the .exe file is and also in various places but the error keeps showing up.
If anyone could point me in the right direction I'd be very grateful. Also if more info is required I'll post that up also.
The DLL must be included in your XAP package. Something you can see being taken care of in the Output window when you build your app, it starts with the "Begin Xap packaging" messages and then lists all the files that get added. The runtime error says it is not being included.
There is remarkably little guidance on how to ensure that a file gets included in a phone package when MSBuild cannot figure out the dependencies by itself. It certainly won't for your DLL, no way the build system can tell if it isn't a project in your solution. Seems you're operating a bit on the bleeding edge in this case :)
But this works well when I try it, going by the MSBuild output and not by actually testing it: Project + Add Existing Item. Navigate to your DLL and select it. Select it in the Solution Explorer window and look in the Properties window. Ensure that "Build Action" = Content, Copy to Output Directory = "Copy if newer". Rebuild, you'll now see the file getting added to the XAP. Which should solve this particular error. There might be others :)
Windows Desktop or Windows Store native DLLs are not binary compatible with Windows Phone, even if they are built for the same CPU architecture.
Therefore you will need to recompile your native DLL for the Windows Phone toolset.
About Windows Runtime Components:
On Windows Phone a Windows Runtime Component is itself a native DLL (.NET is not supported on the phone). The binaries of Windows Runtime Components cannot be shared between Windows Store apps and Windows Phone apps.
The current SharpCompress.WindowsStore.dll library published on Nuget is build in Debug mode. I got this error from the Windows Store App Certification Kit.
Error Found: The debug configuration test detected the following errors:
The binary SharpCompress.WindowsStore.dll is built in debug mode.
Is there any way to have/compile the SharpCompress lib in Release Mode?
I'd rebuild it in release mode.
What, you didn't think about that?
It's on NuGet, right? NuGet packages often list a project site. So looking at the page I can see the link points right over here. That's on GitHub. That's where source lives.
You can either fork it (which there isn't really a point, since you don't want to develop it), clone it (aka use a Git tool such as GitHub for Windows) to your local machine, or just download the latest code in a zip file.
From there you can build in release mode and away you go. May not be just that easy, as there might be some dependencies or such that need resolving. Now off you go.