I am developing an app using Flutter, and I want to be able to test some functionality that behaves slightly different depending on the device directly on both an iPhone and an Android device.
I am using a Linux machine with Visual Studio Code as my main development machine (and do not want to change that), and on that machine Visual Studio Code is deploying to an Android emulator (or a real device).
Then I have a Mac, which has also got Visual Studio Code installed. I mounted the "lib" directory from the Linux machine via sshfs to the Mac (the rest of the Flutter project is just copied to there, since for example I do not want to share the build-folder). From there Visual Studio Code deploys the app to either the simulator or a real iPhone.
With this setup, whenever I change a file, Visual Studio Code on the Linux maching deploys directly to Android. However, since file system events do not get picked up on the Mac due to sshfs, Visual Studio Code on the Mac does not directly deploy. I only have to trigger a hot deployment though (which I mapped to F5), so even now it is only one keypress I have to do on the Mac.
My question is, can I somehow automate this last step? I was thinking about using ssh to connect from the Mac to Linux, and then pick up the filesystem events via inotify. But how could I then trigger a hot deployment on the Mac?
Related
I want to run emulator for Android Studio on a Linux platform. Upon contaction Google (since I'm using Google server) I was told this : "nested virtualisation is not enabled out of the box for Compute Engine instances. Therefore you need to enable it manually," and was given this link for further query "https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances". Can anyone help me with this since I'm not getting the exact procedure to run an emulator for Android Studio on a Linux platform hosted on a Google server.
So, I have a project being built and test on Windows platform, since Visual Studio 2017 works and run program most comfortable for me in Windows. Now, that I have completed debug most part of the code, I'll have to change my platform built target to Linux.
I used an external project (lib) to help with the internet control, which it's built target is also Windows.
Both the project are written with under C++17 standards so cross-platform should work fine.
Following the instruction on Microsoft website, I had successfully built a test project on my remote Linux server.
However, all the tutorials seem to ask people to start up a new "Linux Project", in which I did for the test project. The question is, since I already have a project/solution created and the build target is Windows platform, is there a way to switch the build to Linux Remote Build?
I've tried opening project settings, but the "target build" option is always Windows 10 and is not changeable.
I downloaded Android Studio 3.1 and created a project. I did nothing in it and ran the project. Do I need to install any image?
Initial Screen - API version
Below screen comes when i click on run
I had Android version 2.2.2. I uninstalled it and installed version 3. After this, I was unable to download image for emulator.
I finally had to format the drive to get everything done again in first time.
you need to set your console to developer mode (i'm windows 10 user)
if you windows 10 user go to setting - update&security - for developers -
choose developer mode at use developer features
You need an emulator if you do not want to run your app directly in an physical android device. However, check if your PC supports or have libraries to run an emulator
NO, just check your PC config to run an emulator. Or you can download an emulator to run your app on Pc.There are many emulators with fewer config requirements.
You need the image to use simulator, besides, you may also need to change BIOS setting to enable virtualization if you are using Windows OS
I am using Visual Studio 2012 and Xamarin.Android Beta release to develop an Android application. When I try to deploy the android application for debugging purposes onto an Android device, it deploys the previously built application on the device and not the recent changes I made and deployed (i.e No refresh of build). However, if I use Xamarin Studio to do the same, it deploys the correct build everytime (i.e refreshes the build with new code changes).
Any idea why this is happening?
Thanks in advance!
I had a similar issue: With Visual Studio 2019 the debug version of my driver was deployed while building the release version.
The cause of my problem was, that in the Properties -> Driver Install -> Package Files I had an absolute path pointing to the debug version of my driver in the column File. This setting is valid for all configurations (not separated for debug/release), and when entering macros, they are immediately expanded to absolute paths.
I fixed this by editing the .vcxproj file with my favourite editor and changed the path back to $(TargetPath).
I had the same problem. My solution was to add "deploy" to the build configuration:
BUILD => Configuration Manager... => (select "Debug" from left-hand combo-box) => (tick "Deploy" in grid)
Courtesy of this xamarin forum post.
I have no idea why it does this, I had this issue before. I also noticed that the device log was somewhat behind (ie, at 3.30pm, the last record on the device log was 11.00am).
Uninstalling the app from the device and re-deploying it seems to correct it.
Note: I had this issue in VS, didn't check with XS.
I would look at the difference in your deployment settings in VS and XS (I think it may have something to do with the Fast Deployment option).
Similar question (though for iOS Simulator) here.
I had a similar problem (though on an Android emulator).
What didn't work for me:
restarting the computer
restarting Visual Studio
deleting bin / obj folders
going into Configuration Manager (Debug / Release / Configuration Manager) and ticking everything there - everything was ticked
changing the version of the app in the manifest
What worked for me?
Uninstalling the app from the emulator and then running Debug again.
It was an Android emulator, so I uninstalled by clicking on the app icon and holidng for long, and then dragging it to "Uninstall App". On an iOS simulator it should be similar.
I am developing a networked Windows Store app.
Is it possible to remotely and locally debug a Windows Store app using the same instance of Visual Studio?
I have successfully set up remote debugging using a VM on my local machine.
I have a few alternatives, but I just want to know if this is currently possible. One of them is running them on multiple instances of VS. Another is installing VS on the remote machine and debug it locally as normal. (which I don't want to do as much as possible because it's really a waste of disk space)
This is how you can do this:
Build your Windows Store App in Visual Studio.
Select Local Machine on debugger toolbar. Right click on your Windows Store App Project in Solution Explorer -> Click Deploy. This will deploy latest App on Local Machine.
Select Remote Machine on debugger toolbar. Right click on your Windows Store App Project in Solution Explorer -> Click Deploy. This will deploy latest App on Remote Machine.
In Visual Studio click on Debug menu -> Debug Installed App Package. Choose Local
Machine (by default) -> find your application and click Debug.
Launch Remote Debugger on Remote Machine.
The same step as 4 above, but for Remote machine. In Visual Studio click on Debug menu -> Debug Installed App Package. Choose Remote Machine -> find your application and click Debug.
One issue you can meet:
I tried this approach with different architectures of Remote (ARM) And Local (x64) machine. My guess that each time you do Deploy - Visual Studio can rebuild your application. So in case if you will use the same architecture for Remote and Local - only for one of them you can load symbols (just try it). If you will meet this situation - you can workaround it with two ways:
Use x64 for Local Machine and x86 for remote (or vice versa). So each build / deploy will be independent.
Make a Windows Store Package for Testing. Deploy it manually on both machine and start from 4.