To be precise it pops up the autocomplete box when I press <ctrl-space>. However after approximately 500ms the popup disappears. This happens all the time without fail. When I switch to a C# for VB.Net project the intellisense popup has no problems.
Any ideas?
I've found a fix in case anybody else has this problem.
In your F# solution add a single C# class library. It doesn't matter what it is called. I call mine IntellisenseFix. Ignore the project and continue editing your F# project but now intellisense works correctly.
If you delete your C# class library from the project then intellisense stops working.
It doesn't have to make sense it just has to work :)
Related
Does anyone know how to turn off this annoying popup in Visual Studio Community 2019?
All the answers I see for it are for Visual Studio Code when I google it, which says to change it under the "File" > "Preferences" menu. Visual Studio 2019 doesn't have that menu. I just want to code without visual obstructions from my editor. Driving me nuts. Thank you!
The language is VB in ASP Classic environment.
I have turned off everything I could find that seems like it could be related to a popup under the "Options" menu, but many of the descriptions there are obscure. You could seriously make a full time job out of learning what all this stuff means.
I found an answer, however odd it may be. With #JackArbiter's help in narrowing down the possibilities, it turned out to be the file type within the environment that was the issue. I didn't realize at first that it was only a certain file extension that was creating the issue. The *.asp files behaved appropriately, but the *.inc files were the problem.
I went to "Options" > "Text Editor" > "File Extension" and added the "inc" file extension there with the editor set to Visual Basic. These files now behave the same as the asp files.
Go to Tools>Options>Text Editor>[Your markup or language] and you can adjust the intellisense settings. In your case there will be no intellisense settings listed (general HTML is what I assume to be the issue here, though you'll have to do this again probably for the language of the IF/Else code blocks) so go to HTML>General and uncheck "Auto list members" at the top.
in visual studio 2013,when i create a viwe for a particular function=>when ever i change anything in view it gives a error in every line.although it is correct.
but it is correct means every lines of code is write.every time i need to build the solution to solve the error.its really occurred.
i tried to =>
[Instead of it, try to just delete the contents of this directory with Visual Studio closed then reopen it: %LocalAppData%\Microsoft\VisualStudio\14.0\ComponentModelCache]=>found on Razor intellisense not working in VS 2015
but not working for me.
CodeInsight / Auto-Completion in C++ Builder 10.1 Berlin doesn't work for include files. Is it supposed to work for includes? If so, what am I doing wrong?
I have CodeInsight activated in the options, but it shows me no list, even if I manually press CTRL+SPACE.
In the past, I've programmed with Visual Studio, where auto-completion works for includes. I really miss that feature.
Can someone help me with this?
I am upgrading from Delphi 7 to Delphi 2009.
In an existing app, the code completion does nothing at all. If I start a new project, it works fine.
Any idea what is going on?
Finally found the solution to this one, took awhile.
Added "WinTypes=Windows;WinProcs=Windows;DbiTypes=BDE;DbiProcs=BDE;DbiErrs=BDE" to:
Project Options -> Delphi Compiler -> Unit aliases
There is a whole big reason why, but to tired to explain it.
I can't seem to add a reference to a DLL file in F#. It might be a bug with Visual Studio.
I attempted to add a reference to my F# project by clicking on "Add Reference" -> "browse". I found my DLL, and when I attempted to add it, nothing happened. The window didn't even close to confirm my selection. Help please.
Are you adding a reference to a managed DLL?
Anyways, if you can, make a small repro and send it to fsbugs AT microsoft dot com.
Edit: Here's the list of known issues with the F# Sept CTP.
I think there are some known issues when the DLL is produced by Managed C++, however I don't know the details. In any case, sending a bug report to the F# team as Michael suggests is the best thing to do.
Adding a reference to the F# project never works for me, i need to debug the project, then i reference the resultant dll found in the debug folders. This usually does the trick for me.
When I reference the project it always tells me that there is no dll.