Totally Blank Unity / Microsoft Store Build fails WACK tests - c#

I have been trying to get a successful build for my game in Unity 2018.2.1f1 and Visual Studio 2017 15.8.0.
After trying unsuccessfully to get a successful build / package / WACK for the windows store with all/every different configuration, I tried a totally blank default Unity, UWP platform app, generated a visual studio project. generated some icons, associated it with an app I had in the store. Built it, packaged it and run the WACK tests.
FAILED
Supported APIs
Error Found: The supported APIs test detected the following errors:
API ExecuteAssembly in uwphost.dll is not supported for this application type. WinTest2.exe calls this API.
API DllGetActivationFactory in uwphost.dll is not supported for this application type. WinTest2.exe has an export that forwards to this API.
Impact if not fixed: Using an API that is not part of the Windows SDK for Microsoft Store apps violates the Microsoft Store certification requirements.
How to fix: Review the error messages to identify the API that is not part of the Windows SDK for Microsoft Store apps. Please note, apps that are built in a debug configuration or without .NET Native enabled (where applicable) can fail this test as these environments may pull in unsupported APIs. Retest your app in a release configuration, and with .NET Native enabled if applicable. See the link below for more information:
What do I have to do to make a successful app build that I can actually get into the store. (What configuration, what unity / visual studio versions.) I have tried later versions of unity 2018.2.1 and 2018.2.2 (i think) and could not get a successful build out of them.
A while ago, i could not get a successful build out of Unity, so I reinstalled Win 10 Pro, Unity and Visual Studio. Still problems persist.

Thanks to StormBringerStudios I received an answer that works.
"Just Got Visual Studio 2017 15.7.6 version. works like a charm.
So here is my Solution is anyone will search this kind of problem DONT USE VS 2017 15.8.X.
Downgrade to 15.7.6 and you will be good :)
Microsoft certification also passed."

Related

Problem with AzureStorageEmulator.exe Azure SDK and Visual Studio related

Premise: I'm a frontend web developer and I had to launch a project written in C# that has many dependencies. I tried to set the enviroment but I had many issues, this is one that neither I, nor the people around me, can resolve (at least we couldn't until now).
When I try to run the solution it always throws an error and open a popup where it writes something like "it is not possible run Azure storage emulator. Run AzureStorageEmulator.exe as administrator and try again". I tried to run the command but it tells me that it is not installed. I unistalled and installed again the Azure SDK, still the error, I installed the storage emulator from here https://learn.microsoft.com/en-us/azure/storage/common/storage-use-emulator#using-sdk but nothing.
What can I do?
I'm using Visual Studio 2019, .net core 2.2 and Azure SDK
Sorry for my funny English, I'm not native.

Xamarin Deployed Faild Object Reference Not Set To An Instance

I've been trying to setup mobile development on VS2015 for several days. The issue is
I created blank app
Started Emulator From Xamarin Android Player
Started Debugging
I got my solution built succeed but deploy failed. Here is image
I checked the error list but as we can see it is nothing there.
Well, I searched on internet with different queries and came to know that this problem is quite common but no permanent solution is provided. Some of the solutions suggested on other sites including Xamarin Official Forums are as follows:
Restart debugger.
Install valid Java Sdk Manager.
Restart Visual Studio.
Install android packages for targeted platform.
Create virtual device.
Change settings in Hyper-V manager.
Set your project as Startup Project.
Uninstall android components and reinstall them.
Disable Fast Deployment Option in Project Properties.
I tried everything but issue stands still. The packages I have installed for SDK are in image as follows
I don't know what part of package installation I am missing or there is some problem with VS2015. I have been trying to resolve this deployment issue but in vain.
Note*: I am using HP EliteBook 8460p with Win 10 64-bit installed on it.

VS2015 Community ASP.NET5 Dependency injection and azure publish errors after UWP update

