For an application, while I make the final application, How could I remove the terminal window for the final application on MacOS or Linux.
I find the key point, that is in macos we should build a app file, which should consist of Resources folder、MACOS、PkgInfo、Info.plist files, then when I just click the packaged file, the application could just show the GUI window.
How do I get the UWP back into Xamarin.Forms Cross-Platform creation to have the templates ready to roll?
After picking through the release notes, playing with VS2019's UI and a few hours of web searching, I have only found others posting about the problem in the preview versions. Some say UWP is gone forever, some say it just isn't included by default (so Microsoft can brag about how the install went from 23GB to 8GB or something like that) - but no help on HOW TO re-enable it, or add it to the project creation wizard (apart from adding a blank UWP project sans all code that is in the iOS/Android projects).
<Project Sdk="Microsoft.NET.Sdk">
// the code is not the problem here,
// getting TO the code is the problem
</Project>
EXPECTED:
In VS2017, Xamarin.Forms Cross-Platform supplied iOS + Android + UWP templates by default.
ACTUAL:
Visual Studio 2019 seems to have removed the UWP template from Xamarin.Forms Cross-Platform project creation.
Update 9 apr.: a new version of 2019 was released which reinstates the UWP templates again
It is correct that the UWP template is removed from VS2019, I don't know the reason behind it, but we'll have to deal with it. There is however a page that runs you through the process step by step. It has been there for a while for the projects that were created in Visual Studio for Mac, which don't include the UWP template as well. The full description can be found here: https://learn.microsoft.com/en-us/xamarin/xamarin-forms/platform/windows/installation/ taken from this page:
First, right-click on the solution and select Add > New Project... and add a Blank App (Universal Windows) project:
Then, select the minimum and targeted UWP versions.
Right-click on the UWP project and select Manage NuGet Packages... and add the Xamarin.Forms package. Ensure the other projects in the solution are also updated to the same version of the Xamarin.Forms package.
Also, make sure the new UWP project will be built in the Build > Configuration Manager window (this probably won't have happened by default). Tick the Build and Deploy boxes for the Universal project:
Right-click on the UWP project and select Add > Reference and create a reference to the Xamarin.Forms application project (.NET Standard or Shared Project).
In the UWP project, edit App.xaml.cs to include the Init method call inside the OnLaunched method around line 52:
// under this line
rootFrame.NavigationFailed += OnNavigationFailed;
// add this line
Xamarin.Forms.Forms.Init (e); // requires the `e` parameter
In the UWP project, edit MainPage.xaml by removing the Grid contained within the Page element. Then in MainPage.xaml, add a new xmlns entry for Xamarin.Forms.Platform.UWP, like this: xmlns:forms="using:Xamarin.Forms.Platform.UWP".
In MainPage.xaml, change the root <Page element to <forms:WindowsPage, like this:
<forms:WindowsPage
...
xmlns:forms="using:Xamarin.Forms.Platform.UWP"
...
</forms:WindowsPage>
In the UWP project, edit MainPage.xaml.cs to remove the: Page inheritance specifier for the class name (since it will now inherit from WindowsPage due to the change made in the previous step)
public sealed partial class MainPage // REMOVE ": Page"
In MainPage.xaml.cs, add the LoadApplication call in the MainPage constructor to start the Xamarin.Forms app:
// below this existing line
this.InitializeComponent();
// add this line
LoadApplication(new YOUR_NAMESPACE.App());
Add any local resources (eg. image files) from the existing platform projects that are required.
And now it should work as before. I know, it's a hassle to go through it for something that just worked before. Sorry about that, but this should get you there as well.
With the Update 16.0.1, Microsoft restored the UWP creation on new Xamarin.Forms applications
except when you try to use Shell, which is not available for UWP:
Issues fixed in Visual Studio 2019 version 16.0.1
Add option for Windows (UWP) platform when creating new Xamarin.Forms project from 'Mobile App (Xamarin.Forms)' project
template.
EDIT (7/17/2021): i have started a new xamarin forms solution and it seems all 3 platforms are available again in VS2019 on all prebuilt templates (blank, master-detail, tabbed layout).
thank you, everyone, for your input.
great information!
it helped me steel myself to face the fact:
UWP is gone (for now) from Xamarin.Forms new project scaffolding.
but, the (simplest) solution to the question asked that i have found is:
open VS2017. create new Xamarin.Forms cross-platform project.
once it is open, save-all.
then close VS2017 and open in VS2019 if so desired.
I have an open source application I wrote for my own use that is a text and clipboard reader for Microsoft Windows. The application, which I unimaginatively named TTSApp, can be found on my web site.
The application uses MFC and can be built with either Visual Studio 2013 or Visual Studio 2015, although window resizing only works properly when it is built with Visual Studio 2013. It uses MFC and, as a result, cannot easily be ported to other platforms or compilers.
It currently uses either SAPI 5 or the Microsoft Speech Platform for speech.
I have a GetTitle function that constructs the title of the application to indicate what configuration is in use, SAPI or Microsoft Speech Platform, and what architecture is in use, x86 or x64. For example, the title of the Microsoft Speech Platform configuration built for the x64 platform is "SnKOpen TTSApp - Microsoft Speech Platform - x64." This tile is used for both the window title of the dialog box and App Name (the value returned by the function is passed to the constructor of the CWinApp class). Note that the App Name is used to generate the windows registry key that application settings are stored in.
I have not been able to figure out how to set the title of the Windows 10 Task Bar icon context menu. The following screen shot will illustrate what I mean.
I would like to set the TTSApp in the above image to be the same as the dialog box title bar.
I tried calling CWinApp::SetAppID, which in turn calls the SetCurrentProcessExplicitAppUserModelID Win32 API function, from the constructor of the CTTSAppApp class, but that did not do it.
The description of the SetCurrentProcessExplicitAppUserModelID implies that this is the way to accomplish what I want since the function "Specifies a unique application-defined Application User Model ID (AppUserModelID) that identifies the current process to the taskbar."
Does anyone have any suggestions about what I should attempt next?
I'm trying to create this application on Visual Studio 2010 using Forms with ComboBox
http://pastebin.com/bV7SF3ni
How you can see in this code all forms is fine but i'm don't know how put option in code
I don't have idea how make this , i maked another project using forms to but with button instead comboBox.
http://pastebin.com/rk61drrY
This is working but i want in combobox and i want too when click on option open vnc and close this software.
I recently started developing an app in C++ & Qt 5.1 and I would like to have the double-arrowed icon on the title bar of my window like other Mac apps.
I created a QtQuick 2 Application project and the default code doesn't make this button appear.
I noticed that QtQuick 2 UI default project shows this button.
I really don't understand why. Is there someone who can help me ?
Thanks a lot for your answers,
jnconte.
I don't have experience with qtquick, but if it's the same project file as Qt, you would create the icon (icns file) and add it to the project file like this: -
ICON = images/icon.icns
The icon.icns file, in this case, is in a folder called images, relative to the project file.