I use visual studio 2015 with xamarin android for my project. I build and debug on a Samsung SM-G389F(Android 6.0 - API 23). Everytime I build my project and deploy it to my device it will not override the previously build app. I have to manually delete the existing app in order to see some changes.
Is there a way in visual studio to let the app be successfully deployed?
Is this a bug or are my settings wrong?
thanks.
Sounds like you might have Fast assembly deployment enabled and it's not working correctly. Here's what to do:
Go to project's properties and Android Options tab.
Turn off Use Fast Deployment
Uninstall the app completely from the device.
Rebuild the whole project (rebuild also does cleans the project)
Try to deploy again
Related
I'm using Visual Studio 2017 and .NET Core 2.0 to create a simple console app which I want to run on Windows and macOS.
I'm running VS 2017 version 15.5.4.
I've followed the section: "Self-contained deployment without third-party dependencies" from that page.
I make changes to my .cs files and build and the changes are reflected when I debug and then I published the app and it changed it too.
I've now gone back after restarting my laptop and when I build and publish the console application .exe file has the earlier time-stamp and now runs "Hello World" default console app instead of my code.
I've published both Debugs and Release versions and tried creating different profiles and it either comes out as the Hello World App or my first completed publish, but never my latest version.
Any ideas?
Try Cleaning the solution
If this doesn't work, delete the files included in the .vs folder then try rebuilding the project
I have installed VS 2017, version 15.3.3, breakpoints are working perfectly on web asp mvc projects but not working on xamarin projects, either: PCL, Android or iOS.
(I am on Debug mode) everything is installed in its default setting, I have not changed any project options
If you are debugging with the Android emulator, you might need to tick "migrate to physical computer with a different processor version" under Hyper-V manager -> Image -> Settings -> Processor -> Compatibility. This resolves random app crashes and also allows debugging from visual studio to work.
I've had this issue before, and restarting Xamarin Studio / deleting the app and cleaning/rebuilding/reinstalling worked.
I Solved it,
checked checkboxes was unchecked, now it's working
I have a problem with creating, building and deploying (still on Android) Xamarin/Xamarin.Forms projects on Visual Studio Community 2015
Version v14.0.25431.01 Update 3, Xamarin v4.2.0.680.
I can't build sample opened projects like MvvmCross or XAML examples. What I've done:
Clean and Rebuild
Update Xamarin extension
Update Nuget packages with removing dependenties
Close and reopen VS
Tools -> Clear MEF Component cache
List item
The most common:
IDE0006 Error encountered while loading the project. Some project features, such as full solution analysis for the failed project and projects that depend on it, have been disabled.
Who know how to solve it?
P.S: Solved by reinstalling Xamarin extension, Android SDK (NDK, emulators, etc.)
I had a host of problems with Xamarin under VS2015, e.g. locked files, compiler could not find files etc.. They all disappeared when I transferred my solution from a network drive to a local drive.
I'm starting to program Android app using Visual Studio 2015 (C#). I installed Xamarin, Android SDK and Visual Studio Emulator for Android. Starting deploy and emulator going well, but i can't find my project(application) on Virtual Machine.
When i unlock phone(virtual machine) i can't find my app (menu etc.).
The picture visual studio screen
1>------ Build started: Project: App2, Configuration: Debug Any CPU ------
1> App2 -> C:\Users\Mateusz\Documents\Visual Studio 2015\Projects\Basic\App2\App2\bin\Debug\App2.dll
2>Starting deploy 5" KitKat (4.4) XXHDPI Phone ...
2>Starting emulator 5" KitKat (4.4) XXHDPI Phone ...
2>Validating emulator arguments...
2>Determining if emulator is already running...
2>Preparing virtual machine...
2>Launching emulator...
2>Emulator launched successfully.
I hope with this list you solve your problem, exist many reasons that you are having this problem try this different options.
1) Run the Visual Studio 2015 run as administrator.
2) Open the log and watch the last errors.
3) In this link you can watch the correct installation of the VS Android Emulator Visual Studio Emulator
4) Check you have installed que correct SDK version.
Like #MarcosJoséPérezPérez said, there are many reason this could be happening and looking at logs and your Visual Studio Output window may help.
A few steps you can try, a combination of these almost always works for me but I have not personally tried the Visual Studio Android Emulator yet:
Uninstall the app from the emulator
In the emulator, go to Settings -> App -> look for an entry that is the same name as your Package name (which is listed in your Android project properties under Android Manifest), if you see it, uninstall that also
In Visual Studio open your Configuration Manager (located at the bottom of the Visual Studio Build menu) and make sure that the Build and Deploy boxes are checked for your Android project.
Delete all bin/ and obj/ folders in your Android project directory (also delete them in your shared project directory if you have one).
Open your Android Project Properties, head to Android Options -> Advanced and make sure at least the armeabi-v7a and x86 architectures are checked.
Rebuild project
I have an ASP.NET MVC application that I'm working on in Visual Studio 2013 Premium. I have three projects that are underneath my solution. If I right-click on any of the folders that are immediately under my solution and choose add, the flyout from the context menu displays fine and Visual Studio continues to function normally.
If I right click on any (I've tried a few but not all) folder underneath one particular project in Visual Studio, it freezes for about fifteen minutes. The cpu and memory usage when this is going on seem pretty normal.
If I right click on any of the folders underneath the other two projects and choose Add I get the flyout to appear showing the types of things I can add to the folder and everything works just fine.
What I've tried:
Disabling all Visual Studio Extensions that can be disabled. This didn't fix it.
Starting an instance of Visual Studio in Safe mode, this does fix it.
Any idea what I can try next? I'd hate to have to manually uninstall all of the Visual Studio extensions that can't be disabled, but this seems like the logical next course of action.
As far as Extensions I have:
Application Insights Behaviors SDK (XAML)
Bing Dev. Assistant (Disabled, installed after problem started)
Find in Solution Explorer (Disabled)
Company-created Build Tools (Disabled)
Company-created Core Tools
Company-created Scaffolding Tools (Disabled)
Microsoft Advertising pubCenter
Microsoft Advertising SDK for Win 8.1
Microsoft Advertising SDK for WP 8.1 XAML
Microsoft ASP.NET and Web Tools
Microsoft Visual Studio ASP.NET MVC 5 Scaffolding
Nuget Package Manager
Productivity Power Tools (Disabled)
Release Management for VS 2013
TFS Server Power Tools for VS 2013
TFS Sidekicks (Disabled)
TFS Process Template Editor
TFS Team Collab.
TFS Work Item Type Designer
Unit Test Generator (Disabled)
Visual F#
VS Extensions for Windows Library for JavaScript
WP 8.1 SDK Integration
Workflow Manager Activities
I don't need the WP 8.1 stuff here at work, but dabble with it at home. Since I'm logged into my MSDN account in Visual Studio at both places, would it uninstall it from my home PC if I uninstall it at work?
I'm doing a little further exploration. On the project that has the problem, when I try to do an add to a folder, I'm seeing Nuget.exe get fired off every six seconds over and over again. Where would I look to see where this is set up? I assume in the .csproj file.
Thanks
I disabled and uninstalled a bunch of Visual Studio extensions, which didn't help. I then cleared my nuget cache and that solved my problem.
I had exactly the same problem apparently, in my case it was a reference problem try deleting them one by one until the it starts responding in real time, i suggest starting with 3rd party dlls.