I have set up my IDE to show JS Intellisense based on references set in _references.js (http://blog.craigtp.co.uk/post/Javascript-jQuery-Intellisense-in-Visual-Studio-2012.aspx). In doing so, you have to set JavaScript IntelliSense Reference Group to "Implicit (Web)", which I've done. For some time, it works beautifully.
However, after some seemingly random amount of time (could be hours or days, but not usually more than a day or so), my JS IntelliSense stops working. When I go back to the Reference Group settings, I find that the Reference Group has reverted back to "Implicit (Windows)".
Does anyone else have that problem? What might be causing that, or is this a bug in VS2012 (this is the released version)?
Thanks!
Not sure why it changes on you but I found that this trick still works when set to Windows if you manually add the reference to ~/scripts/references.js
Related
PROBLEM
The Android Studio IDE (macOSX) has issues with Syntax/Intellisense. I'm running Flutter/Dart on it to code and compile a Flutter app. I have the latest install to date and I have the latest flutter/dart sdks as of date.
If I create a new file and start working in it, something causes the syntax highlighting and intellisense to break. This appears to happen within minutes of opening up Android Studio. I have to close it and reopen it for it to resume. When it breaks, other files seem to keep their syntax highlighting, but it no longer updates if I work in them. It keeps old errors on the page regardless of the code I change. Is there a fix for this?
EDIT
I found the problem has to do with type definitions, particularly when defining a Future type for a class method.
REPRODUCE
Open up your flutter project (doesn't matter what it is).
Go to your services code (or code that works with Future).
Create a new method with a future return type with a generic specified. Do this by hand, just start typing it in, do not copy paste: Future<List<asdfasdf>>.
After writing Future<List< it should break. It should do it every time for you like it is for me.
If I'm not working with Future, it doesn't break. The way I'm getting around it is defining the method with the future before defining the generics. So I first write Future myMethod() async { } make sure the syntax is correct and there's no errors, then I go in and define the generic.
I feel like I'm going crazy, but since updating to the new version of Android Studio, I can no longer tell which files have errors in them.
Previously, if I made a change in one class, like to a method signature, then all other classes that were calling that method would suddenly be highlighted in red (at that section along the top that shows the path). Now it shows nothing as though my code is good, except when I go to compile, I now get a load of errors in the build tab at the bottom, in a really unhelpful way to navigate through.
Is this something I can switch back to through a setting somewhere? I'm really not sure what to search for, but I've been through almost all of them.
UPDATE :
Following another SO post, I turned on and off PowerSave mode, at the bottom of File menu (in Android Studio). This, temporarily at least, seems to have solved things.
This may be what you are looking for?
Either that or it may be in preferences.
Is it possible to get the VS 2012 find dialog to always use Current Document and reset case & whole-word when I press Ctrl+F? Currently it remembers my last options and I often forget to turn them off.
Also it sometimes switches to All open documents on its own which totally throws me off. I haven't yet figured out why or when this happens.
I've searched for registry keys and extensions but so far nothing useful has turned up.
It's not possible to get the dialog or the quick find UI to always choose a specific scope out of the box. During beta of VS 2012, this behavior was implemented where CTRL+F would always set the scope to Current Document and Ctrl+Shift+F would set the scope Entire Solution upon invocation of the commands. A lot of users were unhappy with this behavior, so it was reverted. There are no registry keys that you can set to alter this behavior.
Visual Studio always tries to reuse the last used scope. There are circumstances at which that scope is not available, and that'll cause the IDE to change the scope on you. Let's suppose you do a search in "Current Project", after that you close the entire solution and then invoke the dialog. The scope will have to change to something else.
You probably know about this, but Ctrl+F3 will search for the word that is under the caret and it'll always perform that search with the Whole Word option on in the current document. Perhaps that'll suit your needs.
I've published a Visual Studio "SmartFind" extension to fix this issue.
http://visualstudiogallery.msdn.microsoft.com/015611c4-b357-4672-8977-f3ec92f0b808
I have recently installed the RTM version of VS 2012, and when I run the debugger the watch window gives me what appears to be a decompiled vision of the local values. My initial thought was that I accidently hit the "Hexadecimal" display, but that is not the case. When I try to look at sub-properties off a given object, I get nothing, not even a representation if the object is null.
I won't know exactly what I may have set that is causing this, but VS 2010 did not do this, and the first day with VS2012RTM also didn't do this. I'm reasonably certain this is a setting I clicked, but for the life of me I can't figure out what it is.
Here are a couple screen shots of what the watch window looks like, and my debugging settings. As an aside, I have tried resetting my settings to factory, and turning IntelliTrace on and off.
Has anyone used JustCode from Telerik lately? This question has been asked about two years ago, but I'm sure the issues must have been resolved by now. Especially referring to running it side by side with ReSharper.
I have been using Resharper for a while now. I decided to try JustCode to see how it behave.
After a week of using JustCode, I am uninstalling it and returning to Resharper.
What I like about JustCode:
A single window indicating all warnings/errors in entire solution.
Performance seemed to be a bit better than Resharper.
Refactoring is easier to get to.
Projects can be excluded, or type of file
Language can be excluded (such as XAML)
What I did not like about JustCode:
Sometimes the underline used to open the option for fixing or refactoring is frustratingly hard to click since VS also puts an underline at the same spot (and it is the context menu of the latter that pops up).
Cannot change an hint to be a warning instead.
Saw some minor bugs
JustCode was giving hundreds of false positive warnings in the XAML code (luckily I could turn the inspection of XAML off)
What I was missing from Resharper:
Warnings about method parameter missing/mismatch from the documentation
Hints to transform an expression into a Linq expression.
When writing an opening bracket, resharper automatically adds the closing one and puts you on an empty line in between the two.
When completing a method, Resharper adds the first parentheses. It also adds the last one if that method is parameterless.
I am sure there is a bunch of other stuff that I can't remember now
You can install both Resharper and JustCode alongside. I first suspended Resharper before installing JustCode and used JustCode fine. When I resumed Resharper and restarted VS, both were running together without error.
Together, Resharper was finding more than JustCode.
For example, JustCode did not give a warning for the following: "Value assigned is not used in any execution path."
It even missed an error: "Cannot convert type 'int' to 'bool'." The expression was:
if ((bool)CanDoIt) // Here CanDoIt is a property of type int.
{
...
}
All in all, the tool is not bad. I recommend it over not having any. But if you have the choice between Resharper and JustCode, go with Resharper... for the moment; JustCode is still young.
You can change the size of JustCode's smart tag or turn off Visual Studio's smart tag in JustCode's options menu. I prefer to access VS's smart tag by using ctrl+., so it hasn't been an issue for me.