Visual Studio 2017 and Windows App Certification Kit: test errors - windows

I'm trying to publish my app on the Microsoft Store. When I run the Windows App Certification Kit I receive for each action an error related with Microsoft.Windows.SoftwareLogo.TestBase.
I'm using Visual Studio 2017 Version 15.9.3
Bytecode generation
Error Found: The bytecode generation test detected the following errors:
System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.IsPackageWWA(AppXPackage package) at Microsoft.Windows.SoftwareLogo.Tests.BytecodeGenerationCheck.BytecodeGenerationCheck.ExecuteSharedValidation(String manifestFilePath, String packageFullName) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
Impact if not fixed: As a performance optimization to accelerate JavaScript execution time, JavaScript files ending in the ".js" extension generate bytecode when the app is deployed. This optimization significantly improves start-up and ongoing execution times for JavaScript.
How to fix: You may need consider one or more of these steps to fix the issue:
- Avoid deploying the app by pressing F5 in Visual Studio, create an app package instead
- Ensure that event logging is enabled
- All JavaScript files are syntactically valid; otherwise exclude the respective files from the package
- Please note that you should uninstall all previous versions of the app before deploying
Otherwise exclude the respective files from the package.
I verified in my Visual Studio Installer and the Windows SDK in installed.
Also, I checked the targeting version of the project:
Target version: 1809 (10.0; Build 17763)
Min version: November Update (10.0; Build 10586)
There is not SDK for this build...

Related

Cannot install Visual Studio 2017 due to Microsoft.VisualStudio.Setup.Configuration package install failure

I cannot install the above mentioned package, which is requied to proceed the Visual Studio install. I checked on Microsoft's forums for solution but no luck.
I unchecked read-only checkbox in the root of the directory, also manually recreated x64 and x86 folders. The permissions on the users are as they should be also the cleaner app didn't help. I am using the 1809 Windows edition. The current VS version is 15.9.4.
The log is the following:
Something went wrong with the install.
You can troubleshoot the package failures by:
1. Search for solutions using the search URL below for each package failure
2. Modify your selections for the affected workloads or components and then retry the installation
3. Remove the product from your machine and then install again
If the issue has already been reported on the Developer Community, you can find solutions or workarounds there. If the issue has not been reported, we encourage you to create a new issue so that other developers will be able to find solutions or workarounds. You can create a new issue from within the Visual Studio Installer in the upper-right hand corner using the "Provide feedback" button.
================================================================================
Package 'Microsoft.VisualStudio.Setup.Configuration,version=1.18.21.37008' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.VisualStudio.Setup.Configuration;PackageAction=Install;ReturnCode=1317
Details
MSI: C:\TempTmp\Nova mapa\Microsoft.VisualStudio.Setup.Configuration,version=1.18.21.37008\Microsoft.VisualStudio.Setup.Configuration.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 ALLUSERS="1" MSIFASTINSTALL="7" 
Return code: 1603
Return code details: Fatal error during installation.
Message Id: 1317
Message Details: An error occurred while attempting to create the directory: C:\ProgramData\Microsoft\VisualStudio\Setup
Log
C:\TempTmp\dd_setup_20181215215511_001_Microsoft.VisualStudio.Setup.Configuration.log
Impacted workloads
Game development with Unity (Microsoft.VisualStudio.Workload.ManagedGame,version=15.0.27005.2)
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.9.28307.102)
Visual Studio core editor (Microsoft.VisualStudio.Workload.CoreEditor,version=15.0.27205.0)
Impacted components
.NET Native (Microsoft.Component.NetFX.Native,version=15.0.26208.0)
.NET Native and .NET Standard (Microsoft.VisualStudio.ComponentGroup.UWP.NetCoreAndStandard,version=15.8.27906.1)
.NET Portable Library targeting pack (Microsoft.VisualStudio.Component.PortableLibrary,version=15.6.27309.0)
.NET profiling tools (Microsoft.VisualStudio.Component.DiagnosticTools,version=15.8.27729.1)
ASP.NET and web development (Microsoft.VisualStudio.ComponentGroup.WebToolsExtensions,version=15.8.27825.0)
Blend for Visual Studio (Microsoft.ComponentGroup.Blend,version=15.6.27406.0)
C# and Visual Basic (Microsoft.VisualStudio.Component.Roslyn.LanguageServices,version=15.8.27729.1)
ClickOnce Publishing (Microsoft.Component.ClickOnce,version=15.8.27825.0)
Data sources and service references (Microsoft.VisualStudio.Component.VisualStudioData,version=15.6.27406.0)
Developer Analytics tools (Microsoft.VisualStudio.Component.AppInsights.Tools,version=15.8.27825.0)
Image and 3D model editors (Microsoft.VisualStudio.Component.Graphics,version=15.6.27406.0)
JavaScript and TypeScript language support (Microsoft.VisualStudio.Component.JavaScript.TypeScript,version=15.9.28125.51)
JavaScript diagnostics (Microsoft.VisualStudio.Component.JavaScript.Diagnostics,version=15.8.27729.1)
NuGet package manager (Microsoft.VisualStudio.Component.NuGet,version=15.9.28016.0)
Universal Windows Platform tools (Microsoft.VisualStudio.Component.UWP.Support,version=15.9.28119.51)
Universal Windows Platform tools for Cordova (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.9.28307.102)
Universal Windows Platform tools for Xamarin (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.9.28307.102)
Visual Studio core editor (Microsoft.VisualStudio.Component.CoreEditor,version=15.8.27729.1)
Visual Studio Tools for Unity (Microsoft.VisualStudio.Component.Unity,version=15.7.27617.1)
WebSocket4Net (Component.WebSocket,version=15.0.26606.0)
Update 1.1.2019
I contacted the Microsoft support over chat, but didn't get any further. I was told to try to install an earlier release. I ended up formatting my SSD and installing all the software all over. It luckily succeeded. I am providing a vslogs overview of the error, before the format.

