I am developing a Windows 8 application. I tested the app with Windows Certification Kit, and it was throwing the following error:
Debug configuration test
FAILED
Debug configuration
• Error Found: The debug configuration test detected the following errors:◦The binary myappname.exe is built in debug mode.
• Impact if not fixed: Windows Store doesn’t allow a debug version of an app.
• How to fix: Please make sure the app isn’t linking to any debug versions of a framework, and it is built with release configuration. If this is a managed app please make sure you have installed the correct version of .NET framework.
Any suggestions on what this means and how to solve this problem?
To fix this you need to rebuild your application in release mode then re-run the certification test, the test will never pass if you build Debug.
Related
I've developed app in VS2015 which needs to run on target computers that have Windows XP, NET 3.5. The release and debug versions of the application work without any problems on those computers.
I then made a Setup Project to be able to install the application on target computers and I did so that it requests no additional requirements. I ran the installer on my lap top which is Windows 7 and it works fine but on those target computers I get a message when i try to install the app:
"The installer was interrupted before 'App Name' could be installed.You need to restart the installer to try again."
I tried to find out what is the problem but without a success. I read that it could be problem that I am trying to install an application that was developed in VS2015 and that I need older version, but I couldn't understand why or what to do to make it work. Any help would be appreciated. Thanks!
EDIT1: I've checked and XP computers do have 3.5 NET installed. I also checked the event viewer and error I receive is: "Installation success or error status: 1603"
I've tried the resolutions that Microsoft suggests for this error, but didn't succeed.
EDIT2: I've checked permissions for the installation everything is as should, but still getting the error.
Since I start application from Debug and Release folder directly and it works perfectly, I am sure the problem is in the installer. Any help?
I am trying to run one of the samples from the Windows Universal Samples package:
https://github.com/microsoft/Windows-universal-samples
I have properly unzipped all of the files required and changed the platform target to x86 from ARM.
However I still get this error:
DEP6957: Failed to connect to device '127.0.0.1' using Universal Authentication. Please verify the correct remote authentication mode is specified in the project debug settings. COMException - No connection could be made because the target machine actively refused it. (Exception from HRESULT: 0x8007274D) [0x8007274D]
Does anyone know how to resolve this?
DEP6957: Failed to connect to device '127.0.0.1'
I have research some similar issue here, And the provided solution is modify the debug platform from Arm to others. I found you have used x86 platform, please try to test with x64 and clean and rebuild your solution.
Are you trying to run against an ARM desktop device? If not this is just an obnoxious quirk of Visual Studio where it defaults to the ARM configuration when you first load the solution. You need to choose x64 from the platform target dropdown.
On my primary development machine I created an app that can be deployed but lacked advertising. That machine broke and was sent in for repair, thankfully after I committed the working application to source control. I brought up a spare machine, checked out my project making many improvements including successfully displaying adds in the windows 10 UWP application. After repairs were completed on my primary development machine I updated templates, and SDKs that had changed during the repair, ?I believe I got them all?. I checked out the project and after a successful build attempted to deploy and debug.
2>------ Deploy started: Project: Decisive.Uwp.T10, Configuration: Debug x86 ------
2>Updating the layout...
2>Copying files: Total 1 mb to layout...
2>Checking whether required frameworks are installed...
2>Framework: Microsoft.Advertising.Xaml/x86, app package version 10.0.1510.0 is not currently installed.
2>Installing missing frameworks...
2>Error : DEP0800 : The required framework "C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.Advertising.Xaml\10.0\.\AppX\x86\Microsoft.Advertising.Xaml.x86.10.0.appx" failed to install.
2>error 0x80070005: Opening the package from location Microsoft.Advertising.Xaml.x86.10.0.appx failed.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========
I removed the Microsoft.Advertising.Xaml, Version=10.0 leaving the Microsoft.AdMediator.Universal, Version=1.0 The app will now deploy and run but doesn't appear to display adds. I noticed the following warning;
(I don't know how to format the following with wrap so it doesn't need to be scrolled many page widths. I've left it as a paragraph.)
The SDK "Microsoft.AdMediator.Universal, Version=1.0" depends on the following SDK(s) "Microsoft.Advertising.Xaml, Version=10.0", which have not been added to the project or were not found. Please ensure that you add these dependencies to your project or you may experience runtime issues. You can add dependencies to your project through the Reference Manager.
The versions of these two libraries match between the two machines used to created this app.
I'm at a loss attempting to resolve this error Error : DEP0800 : The required framework "C:\Program Files (x86)\Microsoft SDKs\Windows Kits\10\ExtensionSDKs\Microsoft.Advertising.Xaml\10.0.\AppX\x86\Microsoft.Advertising.Xaml.x86.10.0.appx" failed to install.
Additional Information 10/21/2015 2008 MST
FWIW With both references intact, in a state where it won't deploy to my windows 10 notebook locally or in the emulator, I deployed to a windows phone mobile emulator. No errors, app runs. Doesn't appear to be displaying ads though.
On the spare machine where the app will deploy to windows 10 locally and display ads, ads are displayed in both the win10 emulator and the mobile emulator.
Additional Information 10/22/2015 0930 MST
The comments on this post regarding WinTools 1.1, TypeScript 1.6 RTM, and Tools for Apache Cordova Updates may shed some light on the problem. They detail a problem that some developers have experienced installing the win tools 1.1 update that apparently the AdMediator relies on.
I had some great hindsight and you can see what assumptions made out of me.
I got in touch with a PM at Microsoft who stated;
Yes, we are aware of the issue that you are talking about. But that
issue might be a red herring in this context – it is all about just
false notifications showing up when you do the upgrade. That should
not have really caused the issue with the AdControl (if you truly had
the issue with a bogus install of the tools, you could not even create
or build a UWP app of any kind).
Eventually I tried running Visual Studio as Administrator. I was able to deploy the app. Afterwards I exited Visual Studio then restarted with normal privileges. I am now able to deploy the app without running Visual Studio as Administrator.
Well, I'm getting started in applications android development, as I'm familiar with C#.NET(and I love it), I decided to use the fantastic MonoDroid project. I downloaed and installed,worked fine until now. I created hello world application, using MonoForAndroid_API_8 emulator device, worked fine.
then I copied *.apk files and installed in my tablet with android OS 2.2, but when I run my application,I get the following error:
The xx.xx application (xx.xx process) stopped unexpectedly. Try again.
how to fix this? Any help is very appreciated. Thanks in advance.
You can find information here about how to view the Android logs.
I'll take a guess at what your problem is though, without having seen the logs. Are you using the full version of Mono for Android or the evaluation? The eval doesn't support deploying to an actual device.
If you are on the full version, is the APK from a debug build or release? Debug builds are made to use a shared runtime to make deployments quicker, but it means that the APK doesn't contain everything the app needs to run. Release builds don't use the shared runtime, so the Mono runtime is bundled with the APK.
My machine:
Windows XP (x86), VS2008, .net 3.5, sql server 2005, WinForms -> App works fine.
Production Machines: Windows 7 (x64), SQl Server 2005 Express -> App Starts but throws exception
Visual Studio Targeting x86 on setup project and RMO project. Visual Studio gives me a a couple warnings but I can still build:
Unable to find dependency 'MICROSOFT.SQLSERVER.MANAGEMENT.SQLPARSER' (Signature='89845DCD8080CC91' Version='10.0.0.0') of assembly 'Microsoft.SqlServer.Smo.dll'
Unable to find dependency 'MICROSOFT.SQLSERVER.MANAGEMENT.SQLPARSER' (Signature='89845DCD8080CC91' Version='10.0.0.0') of assembly 'Microsoft.SqlServer.Management.SmoMetadataProvider.dll'
This is a simple RMO (Replication Management Objects) app that initiates a pull subscription in SQL Server 2005 and displays status. Works fine on my machine, but fails on the production machine. I'm using a setup project to install the app on the production machine, but I think I'm missing a dependency somewhere, but I can't figure it out.
On the production machine the app starts fine, but when I try to synch the subscription i get:
System.IO.FileNotFoundException: The Specified module could not be found. (Exception from HResult: 0x8007007E)
EDIT: Task Manager in Win 7 inditcates that it is running as a 32-bit app (myapp.exe *32).
EDIT: Ok, my app is now showing in task manager that it is a 64 bit app, but I'm getting an error. I'm thinking that I some how have a dependency dll targeting x86. How can I verify the dependency dll is targeting the correct platfrom and/or make sure that it is targeting x64... I thought the setup prjoect would rebuild the dll in my detected dependencies to target whatever cpu I chose in the setup project?
Could not load file or assembly 'Microsoft.SqlServer.Replication, Version=10.0.0.0, Culture-neutral, PublicKey Token=89845dcd8080cc91' or one of its dependencies. An attempt to was made to load a program with an incorrect format.
run Fusion Log viewer as administrator and set it to Log Bind Failures to Disk.
that way you'll be able to see which DLL's don't load properly.
I thought the setup prjoect would rebuild the dll in my detected dependencies to target whatever >cpu I chose in the setup project
the setup does not compile any dlls for you automatically.
An attempt to was made to load a program with an incorrect format.
look here, on where to find an x64 version of 'Microsoft.SqlServer.Replication'
http://social.msdn.microsoft.com/Forums/en/sqlreplication/thread/628ec2ae-c5d1-4aef-b31b-b889975bfc2b