On the basis of the answer to this question, I installed the visual studio cordova app on my windows tablet.
I want to install the app on a few device permanently.
Is this the best way for it? (Without app store)
And with this way, I have to use a license which have a expiration date.
For test purpose, I think it's better to use developer sideloading, which is introduced in Developer sideloading Windows Store apps.
And the developer sdeloadig app dosn't expire.
Related
We have built a Windows 10 UWP app and have packaged it through Visual Studio as a Sideloaded app. The packages will be deployed on to user's machines by running powershell scripts. We are hoping to disable Sideloading in Developer features once the app has been deployed. However there isn't enough documentation available to see if a sideloaded app will work as usual or cause any errors in future once the sideloading in developer features for the machine has been turned off? Is there a way to safely achieve this.
The sideloaded app still is UWP app. Once the app installed successfully, disabling 'Sideload apps' in developer will not affect the installed apps. You needn't worry.
I am looking to develop a Windows 10 Universal app based in HTML, CSS, and JavaScript for use on Microsoft Surface tablets primarily. I have found information that says it can be done on this page, but at the very bottom of the page it says it is in beta. However, I can't seem to find anything more than that post. No updates, or documentation or anything. Does anyone know if you can do this from the PhoneGap app on Mac OS?
If not, I guess the next best option it to do it on a Windows machine using Visual Studio 2017 and Cordova?
Any information anyone has on this subject would be helpful.
Thanks!
No, I am pretty sure you can't build UWP apps on macOS. The reason is quite similar as the reason you cannot build iOS apps on Windows - you could build the JS portion of your code, but the problem is the fact that UWP build tools and SDKs are OS specific and unless Microsoft specifically ports them to macOS, they cannot work there.
You could use Parallels and run Windows as second OS, or use a build server to build the app in the cloud. Visual Studio App Center is a very good solution for you purpose as it allows you to configure a full build pipeline including UWP, iOS and Android builds.
You can actually develop a UWP app using phoneGap on Mac if you are building it using web technologies. (HTML, CSS, Javascript) But you can not build/publish the app on Mac, but if you have a Creative Cloud account, you can use Phone Gap Build to upload it to the service and have it built there.
I'm aware that a Mac or a Mac service e.g. MacInCloud.com is necessary for building and submitting iOS apps.
My question is about the actual workflow of building an app on Windows using Xamarin on Visual Studio 2017.
We need to write code, test and debug throughout development cycle. How does this work with Xamarin running on Windows? How would I actually see what my mobile app looks like or behaves during the actual development cycle?
While developing my web apps in Visual Studio, there are many trips back and forth to the browsers and back to VS in order for me to see the results of my code. How does this work with Xamarin running on Windows? Is Xamarin Live Player the only option for development cycle? Is there a solution through MacInCloud or similar services so that tethering a device to dev machine is not necessary?
I'm just trying to understand how a healthy development cycle is created for Xamarin developers on Windows.
I will answer your question in few section: Coding, Debug, Test
Coding
You will be using Visual Studio to write your codes. iOS and Android code will be written in C#. You will get access to UI Designer for both iOS and Android to edit the layout files and storyboard/xibs. For 3rd party library, there is NuGet to serve your needs.
Debug
You can use Xamarin Live Player without connection to a Mac/MacInCloud for basic preview. However, some features of iOS is not available in Xamarin Live Player (e.g. xibs files not supported...).
If you setup with connection to a Mac, you will be able to see a list of Simulator that available in the Mac you connected to. By default, if you debug it, the simulator will still show up in the Mac. Then you will need to VMWare or remote into the Mac to check the simulator output. If you have Visual Studio Enterprise license, you can get access to a Remote iOS Simulator feature. You will need to turn the option ON. After that, you will able to see a remote iOS Simulator showing in your Windows machine without the needs to remote into Mac machine anymore. For debugging in actual iOS devices, you will still need to plug your device into the Mac. Previously (more than 1 years ago), Xamarin announce that they are working on "iOS USB remoting" to allow you to plug in iOS device into Windows machine and debug on it. But it is not release until now.
For Android, you can get access to Android Emulator Manager to add emulator to debug or you can deploy apps to physical phone just like what you can do with Android Studio.
Test
I will be referring to Xamarin.UITest for this part. You will be able to write UITest code in C# inside Visual Studio. Xamarin have product "Xamarin Test Cloud" to allow you to upload test code and binary and then run your test in cloud periodically. If you want to run the test locally in your machine, you will only able to run Android UITest in windows machine. To run iOS UITest locally, you will only able to run it in Mac machine. Using a Mac, you can also run Android UITest.
You can use a simulator/emulator instead of a device. For iOS, the simulator would run on the Mac Build Host that you are connected to. You can select the option for "Remote iOS simulator" in Visual Studio -> Xamarin.iOS options and you'll be able to interact with the simulator without having to RDP/VNC/look at the mac. For android, you can just run an emulator in Window and interact with it like that. Using your web apps comparison, you would use a simulator/emulator instead of browser but, for the most part, the process would be similar.
I have been developing a Xamarin MVVM app targeted at iOS and Android. I initially did the iOS development on Windows with VS 2022 and an iPhone attached via USB. I knew that I was going to have to eventually move to the Mac for final provisioning but I ended up taking that painful step earlier than planned because certain Xamarin features were just not working on Windows. First I could not get my app icon to be anything other than the Xamarin default and then Xamarin.Essentials.FilePicker would not select a file:
https://github.com/xamarin/Essentials/issues/1710
So after a week of struggling I finally got my project building and deploying on the Mac. However, I am not nearly as comfortable working on the Mac as I am on Windows where I have all my familiar development tools. So then the question was how to share the project files between the PC and the Mac so that I could edit and compile on the PC and then move to the Mac for final testing.
At first I tried iCloud but I could never get the files to sync reliably between the shared folder on the PC and the Mac. I am used to Dropbox and OneDrive, which work as expected. iCloud not so much.
So what I have been doing is committing and pushing the changes to github and then pulling the changes into the project on the Mac. It is quick and has the added benefit of version control using an offsite server. I am happy with this workflow and publishing the app on the Apple Store should be an easy task when that time comes.
Update:
This process is still working for me. I have taken the additional step of doing the release configuration on VS Mac and publishing my app to App Store Connect. That experience was convoluted and frustrating but it now works and I have people testing my app via TestFlight.
One hiccup is that when selecting Automatic iOS Bundle Signing in the project properties on VS Windows, this change gets pushed to the Mac side and causes a build error under Debug until I select the Automatic provisioning profile on the Mac. Somehow it gets set to the Wildcard profile on the Windows side.
I want to deploy my first iOS App created with Xamarin Forms to the AppStore or at least to a single device. I have an Apple Developer Account and performed this task several times before using xCode and native iOS Apps.
But as a Windows guy I hoped to get this done for Xamarin using my VST for Windows.
But all guides and tutorials I found are only explaining how I can deploy iOS Apps to the store and to devices using VST for Mac ... Is this the only way? How do I get the code to the Mac? Can I use the TFS Source Control? Do I have to commit every little change to TFS, check it out at the Mac, rebuild the whole app there and deploy it from the Mac?
Or are there ways and workflows that work with Windows only having the Mac 'in the background' via network?
Take a look at https://mobile.azure.com (the best solution for continuous app development: analytics, crash reports, iOS/Android/UWP builds + deploy)
I'll address the second part of your question - the ability to deploy to a single device. I'm assuming that the single device is your own device and you want to deploy via compilation. This can certainly be done from your Windows machine but due to apple licensing requirements, you will need your Mac available to compile and deploy to your phone. Your iPhone/iPad will need to be plugged into your Mac's USB.
The guides listed on the Xamarin website outline how to set up the mac build host. https://developer.xamarin.com/guides/ios/getting_started/installation/windows/connecting-to-mac/ In short, you need some prerequisites (Remote Sharing turned on, XCode installed, etc).
Once you've connected Visual Studio to your Mac, set the iOS project as the startup project, change the config from Debug to iPhone, and press F5 to compile and deploy to your device.
When in doubt, select iPhoneSimulator instead of iPhone. The simulator isn't subjected to provisioning and signing profiles which can be daunting to setup. If you can get the simulator working, you've solved the software and connectivity prerequisites.
There's a lot to configure, but it does work. This is my primary setup for Xamarin.Forms development.
I have created an app using Xamarin, and it works great on Testflight and Google Play beta-testing (I am not ready to launch completely yet, but nearly).
I need to know, how am I going to create the package for Windows Store (or what it is called?).
If you are developing a windows phone app, you should have a developer account.
Now if you are ready to publish (or even before) go to the Windows Dev Center and create a new app in there. There you can see the following steps to publish your app in the windows app store.
If you don´t know what your developer account is or you don´t have one, start here: https://developer.microsoft.com/en-us/windows