DEP0600: Deployment failed. XmlException – Data at the root level is invalid

When I deploy a UWP from VS 2017, I’m seeing the following error:
DEP0600: Deployment failed. XmlException - Data at the root level is invalid. Line 24, position 11.
Any clues on how to resolve?
After much debugging and Binging, an SDE pointed out that I was hitting a known bug in Windows 10 Creators Update – which will be fixed in the upcoming Fall Creators update. At install time, all of the installed package are enumerated to see if the package has already been installed. This enumeration fails if the installed app’s AppxManifest.xml file is malformed.
I had several test apps installed on my machine, some deployed with Visual Studio, some installed with PowerShell using the command:
Add-AppxPackage -Register .\PackageLayout\AppxManifest.xml
After uninstalling several of the test apps, I was able to deploy my app with Visual Studio 2017 without problems.

Error while building cordova app for release

Getting error
Error MSB3819 Cannot find assembly
"plugins\cordova-sqlite-storage\src\windows\SQLite3-Win-RT\SQLite3\SQLite3.UWP\release\SQLite3.UWP\SQLite3.UWP.dll",
which may contain managed resources that need to be included in this
app package. Please ensure that this assembly exists.
[platforms\windows\CordovaApp.Windows10.jsproj]
While building windows app for release using visual studio 2015
Although is it working fine for debug mode.

Cannot load shared 'project' in Windows Universal app after upgrading to Azure SDK 2.6

