I am running Visual Studio 2013 Update 4 with Tools for Apache Cordova CTP3 installed. After creating a brand new Apache Cordova project, and then debugging it, it breaks/pauses/stops on seemingly random lines of javascript files where there are no breakpoints. Meaning, it stops on lines as if there was a breakpoint there, but there really isn't. I'm using RIPPLE debugging only. I don't use a device or emulator AT ALL.
At one point, I had installed Visual Studio 2015 CTP5, and an associated update to the Android Emulator that was recommended. I since have uninstalled them.
This is a bug that appeared since a recent update to Chrome, and it is being worked on. You can run your app on Ripple by hitting F5 through the debugger breaks (hardly satisfactory), or Ctrl+F5 to start your app without debugging in Ripple. To debug, the better option is to run on on an emulator. The VS Emulator for Android on VS 2015 Preview has been working well for me. In VS 2013, GenyMotion is probably the best option for Android.
I have having the same problem as discussed here but noone seems able to help
https://social.msdn.microsoft.com/Forums/vstudio/en-US/10b9a01c-4afa-443e-83d5-fa4cd92493c0/visual-studio-cordova-templateangularjstodo-example-project-debug-issue?forum=vsdebug&prof=required
I fixed it by doing: Tools > Options > Tools for Apache Cordova > Cordova Tools.
Then click on the button 'Clear Cordova Cache'. Give it a few minutes..
Another thing I noticed, is that I might have had CTP3.0 vs CTP3.1. Be sure to take a real close look at https://support.microsoft.com/en-us/kb/3014133?wa=wsignin1.0
Related
When I run the application with Visual Studio and ripple, and I click link for other pages from Cordova project( to localhost) comes an error. Ripple notificates: "Instead of the page you'll see an AW, snap!" Chromes DeveloperTools tells: "was disconnected from the page.'
Links for some website works good. Before links worked well.
What could be the problem?
We found what appears to be a bug in Chromium and filed this to track it:
https://code.google.com/p/chromium/issues/detail?id=585260
We are making a change to Ripple to work around the issue. Please keep an eye on our VS TACO blog for more information; we'll make an announcement when the change goes live with instructions on how to update Ripple. You can find our blog here:
http://microsoft.github.io/vstacoblog/
We're sorry for any inconvenience this has caused you and hope to have a fix, both in our tools and in Chrome, shortly.
(Disclosure: I work on the Tools for Apache Cordova in Visual Studio)
I followed instructions from http://microsoft.github.io/vstacoblog/2016/02/12/update-to-ripple.html
and it's working :
-In Visual Studio, click Tools -> Options
-Find the Tools for Apache Cordova
-Click the “Clear Cordova Cache” button
-Rebuild your project
Please make sure that you have VS2015 TACO tools update 5. let me know if you have any issues afterwards. It works great for me with the latest update.
Luck did not last a long time. Chrome updated himself(Versio 48.0.2564.103 m) and Ripple does not again working. In new Chromes is bug with Visual Studio 2015 and Ripple.
This is a new issue we're investigating on the VS TACO team, too. I'll update this answer with any workarounds/next steps as we keep researching.
For now, the workaround is as suggested by #PeteQoo - you need to revert your version of Chrome to version 46.
I'm a starter in writing app code in Visual Studio 2013 Community Apache Cordova and have managed to connect VS2013 with my Mac. Once I have gone through the process of building the app in VS and on my Mac and installing in on my iPhone, I open it up and it won't rotate. It doesn't rotate for a number of basic apps that I've written nor does it rotate if I build the default new project "Hello, your application is ready!" app.
I have done some research and tried changing the config.xml "Orientation" preference to "both", through the code window and also in the designer window but that doesn't change anything. I've also noticed that adding in a "BackgroundColor" preference doesn't work either.
Does anyone know if I may have configured something incorrectly or perhaps need to add something to my code?
All the HTML, JS and CSS that I've written seems to work okay (with the exception of trying to link URLs to the Safari Browser but that's another issue).
I have noticed the same issues. I tried finding some settings to fix that in the config.xml, but was not successful. I have resolved myself to just opening the iOS project in XCode and changing a few things:
Device Orientation: no matter the config.xml setting, its always only Portrait. I click-check the other 3 orientations.
Team: I have multiple developer profiles, and I need to choose correct one here.
Bundle Identifier. I screwed up one project, and have different case for iOS and Android. I leave the VS one as the Android one, so I can build completely correct for Android. Since I know I have to go to XCode for iOS anyway, I change the bundle identifier here.
You can find the project using Finder at ~/remote-builds/builds/9999/cordovaApp/platforms/ios/*.xcodeproj, where 9999 is the build number, though not necessarily the latest, largest number, but the latest datetime of the folder.
You can also refer to Greg's answer in this related post as an alternative solution.
I'm working with a ASP.NET 2.0 project that has been upgraded from vs 2005->2010->2013.
In vs 2005 and 2010 I can modify the code while debugging, save the changes, and reload the page with the changes applied.
Now in vs 2013 I can't do this. Can't change the code when I hit a breakpoint. Tried to activate all checkboxs in "Edit & Continue" options, but nothing worked.
It's annoying having to stop debugging and recompile the app to debug again the changes.
How can I solve this?
FINALLY figured it out. Here are my findings.
To Reproduce:
I created 2 vanilla projects:
1) .net 4.0 project with VS2012 (ProjectA)
2) .net 4.5 project with VS2013 (ProjectB).
Then opened ProjectA with VS2013 and I couldn't Edit & Continue (E&C).
Resolution:
In VS2013, go into the project's properties on the "Build" tab and uncheck "Optimize Code".
I still don't know why I could Edit & Continue in VS2012 even with "Optimize Code" checked, but in VS2013, it won't work.
Resources:
Here is the link that aided me in locating the problem:
http://msdn.microsoft.com/query/dev12.query?appId=Dev12IDEF1&l=EN-US&k=k(vs.debug.ENC.SupportedButNotAvaiable);k(TargetFrameworkMoniker-.NETFramework,Version%3Dv4.0);k(DevLang-csharp)&rd=true
Hope this helps!
I know this is a bit old, but I found the answer today - at least one answer. I'm running Visual Studio 2013 Update 1 and in my case, attempting to debug an MVC 5 application. Switch your target platform (in the Build menu) from Any CPU to either x64 for 64-bit or x86 for 32-bit.
I ran into this today while attempting to debug my MVC 5 application. After reading the release notes for Visual Studio 2013, including the fact that they added the ability in, I was puzzled. I checked my properties and saw that Optimize Code was unchecked while Edit & Continue were checked. The only other debugger marked was ASP.NET. On a hunch, I changed from targeting Any CPU to just targeting x64 under the Build menu. After that, I was able to use Edit and Continue as long as I wasn't attempting to edit lambdas or other items!
Find little solution for this case - close all files in solution before run debug.
Only files which were closed when debug is started can be edit.
Of file is opened when debug is start - edit is not possible.
What works for me, is the following:
1) Break point is hit, and I want to change code.
2) Now: Set next statement to somewhere earlier in the current function.
3) Do the change
4) Save / CTRL-s
5) Stepping through the function now includes the change.
I dont know if anyone else has had this problem. I'm using VS2005 working on a C# website.
The problem is on the .aspx page, when I click on the "Design" option two things happen.
It does not switch to design mode. I see only source. But I the problem is that the source mode gets stuck and uneditable.
Second thing is that I cannot switch back to source mode and hence am stuck only in that non-editable mode.
I tried to Reset my settings, but that hasnt helped.
Any ideas?
Try running visual studio in safemode. Launches Visual Studio in safe mode, loading only the default environment and services, and shipped versions of third party packages.
Try the below command in Start-> Run
devenv.exe /safemode
http://msdn.microsoft.com/en-us/library/xee0c8y7(v=vs.80).aspx
I was running my application from Flash Builder 4.5.1 without any issues. (It is a Flex application that connects to .Net Web Services). However, something has changed recently in my configuration or project, because when I try to run the app with the play or debug button, I just get a grey screen. I can't even stop on any breakpoints.
Eventually (maybe 30 seconds), a message pops up like so: 'The Flash Builer failed to connect to the running application. Please make sure that you are running the debug version of Flash Player...'
I definitely have latest version of Flash Debug Player installed (11.1.102.55). I have tried uninstalling it and re-installing it.
I have tried cleaning and rebuilding my project.
I have tried switching to a different workspace and back again.
I have tried restarting the PC.
I am using the latest version of IE for testing.
I'm really stumped - has anybody got any ideas on how to solve this?
Thanks
Have you tried deleting the html-template folder? This has caused issues for me in the past.
After it's deleted, when you try to build you will have a compiler error/warning about the missing folder. Right click and 'rebuild'.
There are some issues with compatability between 64 bit IE9, the 64-bit flash player, and 32-bit debugger. It seems like flash builder gets confused on which to use. I haven't seen any decent resolution yet in the Adobe forums for this particular issue other than use a different browser for testing.
To switch browsers, go to Window > Preferences... > General > Web Browser in Flash Builder. Select Firefox or Chrome.
In order to use Firefox, you need the Flash Debugger for Netscape compatable browsers installed. You can get that from Adobe here.
To use Chrome, you need to replace the built in flash player that is installed with Chrome with the debug player. Instructions from Adobe are here.