I created a Xamarin portable platforms app which contains four projects, Portable, Android, iOS and Windows Phone. When I make the Windows Phone project the start up project and then select menu > Project > Store, the store menu is disabled. St this point I am not able to reserve an app name or link my app to a registered app name. Menu item Associate app with the store is also disabled. Is there anyway of fixing this problem, I have no way of publishing my app.
An easier way to publish your app is through the dashboard. Go to http://dev.windows.com.
Sign in, reserve your app name and setup all the artwork etc for your app.
Then when you compile your Windows Phone or Store app, just get the generated file (.xap or .appx) and upload.
But to make sure the Store menu option is enabled also try these things.
1. Select the Windows Phone App in the solution explorer
2. Make sure you are in release mode
3. Make sure you have it compiling for ARM.
However I have never actually deployed from Visual Studio (something I should check in to). All I have in my menu is launching the Windows App Certification Kit.
Related
I have a windows 10 uwp app that runs fine when i have it sideloaded in my computer or any users computer where they have full admin priviliges. i use appxbundle and click on install button to install the same. Even powershell installation works fine.
Some of our clients don't have access to C: drive and the installation of UWP app is incomplete or fails because they don't have any install permissions.
Is it possible to run UWP app stand alone or specify a different install location which is other than C drive where user has both read and write permissions .
I tried to use .exe generated in the bin folder of uwp x64/Release folder but that doesn't run as uwp doesn't support exe
Currently, there is no such feature in UWP. UWP can't change the install process when installing, which means UWP apps can't choose where apps should be installed.
But there is a setting for Windows 10 that could change the location where the UWP apps are installed.
You could go to the Settings app and navigate to System > Storage.
Under the More Storage Settings heading click on the link that says Change where new content is saved.
You can choose one drive from the drop-down menu under "New apps will save to" and then click Apply. A new folder called "WindowsApps" will be created in the drive you've chosen. And any new UWP app will be installed in this folder. Please note Windows 10 will only install new apps to the currently selected location. Existing apps do not get moved to the new location.
Like this:
I made a new Xamarin Project in Visual Studio , I chose the Single View App .
Then I did not make any changes.
I just pressed the Run Button.
The emulator started ,
but the app was not appeared in the menu of the phone of the emulator.
Is there anyone who know what cause the problem?
On Windows you have a couple of options to accelerate the Emulator. Read more here: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows
Using HyperV: Make sure to install the Windows Hypervisor Platform:
Right click on the Windows button and select ‘Apps and Features’.
Select Programs and Features on the right under related settings.
Select Turn Windows Features on or off.
Select Hyper-V and click OK.
You probably need to restart your computer after.
Intel HAXM: If you are not using HyperV and don't intend and don't run other hypervisors such as VMWare, VirtualBox etc. then you can install Intel HAXM.
In the Android SDK manager, in tools, download Intel HAXM. After that is done, go to the folder where the Android SDK is installed. There should be an extras folder where there will be an installer for Intel HAXM.
On macOS, Intel HAXM is the way to go. Read how to install it here: https://learn.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=macos
Should be as easy as running sh ~/Library/Developer/Xamarin/android-sdk-macosx/extras/intel/Hardware_Accelerated_Execution_Manager/silent_install.sh from a command-line.
Either of these approaches should significantly speed up the Android Emulator.
If you have issues deloying to the emulator, sometimes the default configurations have very limited space and installing anything may fail due to the emulator running out of storage. Go to the Android AVD and increase the internal storage size.
For other failures, check the Deploy Output window in Visual Studio and provide more information of what is going wrong. Otherwise it is just a guess.
This might be just a bug. Create a new project. If still blank wait 5 minutes. Maybe your computer is slow so it takes time to load.
If you start using xamarin for the first time
Create device from dropout menu (don't just let it create it from pressing run button).
Select device from dropout menu.
Run up.
if it didn't added just restart Visual Studio (should change "Run" into name of the device)
My question is really simple: I’m a UWP developer and I developed some UWP app for the Win Store.
The problem is that I would want to use these apps on my own too, but I can’t, because I have to have deployed version from Visual Studio for testing new features and new versions.
To the point... is there a way, for an own UWP app, to have both “Store” and deployed version of it, right on the same PC with the same user?
For your scenario, we could make a project copy, and regard the copy as developer type, open the project with Visual Studio and double click Package.appxmanifest file then find Packaging tab option modify the package name to another. click the Local Machine button. You will find the new app in the start menu and the app will not override the store version.
Icon is not being displayed in Share menu next to my app name. But its displayed correctly in icon
I have added icons to all the options in visual studio
The assets you are using are right. At first, I didn't see any problem when I used RTM OS version (Version 1511, OS Build 10586.494). However, from your screenshot, it seems you are using Insider Preview Build. So I tested it again on Windows 10 Insider Preview Build 14393 and I can reproduce your issue.
Actually, your app icon is not invisible. It seems that System has cached the app icon used in Share menu when your app is deployed for the first time. After this, even we reset the app icon and redeploy the app, the icon in Share menu still won't change. I guess you've run your app with the default assets before you set your own assets. So in Share menu, it still use the default icon, but in Start panel, it is correct. You can created a new project with your own assets and then run this new project, you icon should be able to display in Share menu correctly.
This issue seems only affect Insider Preview Build. For Insider Preview issues, please feel free to share feedbacks with Microsoft. You can report this issue with Windows Feedback app. Your feedback has made Windows better!
All Logos Related to UWP are stored in Package.appxmanifest. Edit it using an xml editor. See if there is any image that is still a default icon.
Currently I have a solution with Windows and WP7 XNA projects in it.
Whenever I try to debug just the Windows project it thinks it needs the WP7 emulator and decides to launch it. I opened up the Configuration Manager and created a new configuration just for Windows debugging and unchecked the building and deploying of all my WP7 projects yet it still insists on having the WP7 emulator open.
Is there a way to stop this behaviour?
In Configuration Manager uncheck deploy next to windows phone project
I bet it's very similar to this issue with multiple ASP.NET Development Server instances loading up no matter what project is being debugged. I can't check this right now to be sure, but I bet there might be a similar setting to this "Always start when debugging" option for the emulator.
So opening the Properties Window (View->Properties Window, not the View->Property Pages one) and then clicking on the project in Solution Explorer, then look for a similar setting to "Always start when debugging".
Alternatively, have you tried setting the target to a be Device instead of the emulator? That might also be a workaround.
It's probably because It's set as the startup project:
How to: Set Startup Projects