I output a lot of information by way of Debug.WriteLine() when programming in Xamarin.iOS. But with the latest version of Xamarin Studio (4.0.10 (build 7)) there is now a ton of whitespace and duplicate output text when I use Debug.WriteLine().
Is there a way that I can suppress all this extra output, or at least have a little more control over it? Using Console.WriteLine() solves the problem, but I would prefer to use Debug.WriteLine() so that it is removed from the release build.
Might be a little late, but I had already logged a bug for this - still unresolved.
https://bugzilla.xamarin.com/show_bug.cgi?id=13538
Related
I do not remember the exact version, but about from 3.2, the lint processing of Android studio has become dreadful.
ctrl + b won't work for about 5min after putting the code, and red lines which are supposed to indicate unwritten methods or wrong referencing is completely broken.
I never had such issue on the previous versions, and I don't know what to do with this. I looked through stackoverflow with the tag android-studio, but no one seems to have the same issue, or I'm selecting the wrong keyword for this.
But, all three of my colleagues are having the same issue from a certain version of Android studio.
Is this an issue with vmOption? Please help.
I was just about to update Android Studio to the version 3.1, but this warning made me to stop and think a little bit:
I tried to search for it and even read here and there again without finding nothing specifically related to the Markdown support.
I'd just like to know more about the consequences of ignoring this warning before updating and, if possible, to have more info about the Markdown support.
I thank you in advance for the attention!
It seems it's nothing much, just an usual warning indeed.
Just after I did a test update, the following report popped up:
Then it allowed me to briefly update the Markdown support to the version 2017.1.20170419 - 173.4301.21.
I want to watch android sources code, but Android Studio has so many errors in base Android code. How do I fix these?
Since no one has jumped in here to help with this...
The longer answer here is that the imports (in red) are failing because Android Studio can't find them. So all the calls made to those libraries are failing. So ALL your code after that is full of errors.
For instance, the android.annotation.ColorInt seems to be broken. A quick Google search provides THIS: https://developer.android.com/reference/android/support/annotation/ColorInt.html
Which tells me that the reason that dependency is broken is because whatever you have there is deprecated and should now use a new reference.
Continue with this sort of research and your problem is solved.
The NDK r11 that was just released.
release notes state: Removed ndk-gdb in favor of ndk-gdb.py
However there doesn't appear to be any gdb tools anywhere in the r11 NDK package. What am I missing. Is this now a separate tool that has to be tied in some how? Was it a gross oversight by the NDK gods? I peaked at my old ndk r10e and there is indeed both ndk-gdb and ndk-gdb.py so I know the python script at least existed there. Are these items I can port over from my R10e version. I know the ndk-gdb script was always breaking on me with some periodic tweaks needed. I've never used the python script so I guess really my question is two fold.
Where do I get/install/configure ndk-gdb.py and how do I use it. Is it vastly different than the old ndk-gdb shell script.
Any insight or help is greatly appreciated.
Update to the latest NDK r11b release, a bug related to ndk-gdb.py was fixed in that version: https://github.com/android-ndk/ndk/issues/3
I'm not totally sure about ndk-gdb vs ndk-gdb.py, but if you look in <NDK>/prebuilt/darwin-x86_64/bin (or replace darwin-x86_64 with your platform's name), you'll find ndk-gdb and some other tools (ndk-depends and ndk-stack). I haven't tried using them myself though, so I don't know if their behaviour has changed compared to r10e.
I often see that some of the ReSharper functionality just doesn't work until you restart VS and reopen the project. But this situation I have now is consistent across restarts. So I am using a Go To Everything fuctionality often. It is enabled in ReSharper settings.
But since yesterday Go To Everything (Ctrl + N for me) can't find most of the files in the project (though it can find some).
Here is a screenshot of the problem:
I have that file open in editor just to prove that it's there. I show it found in an open solution in file tree. But ReSharper doesn't seem to be able to find it.
What to I do to troubleshoot. Thanks you in advance.
The best thing to do here is to raise an issue with JetBrains. Either log a bug with the issue tracker, or email resharper-support#jetbrains.com. Include details about what version of ReSharper you're using, what type of projects you're using, version of Visual Studio, etc.
However, from that screenshot, it looks like ReSharper isn't configured to analyse that file - there's no "green tick" in the scrollbar. Is ReSharper disabled? Is that file excluded from analysis? (Mind you, even when it's excluded, it should still show up in go to results. Something odd is happening here, support should be able to help better than StackOverflow)