I've just installed the April 2015 release of the Azure SDK. It is version 2.6 and previously I was on 2.5. Now one of my projects will not load. It is the shared project in a Windows Universal application.
When I right-click the project and choose 'reload' I get the pop-up error
The method or operation is not implemented
The output window gives more detail:
Things.Shared.shproj : error : The composition produced a single
composition error. The root cause is provided below. Review the
CompositionException.Errors property for more detailed information.
1) No exports were found that match the constraint:
ContractName Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
RequiredTypeIdentity Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService
Resulting in: Cannot set import
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")'
on part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.ProjectReferencesService
(ContractName="Microsoft.VisualStudio.ProjectSystem.References.IBuildDependencyProjectReferencesService")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
Resulting in: Cannot get export
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")'
from part
'Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService'.
Element:
Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService.WireUp
(ContractName="Microsoft.VisualStudio.ProjectSystem.ConfiguredProject.AutoLoad")
--> Microsoft.VisualStudio.Azure.Deployment.ProjectReferenceMaintenanceService
The other parts to the Windows Universal app (the Windows 8.1 project and the Windows Phone 8.1 project) have two Azure NuGet packages installed: Windows Azure Mobile Services 1.3.2 and Windows Azure Storage 4.3.0. (N.B. Those two projects load without issue.)
This is not a show stopper for me since uninstalling the Azure SDK 2.6 removes the load failure. To uninstall I go via the Control Panel to 'uninstall or change a program' and then uninstall Microsoft Azure Tools for Microsoft Visual Studio 2013 - v2.6
I would like to know how to fix this without uninstalling the Azure SDK 4.6.
Over on the Azure Mobile Services forum Chuck Weininger has posted the following answer:
The [fixed] build of Azure SDK 2.6 is now available, but it may not have
propagated to all download servers yet.
You can run the Web Platform Installer and if you don’t have the new
build installed, it should allow you to install 2.6 again. But it
might not if you are accessing a download server that doesn’t have the
new bits yet. If WebPI doesn't allow you to install 2.6 again, then
wait a few hours and try again.
The build number for the version with the fixes is build
2.6.30508.1601. You can identify the build of the SDK from Control Panel -> Programs and Features -> Microsoft Azure Tools for Microsoft
Visual Studio 2013 – v 2.6. The Version column will display the build
number
I have followed Chuck's instructions and have the new build and the shared project now loads without issue.
We have been able to reproduce the issue, but don't have a workaround at this time. If you want to use the Universal App projects with VS 2013, you will have to uninstall Azure SDK for VS 2.6. The issue does not happen on VS 2015 RC if you would like to give that a try. We hope to have news soon about how we can get a fix for this issue on VS 2013.
Chuck Weininger, Dev Lead, Microsoft
https://social.msdn.microsoft.com/Forums/en-US/e8123821-dcb1-477f-a746-f6f016a724ea/cannot-load-shared-project-in-windows-universal-app-after-upgrading-to-azure-sdk-26?forum=azuremobile&prof=required#de621720-3afc-458c-ba85-f691be9e74c1

application failed to initialize properly (0xc0150002) [duplicate]

This question already has answers here:
The application failed to initialize properly (0xc0150002)
(5 answers)
Closed 5 years ago.
my mfc application created in visual studio 5 running on windows server 2000 sp4, i create a release for it and try running it win xp slp2. it gives me application failed to initialize properly (0xc0150002)
i have tried following things
-Install Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) the one that comes within the release folder as well as one downloadable from website
copied all dll and mainfest from microsoft visual sutdio\vc\redist
I still keep receiving the same messsage. c
what could be wrong?how can i fix it
some things to check:
check the /SUBSYSTEM linker option for you project. It might include OS major/minor version numbers.
ensure that you are using appropriate Windows XP PlatformSDK on DEV machine; check values of WINVER, _WIN32_WINNT
use depends to see whether the problem is in unresolved dependencies
check the version of runtime that your application requires with that on target machine. I usually do this by looking at the app's manifest from one side and into WinSxS folder of the target machine from another (recently there had been an ATL Security update from Microsoft http://msdn.microsoft.com/en-us/visualc/ee309358.aspx; new binaries created by updated Visual Studio will not run on machines that haven't the same updated version of runtime).
It is possible you have applied a security update or compiler update to your VS2005 SP1. That makes it generate a manifest that requests a different MFC/CRT-dll than the one installed with Microsoft Visual C++ 2005 SP1 Redistributable Package (x86) .
Try to use Depends.exe and open your application, then in the menu choose "Profile". Look in the output window below for a more detailed description.
Are you trying to run the debug version? That may give you an error similar to 0xc0150002. Try the release build, or you could compile against the static libraries rather than dynamic libraries. If you get this problem on a release build then the chances are that it's a missing dll (in which case try running Depends.exe) or an incorrect manifest.
If you have a missing dependency on a runtime dll you could try creating a deployment project for it as this will detect the appropriate runtime dlls and build it into an installer for you.

Resources