In trying to run integration tests on my windows store app but the sideloading of my test appx file fails with error (0x80073CF3):
Windows cannot install package (my package GUID) because this package depends on another package that could not be found. This package requir
es minimum version 12.0.21005.1 of framework Microsoft.VCLibs.120.00 published by any publisher to install. Provide the framework along with this package..
The same procedure works fine on my dev machine (from powershell).
A Microsoft blog post states:
...In order to facilitate this scenario for sideloaded apps, we have made
the framework packages available here.
After downloading, and extracting the relevant architecture appx file, I installed it via powershell:
Add-AppxPackage "C:\temp\Microsoft.VCLibs.120.00_12.0.21005.1_x86__8wekyb3d8bbwe.appx"
Related
I am building an app with Xamarin Forms and XLabs plugins.
To be able to run everything smoothly on Android and Windows Phone, i've had to use a prerelease version of xlabs (2.2.0-pre05).
When I tried to create a Windows Phone appstore package the certification failed because the packages for 2.2.0-pre05 have been built in debug mode.
To overcome this, I cloned the git hub project for XLabs and built everything in release mode.
The problem is, when I try to build the project with the packages i've built, I get this error:
Payload file '..\packages\Mike Xlabs\XLabs.Platform.WinRT.Phone\FodyWeavers.xml' does not exist.
Also, the windows store certification checks fail because of libraries used by the prerelease package.I'm getting the following error:
Error Found: The supported APIs test detected the following errors:
This API is not supported for this application type - Api=D2D1GetGradientMeshInteriorPointsFromCoonsPatch. Module=d2d1.dll. File=SharpDX.Direct2D1.dll.
Impact if not fixed: Using an API that is not part of the Windows SDK for Windows Phone Store apps violates the Windows Phone Store certification requirements.
I'm trying to build a SSIS 2016 project, that's been configured with the Project Deployment model in a VSTS build with the intent to deploy the .ispac file onto a SQL Server VM hosted in Azure.
Using MSBuild to build the project file returns the following error:
The default XML namespace of the project must be the MSBuild XML namespace.
If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element.
If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
I found a blog post here describing the same issue
https://speaksql.wordpress.com/2013/06/07/a-journey-to-db-deployment-automaton-ssis-build-using-msbuild/
However, the solution depends on installed SQL Server Data Tools into a build agent.
Is there a method where I can use a VSTS Hosted agent, and not have to create an on-premises agent with SSDT installed?
Just released new Extension for VSTS/TFS
https://github.com/ToxicGlobe/VSTS-SSIS-Extension
It build Visual Studio project, containing packages and parameters to a project deployment file (.ispac)
https://marketplace.visualstudio.com/items?itemName=TG.VSTS-SSIS
For similar scenario i used devenv.exe
Tool : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Arguments : .\Code\Database\NameOfSolution.sln /build $(BuildConfiguration)
devenv.exe /build does not require ssdt to installed on build agent
Looks like Microsoft is not supporting this just yet based off UserVoice
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/11543292-install-sql-server-data-tools-ssdt-for-sql-serve
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/4850300-install-sql-server-data-tools-for-bi-on-the-team-f
My project structure is defined like this:
LIB Com basic communication, (requests and responses)
LIB Com.BackgroundTask background task that will fetch new messages from server
LIB Com.Mediator background logic that will handle every exchange of information and interaction between Com and the ViewModel
LIB Model all Models for the Project, also the Databases should be defined here.
LIB Settings App settings.
Windows App Views/Controls for Windows
Windows Phone App Views/Controls for Windows Phone
Shared Basic App logic, Mediator init, ViewModels
the Problem is that you cannot reference the SQLLite extension in the (Portable) LIB Model but this is essentialy for the project structure to work. Otherwise the BackgroundTask would never be able to update the Database, am i right?
You can refer SQLite in a portable class library project using Portable Class Library for SQLite. This project has been initiated by Microsoft Open Technologies, Inc. working with the community.
This portable class library for SQLite available as NuGet package
simplifies the installation and development experience for .NET
developers by providing a single interface across Windows Phone,
Windows Store and .NET Framework 4.5.
With this solution .NET developers can develop against one portable
class library and do not have to worry about what assembly is loaded.
Drawback: Targeting x64 platform architecture is not supported at the moment.
Targets supported: x86, and AnyCPU (with "Prefer 32-bit" option marked).
Pre-requisites:
1) The developer visits http://sqlite.org/download.html, and downloads the required precompiled binary for Windows v3.8.5 (http://sqlite.org/2014/sqlite-dll-win32-x86-3080500.zip), extracts the sqlite3.dll file, and adds it as Copy-Always Content to the root folder of the project.
2) In Visual Studio, the developer uses NuGet Packet Manager Console to install the SQLitePCL wrapper package.
Inside the Package Manager Console, type: Install-Package SQLitePCL
I have a VS 2013 solution with a WP8 App, a WP8 Library for my viewmodels, a WP8 Unit Test project to test my library and other standard unit tests projects. The solution is under TFS 2012 source control, the build controller is setup and it correctly build my solution.
But my WP8 specific tests are not ran after automatic build. All other standard Unit Tests projects run well.
Some additional infos:
the ".xap" package for the test project is well generated
the build process Template (Default Template) is setup to use "Visual Studio Test Runner"
the build agent is running interactively
when i launch vstest.console.exe from the command line, giving the ".xap" package as argument, the test are well discovered and executed
I'am i missing something in the configuration ?
Windows Phone apps are currently not supported on Team Build, as documented here.
Feature | Windows Phone | Windows Store App
Team Build support | Not supported. | Includes support for running unit tests as part of Team Build.
There are a few unsupported work-arounds to solve your issue, more an be found here.
Is it possible to use the protobuf-net library in an application that targets Windows RT? I tried adding it via NuGet to my project but I receive this error:
Successfully installed 'protobuf-net 2.0.0.480'.
Successfully uninstalled 'protobuf-net 2.0.0.480'.
Install failed. Rolling back...
Could not install package 'protobuf-net 2.0.0.480'. You are trying to install this package into a project that targets '.NETCore,Version=v4.5', but the package does not contain any assembly references that are compatible with that framework. For more information, contact the package author.
You need a newer version. Version 594 has support for 4.5.
In the package manager console (Tools->Library Package Manager->Package Manager Console) run:
PM> Install-Package protobuf-net -Version 2.0.0.594
Or download it from the project web site.
Yes, the more recent builds have full support for .NETCore (aka "WinRT", "Windows Store Applications", or "Metro", or "Modern UI", or whatever they want to call it today). As Eli notes, you can obtain it by specific version, or you can get it from the google-code download.
Note that for the best performance it is recommended to use "precompile", the new precompiler, because .NETCore has no support for meta-programming: without this, it will be using reflection at runtime, and will not be anywhere near as fast as it can be. This is included in the google-code download.