I am developing a cross platform application using Android(Monodroid), iPhone(MonoTouch), WP7 and Windows and would like to keep my code base as coherent as possible. The iPhone requires a Mac which is fine I can deal with that but Android allows development in Visual Studio which is great as I can manage three projects under the one solution.
Now adding an new android project to a new visual studio solution will allow me to deploy in the emulator just fine. Same goes with a new solution and new WP7 project and corresponding emulator.
The issue I have is that if I setup a new solution with a WP7 project first and then add an new android project to the solution I cannot launch the android project as it always defaults to the WP7 emulator even when I set the android project to active project.
From what I can gather I think VS2010 will allow an emulator for the solution but will not allow an emulator per project within the solution. Has anyone come across this? Is there a work around maybe via command line? One workaround would be to have two visual studios open at the same time but I am trying to avoid that if possible.
Source of the problem has been identified and solved
Within the same solution don't give different project type executables the same name as this causes Visual studio a problem when determining which emulator to select. I changed the names for my launching apps for each project within the solution and everything works fine.
Original:
Solution \ Android \ MyProject
Solution \ WinPhone \ MyProject
Fixed:
Solution \ Android \ MyProject1
Solution \ WinPhone \ MyProject2
This might be controlled via the "Deploy" setting. Try disabling Deploy for the WP7 project in your solution configuration manager.
Related
What I have done
I looked up a few tutorials and did all their steps. MRTK is successfully installed. I created a simple world in Unity 3D (latest version), with 2 moveable (using the hand interface) objects. In game mode, everything works fine.
Now I wanted to deploy it to my Hololens 2.
So I build the project with the following settings:
After that I connected my Hololense to the PC and want to deploy it via Visual Studio 2022.
It is set to "Release" "ARM 64" "Device".
After pressing on "start without debugging" i will get the following error Codes (as an image because it is better structured):
I already tried installing different SDK packages and creating 5 new Unity projects but it doesnt work. Hope you can help me!
Greetings!
Apart from the suggestions from derHugo, you may also check the following configurations of your project.
Make sure Unity is 2020.3 LTS, and you have used Mixed Reality Feature tools to import/update to the latest package.
Select a specific “Target SDK Version” and “Visual Studio Version” instead of “Latest installed”
In visual studio, make sure the Platform Toolset consists with Unity selection (v143 for vs 2022)
Reinstall “Universal Windows Platform development” component in VS installer and ensure any related to v143 ARM64 build tools are installed (because you are using vs 2022)
LNK1136 error is caused by corrupt or invalid files. Because to deploy a unity project to HoloLens, you need to build a Unity project first. If cleaning VS build then rebuilding is not working, try to remove Unity build then rebuild.
VS installer Screenshot added:
I'm new to creating Mobile Android apps using Visual Studio and I've started creating a new Xamarin Forms project. I didn't add any code. I just created it and testing out how it works. When I tried to deploy, it will show an error, "There were deployment errors. Continue?"
Deployment Error
I even went to the Android Device Manager to create an Android Emulator and it also provided me this error.
Android Emulator
I tried every solution that I could find online. Some told me to rebuild, clean and build my solution. That didn't work. I researched to check mark Hyper-V in the Windows features and even rebooting my computer several times and that didn't work. When I tried to deploy, this shows up in the output log. Not sure if this will help.
Output Log
I also attached images of what I've done so far and I really don't know what else to do.
Android SDK Platform and Tools 1
Android SDK Platform and Tools 2
Windows Features 1
Windows Features 2
I developed an application in Xamarin.IOS on a windows machine, but the build time is getting ridiculous. So I decided to try to load and develop the solution on my Mac using VS. I have updated everything on my Mac (such as: Mac OSX, visual studio, and Xcode). I load the solution and everything builds, but no simulators show up in the target devices for debug mode. If I switch to release, the simulators show up, but not in debug. All provisioning files are downloaded and I have it set to Developer Automatic and Automatic.
Debug and Release are the only two build options. Debug|IPhoneSimulator is not one of them.
I also managed to get in this screwed up state with a new iOS project in VS4M. I tried changing various config settings to get it working, to no avail.
I added a new single-page iOS project to the same solution to see if the problem would persist. This fixed the problem in the new product and the existing project. I then deleted the extra project and called it good.
A stupid solution, to a stupid problem.
You will have to choose Build Configuration Debug|iPhoneSimulator, check the configurations and the target platform
Ended up creating a new project and edited the sln file to mimic what the defaults were for a new project then it started working.
I am trying out the new Visual Studio App Center for a mobile app I am writing.
I have three solutions checked into VSTS Git. The first solution named App.sln is a master solution that has 2 solution folders, Apps and Services. The Apps folder has 3 projects App.csproj which is a .NET Standard 2.0 library containing the Xamarin Forms shared code. App.iOS.csproj is the Xamarin Forms iOS project. Finally, App.Droid.csproj is the Xamarin Forms Android project. The Services folder contains project files written in ASP.NET Core 2. The second solution is a solution named App.iOS.sln containing just the iOS and App library projects. The last is a solution named App.Droid.sln containing just the Android and App library projects.
In App Center I have 2 Apps configured per the instructions for Xamarin Forms apps. The first is an App configured as iOS Xamarin app. The second App is configured as Android Xamarin app.
I configured the analytics and crash reporting which works. I then configured the builds and this is where I have run into an issue. Specifically the Android build configuration project drop down only sees the App.Droid project. The iOS App build configuration project drop down sees all three solutions but only the App.iOS project. I selected the App.Droid and App.iOS projects. It seems to work. However I'm concerned that in the future things might break. I rather select the App.iOS and App.Droid solutions. That way I know that the correct projects are compiled and nothing not need is compiled. This is especially true since I am trying to stay within the free compile time budget until the MVP is done. Any ideas how to accomplish ensuring only the right projects are compiled?
According to App Center team (on Jan 30, 2018):
Unfortunately we do not support the selection of sln's with Android
Xamarin, currently solution file is only supported for iOS.
I am the newbie in Xamarin Cross Platform development. I am using Visual Studio 2015 Preview for development. I created the new solution for mobile app and it is working correct for both Droid and Windows phone. But after successful connection with iOs Build host I got the error when I build the iOs App like -
Xamarin.iOS does not support running or debugging the previous build version of your project.Please ensure your solution builds before running or debugging it.
And also when I click on View iOS Simulator I got build host error.
Error: Build version problem. it will show the build version problem.
Please tell me the solution for this.
Most common cause of those symptoms
The most likely cause of this issue is the following known bug:
https://bugzilla.xamarin.com/show_bug.cgi?id=25811
Explanation
The problem in that bug is that the Xamarin.Forms template is using a bad default setting for the iOS project in Visual Studio's configuration manager.
The configuration manager works by telling Visual Studio which projects you want to be built and/or deployed at the same time in the configuration you're using at the time.
So for example; when you build your Android project in Forms, the configuration manager makes sure that the shared project is included; otherwise it wouldn't work, or you'd have to build it separately or etc. etc. (i.e. a real pain.)
Normally, Visual Studio doesn't have a way to automatically "know" which project(s) you want to include in all your configurations; you'd have to tell it to include (some library) with (some app); etc. manually.
How to fix it
Screencast: http://www.screencast.com/t/zLoQOpEn
Go to "Build -> Configuration Manager"
Select the configuration(s) you wish to adjust, (e.g. Debug | iPhoneSimulator, Release | iPhone)
Make sure your shared library project(s) are included with the platform-specific configurations. (You can ignore the greyed-out 'Deploy' checkboxes, those are handled automatically)
Why this is a bug
So this isn't a bug in that the configuration manager isn't working correctly for iOS projects, but that the Forms template is using a bad default setting for the iOS projects when you create a new app. It should "know" to include the shared project in the iOS configurations by default.