VS Pro F# compiler still works. Correct F# code still runs. BUT hovering over a function or symbol in a VS window presenting F# code no longer causes its type to appear as a tool-tip.
For no reason I can discern my Visual Studio Pro has stopped live-checking my F# code. No idea why the change. I can still compile and of course type errors are still emitted.
Any idea where it is controlled in VS Pro?
Any ideas why F# Intellisense might suddenly NOT
work in VS Pro?
Thank you!
This issue may reappear in the future so I will not mark any answer as final. If you have a fix that works then please state the version of Visual Studio and F# Tools (found in the About Visual Studio pop-up) with your answer
Version:
Visual Studio 17.23
Visual F# Tools 17.1.0-beta.2253.3
As Bent Tranberg noted the F# Github repo has a discussion "F# intellisense sometimes stops working #12982". Looks like a fix will be pushed into the next update of F# (Visual Studio).
But what worked for me was to both:
close and restart Visual Studio
Recompile your project (need not be error-free)
After this my Intellisense tooltips would appear.
I have both Unity 5.3.1f1 and Microsoft Visual Studio 2015 Community edition properly installed and running (I've been using them separately for a while now). However, now that I try to install Visual Studio 2015 Tools for Unity, the installation process crashes giving me the following error:
"Microsoft Visual Studio 2015 Tools for Unity Setup Wizard ended
prematurely because of an error. Your system has not been modified. To
install this program at a later time, run Setup Wizard again. Click
the Finish button to exit the Setup Wizard".
Of course, I already restarted my computer. I even uninstalled Visual Studio and Unity and then installed them again (that is really painful by the way). Nothing changes.
Can anyone help me on? I don't even know how to get support for something on the boundary like the Visual Studio Tools for Unity.
Here is a screen capture of the error:
From unity 5.2 and up i guess you don't need Visual Studio Tools for Unity as Unity from version 5.2 has native support for Visual Studio (same applies on 5.3.1f1).
i use Unity and visual studio with the tools
a link that can be helpful on what i said:
Native support for VSTU 2.1 in Unity 5.2
http://unityvs.com/documentation/native-support/
I have the problem that Visual Studio 2013 crashes when I lock the computer or start another instance of Visual Studio.
I use Visual Studio 2013 with latest patches applied. I always start Visual Studio as Admin.
This seems to only happen with a certain big solution. This problem did not occur to me with other solutions.
I tried to delete the solution and make a clean checkout from TFS, but Visual Studio still crashes.
I know this is not much information, but do you have any idea how to fix this or how to what else I could check?
Additional Information: This still happens even with Visual Studio 2015 on a fresh Windows 8.1 installation...
Here's the error:
Use the following steps to solve the issue:
Source: http://resharper-support.jetbrains.com/entries/24765142-Visual-Studio-with-ReSharper-is-freezing-and-or-crashing
I would copy the solution with quotation but as you can see, there is a lot of text to edit.
Start Visual Studio using the /log switch. Then check the created log file for warnings and errors:
%APPDATA%\Microsoft\VisualStudio\11.0\ActivityLog.xml
If you use a Web Browser to view the file, it will be nicely formatted, due to the accompanying xsl-sheet.
I apologize as this may seem as bit of a general question.
I have developed a couple of VB programs using Visual Studio 2010 Professional and others on Visual Studio 2013 Ultimate. While I have not done any work in about a month with either version of Visual Studio, I thought I would go in and start work on a new project.
After entering some code in Visual Studio 2010 using WinForms, I found I was unable to run the code in the debugger (pressed the start button and F5).
It acted like it would start, then it just stopped and returned back to my code.
I thought I would try it on another program that was completed and working a couple of months ago, but I had the same issue present itself. Attempting to use Visual Studio 2013 had the same effect.
Any ideas from anyone? Has anyone else experienced this same issue recently? Once again, I do apologize for the lack of examples here, but I'm not sure what I can include to show the problem.
IMO, you should try resetting visual studio settings (and a restart may solve the issue)
you can try following
do it via visual studio -> tools -> import export settings
or you can run this command devenv /resetuserdata
or checkout this http://msdn.microsoft.com/en-us/library/ms241273.aspx
I have around 50 projects in Visual Studio 2005 that I am building a new development machine for and I'd like to slowly move those projects to VS 2008 but also have 2010 available for select new projects.
Can this work? Are there any gotchas for this sort of setup? Any general advice for running multiple versions of Visual Studio on the same system would be greatly appreciated. Specifically related to managing a controlled migration of projects to new versions but being able to selectively keep some on old versions.
I've got 7.1, 8, and 9 installed at the same time (well, and VB part of 6 as well) and I've not really had a problem opening projects file in the wrong version. The Visual Studio Solution files is "associated" with a particular version even if they all have the same extension of .sln, as you can see from its little icon. Microsoft Visual Studio Version Selector seems to handle individual project files (.vcproj) fine as well.
The only thing I've had is the individual source code files not opening up in the latest version like I want, but that's easily fixed with the click of a little button in VS Opions.
Microsoft have this to say:
Visual Studio supports the installation of Visual Studio .NET 2002, 2003, ... on the same computer.
In general, you should install the earliest release of Visual Studio first, and then install subsequent versions of Visual Studio in the order in which they were released.
Make sure when you open up the 2005 files you're doing it in 2005. To open them in another would require a conversion which would render them incompatible with the older compiler set-up. To aid this, structure whatever workspace you're using into 2005, 2008, and 2010 so as to minimize accidental chance of this.
Second, when you double click to open the projects, it will invariably attempt to open them with 2010. You'll have to start with VS#### instead of the solution/project unless you're in the 2010 workspace.
I have VC6, VB6, VS 2008, and VS2010 RC installed on Windows Vista. I cannot double click on the VC6 dsp files without VS2010 opening and asking to perform the conversion. The 2008 C# projects open in 2008 as long as I use the solution file. The 2008 project file opens in 2010 instead of 2008 even though the version selector is the default program. Most of the time I try to remember to open the desired version of Visual Studio and then open the project.
You can mitigate some of these issues by changing the default program associations in the control panel or the registry.
Update: This setup works on Windows 7 x64, with the addition of VS2013.
Yes it can work. I'm not sure if you have to install them in a particular order... but install them in order of the versions... 2005, 2008, 2010. Should be good to go.
I can't speak for 2010, but I have run 2005 and 2008 at the same time on my system without any fuss.
And I made the double-click mistake that wheaties warns about more than once :(
I have VS2005 & VS2008 running without any issues. I have had problems when working with betas, express editions & am assuming you don't have them.
I would say refrain from making too many changes to the setup of these editions, it should be fine.
I also had the same doubt. I work at my company which is still on VS 2008 and I want to personally use the VS 2010 and not risk the 2008. I installed the 2010 and it worked fine with the 2008. Just make sure you note the projects that are in 2005 and open them with the same accordingly.
The reason why it works is simple: if you open your solution file in Notepad, you'll see which version of VS is related to your project.