Until recently i had working asp.net 5 mvc webapi project. It worked locally and i was able to push it to azure cloud (publish option).
About week ago i started to work on universal windows app for rasberry pi 3 - so i installed necessary package (Visual Studio Tools for Universal Windows Apps) with couple more updates from gallery (new version for ASP.NET and Web Tools probably).
When i got back to working on webapi project i've noticed warnings:
DOTNET1015 The 'compilationOptions' option is deprecated. Use
'buildOptions' instead.
DOTNET1015 The 'exclude' option is deprecated. Use 'exclude' within
'compile' or 'embed' instead.
DOTNET1015 The 'publishExclude' option is deprecated. Use
'publishOptions' instead.
in my project.json file
So something must have changed after those updates.
Project build passes but when i start it locally on debug and IIS Express i get:
An unhandled exception of type 'System.InvalidOperationException'
occurred in Microsoft.Extensions.DependencyInjection.Abstractions.dll
Additional information: No service for type
'Microsoft.Extensions.PlatformAbstractions.IApplicationEnvironment'
has been registered.
And when i try tu push it to azure i get some errors in my language (polish) about metabase problems and wrong format of paths eg. lm/w3svc//ROOT/
my project.json file: http://pastebin.pl/view/f823f093
VS info: http://pastebin.pl/view/86bae236
I try to clean and rebuild solution, restore packages but its probably something else.
What can i do except of uninstalling VS and instaling one more time?
Complete uninstall of VS 2015 Comunity and clean install of AspNet5.ENU.RC1_Update1_KB3137909 did the trick for me. Problematic update probably was
https://visualstudiogallery.msdn.microsoft.com/c94a02e9-f2e9-4bad-a952-a63a967e3935?SRC=VSIDE

Building Metro Apps for beta testing

I have created a Metro application, but I did not yet send it to Windows Store as it's still in beta. One of my friends was interested in testing my application. To install my application on hes computer I used sideloading, following the steps in this article : http://blogs.msdn.com/b/patricka/archive/2012/11/05/how-do-i-deploy-a-windows-8-app-to-another-device-for-testing.aspx . The problem is that, when a press "Y" (yes) and PowerShell should install my app, it gives an error "The package or bundle is not signed or it's digital signature is corrupted. ". What should I do ? I sent him all the files that were generated by the Visual Studio.
I have to mention that :
I'm using Windows 8.1
I've developed the app in Visual Studio 2013 Professional
The target platform of my app is Windows 8.1 (and I have no idea how to change this)
My friend does not have Visual Studio installed
My friend uses Windows Server 2012 Datacenter (Could
this be the problem ? What should I do in this case ? I'm very
interested that my app to work also on Windows 8, Windows Server 2012
because this are the OS-es that are used at my office and by a
majority of the people with whom I work and that could test my app
before releasing it to the market. )
EDIT : I tried to follow the steps in this article http://msdn.microsoft.com/en-us/library/windows/desktop/jj835836(v=vs.85).aspx , but my error does not appear to be listed there.
In AppxPackagingOM > Microsoft-Windows-AppxPackaging/Operational I have the next error:
error 0xC00CE014: App manifest validation error:
The app manifest must be valid as per schema: Line 27, Column 8, Reason: Element
'{http://schemas.microsoft.com/appx/2013/manifest}VisualElements' is unexpected according
to content model of parent element '{http://schemas.microsoft.com/appx/2010/manifest}Application'.
Expecting: {http://schemas.microsoft.com/appx/2010/manifest}VisualElements.
Also in AppXDeployment-Server > Microsoft-Windows-AppXDeploymentServer/Operational I have no errors.
After reading your question again, I see the obvious solution.
The target platform of my app is Windows 8.1 (and I have no idea how
to change this)
...
My friend uses Windows Server 2012 Datacenter
You need to target Windows 8 to make it run on 8/2012. And if you check out MSDN, you'll see:
If you want to create a Windows 8 version of your app, you must use
Microsoft Visual Studio 2012.
Please make sure you have created beta app package in release mode not in debug mode. This is wrong from here.
Also check out Can Windows Server 2012 run all Metro (/ Windows Store) applications?

C# Form Automatically closes when visual studio is not installed

I wrote an application with .Net4 and C# and also deploy it to user system with install shield.
After I changed few lines of code, one of my Winforms automatically disposes** without error in client system which has .Net4 but does not have Visual Studio installed.
All prerequisites are installed and it used to work fine...
If I install Visual Studio in client's system, it will work perfectly.
I tried to debug it but visual studio does not find any exception.
Please help
Form may contain components that are not present in client's system.
It depends upon way in which you are deploying your application.
General way is:
Install framework.
Copy-Paste debug folder to client's system.
Bring shortcut to desktop.
OR
Simply publish the application.
Copy paste publish folder to cliet's System.
Execute publishing setup.
Bring shortcut to desktop.
It works in this way.
Hope its helpful
You wrote on the user machine .Net 4 Client framework is installed. Try to uninstall it and install full .Net 4 framework (here is a link to MS download site).
Those 2 lines that you have added may now reference the features that are available only in full .Net 4 installation. (Unfortunately you did not post those lines so we can only guess what the problem is).
With Visual Studio full .Net 4 is installed and maybe because of this your app starts to work after VS installation.
See Difference between .NET 4 Client Profile and Full Framework download for more details.

Categories

Resources