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.
Related
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.
Iam using Visual Studio Code for developing NodeJS apps. Is there a way to make changes while the app is running (debugging) and see them without restarting the app ?
I've requested for this feature and need more votes to get it accepted as valid request. You can vote too and wait with finger crossed.
https://visualstudio.uservoice.com/forums/293070-visual-studio-code/suggestions/10336395-edit-and-continue-node-js
Using VS 2013 with "Node.js-Tools for Visual Studio", changes in functions are applied in realtime.
Furthermore this even works with remote-debugging from within Visual Studio. (Debugging->Attach to process->Node.js remote debugging)
Edit: Sorry, wasn't aware Visual Studio Code was a separate thing.
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 having real trouble when I try to use the IOS emulator from the visual studio. So I created a hello world app in VS using xamarin (latest stable version), I set the project as main project, and When I refresh the connexion with the mac, I can't select the device that should be shown in the selectList. The message is "No device attached" :
And if I try to use xamarin studio on the host mac, all is okay, the sample app builds on the iphone emulator:
Thanks to help me !
I know this question has already been answered, but i found it when i had a problem, and it did not help... but i did find the solution:
Under the debugging menu in VS2012, click on Configuration Manager
make sure that iPhone Simulator (or iPad, if you want) is set...
Default seems to be looking for a physical device...
hope this helps.
Are you sure the device is connected to the Mac and not the Windows machine? Have you tried debugging from that same device from Xamarin Studio on the Mac?
Had the same problem. Issue was when i loaded my solution, visual studio 2012 decided to choose a library project as the 'Startup project'.
Rt Clicked the ios project, chose 'Set as StartUp Project' and the device list was populated.
P.S: Visual Studio you should be old enough to figure this out by now.
When I ran into this problem, I had another instance of visual studio running which was connected to the Mac.
Apparently you can only have on VS instance connected at a time.
Check your server log in Visual Studio output window for some more clues:
Closing the other instance of Visual Studio allowed me to connect in the instance I wanted to debug in
I discovered something missing. For me, in Visual Studio 2013, for some reason they have removed Solution Platforms from the toolbar. This makes it impossible to switch from iPhone to iPhoneSimulator without opening Configuration Manager. So, to fix this.
Click TOOLS/Customize then select the 'Commands' tab then select the 'Toolbar:' radio button and click the dropdown to the right of it and select 'Standard' as the toolbar you're working on.
Now, click 'Add Command' and select 'Build' from the catagories on the left and then scroll down commands until you find 'Solution Platforms'. Select that one and click OK. Then click the 'Close' button. You will now see an additional dropdown next to the Solution Configurations dropdown on your Standard Toolbar.
This will allow you to easily switch from iPhoneSimulator and iPhone. Use iPhone when you want to plug in an actual device, and use iPhoneSimulator when you want to pick a simulated device.
Hope this helps somebody out. I too have spent lots of time trying to figure this one out when I went from a device and was trying to use the simulator instead.
Restarting of Visual Studio 2010 worked for me.
Different things worked for me (Windows 8.1 & Visual Studio 2013):
Restart Visual Studio
Set 'iPhoneSimulator' as platform (only working one)
In Properties - iOS Application change 'Deployment Target' version to some lower number (6.0 worked for me).
As well as checking you have the right startup project selected as per #Chamkila's answer, check that you haven't accidentally broken your project's Info.plist file by attempting to open it through Visual Studio.
I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.