When I create a new Xamarin.Forms project (PCL), Visual Studio becomes unresponsive, only accepting clicks and key presses every few seconds with large pauses in between. No other project types that I've tried have this issue. Have you encountered this problem or have a workaround?
*Update: Deleting the iOS project from File Explorer seems to have fixed the issue but this means I can't target iOS. Also, native iOS projects freeze as well. Could this be an iOS thing?
Since installing the recent Visual Studio 2017 updates, the problem seems to have been resolved.
Related
I'm about to publish my first APP on IOS.
I stopped because visual studio 2017 (windows10) does not find the provisioning list (see image) in IOS Bundle Signing.
what could be the problem?
thanks
ok, I solved.
Usual refresh problems. Close and reopen Visual Studio, reconnect the MAC etc.
Older versions of Android Studio had a Refresh option in the layout preview in the IDE, but in v2.2 it has vanished. I am finding repeatedly that I update drawable bitmaps in the project with updated files, that new version is not reflected automatically, and I do not see the preview. Problems like this are so common with Android Studio, it's such an utterly infuriating IDE and so flaky, despite the speed it is advancing.
Where did the refresh option go? I can't believe I'm having to actually ask this, but maybe I missed it somewhere obvious!
My current Android Studio installation (linux-64bit) is showing a pop-up saying there is a new Version of Android Studio 2.
I am unable to download the current stable of Android Studio.
The download-link (on big green button) reffers to the Terms and Conditions. If i Accept and klick the button (which is showing no text, which is also strange) it redirects me to the index page again.
Here is the index page: http://developer.android.com/sdk/index.html
Have they withdrawn the release or something? Does anybody know a direct-link?
Thank you for any help on it
You need to have a little patience and try to check for update from time to time until you'll be able to update Android Studio from within the IDE. I encountered the same issues as you but after a while it worked well.
My advise is to wait with the upgrading to 2.0 and stick with your 1.5 version because a lot of people here have problems with Android Studio 2.0 (for now it is kind of buggy, maybe later Google will fixed some issues...).
As an example of my problems with Android Studio 2.0 I've posted recently, check this: After upgrading to Android Studio 2.0, I cannot change the screen orientation in the Android emulator, but of course it is your decision to upgrade or not :) .
P.S. I'm a linux user too.
As this is entirely a new version, you will not be able to update (or upgrade) from within the app.
You will have to download the installer and install at the same location replacing your Android studio 1.5
I did the same thing and is working for me.
Regards
Vivek
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'm running Visual Studio Express 2012 on Windows 7. I've been running it with no problems for several months now.
Last Friday, when I shut down my PC, a lot of Windows updates were installed. This morning, when I started up and opened a VS2012 solution, I got this error message:
This program has known compatibility issues
...
Visual Studio 2012 Express for Windows Desktop is incompatible with this version of Windows.
There's a button for Run Program, and when I click it, the solution opens normally. I haven't changed anything about my Windows configuration. This happens every time I open a solution. Did MS release a flawed patch in the batch of updates that got applied last Friday?
EDIT: I'm not sure why people are voting to close this question. The answer that's been linked to isn't related to my issue; that answer seems to pertain to trying to open a VS2012 project in VS2010. I'm trying to open a VS2012 project in VS2012. If you really think that the question needs to be closed, please let me know why in the comments, so that I can change it appropriately.
The .NET updates installed on Friday were:
KB2805226
KB2805221
KB2804582
UPDATE: I gave up, more or less, and clicked the "Don't show this window again" checkbox on the error window. Visual Studio seems to be running ok.
I received the same message on Visual Studio 2012 Premium (on PC where Windows 7 re-installed in last month) - the suggested fix was "Update for Microsoft Visual Studio 2012 (KB2781514)" which seems to have fixed it
www.microsoft.com/en-us/download/details.aspx?id=36020
Install Visual Studio 2012 Update 2 solved my problem. No previous update needed for this one. Here's the descriptions of the update.
(I'm using Windows 8, installed all important updates for Windows, then tried repair Visual Studio in Programs and Features, problem still here until installed Update 2.)
I've been running VS2012 for about 2 weeks now since I clicked the "Don't show this window again" button. I haven't encountered any problems. For now I'm going to consider this an adequate solution.
I've just installed VS2012 at home and came across the same problem. The 1st solution I found is that webdeploy doesn't work after Oct 2013 and I should install Web deploy V3.0.
Done that, no joy. I let Win7 search for compatibility solution on-line and it found an update patch (KB2781514) which did work.
This is the same solution as mentioned before by #John M.
Should've looked here first, just posting this again if someone comes across this again these days..
Thanks to all other users who helped with this thread.
I had a similar problem with VS2012 awhile ago it was along the lines of:
"this solution has no errors and could potentially be damaged"
*yet still opened fine.
as far as fixing it went I performed a clean install of VS2012 and the error has not bugged me since in saying that I am probably out of date at this time and may find if I updated I would have the same issue.
Food for thought.
Even i had the same problem on Windows 7 with Visual studio 2012.
Installed Update for Microsoft Visual Studio 2012 -KB2781514 and it fixed the issue.
Note: "Just clicking on Run program was also opening up the solution file without any issues in my case."