I recently upgraded to Visual Studio 2015 from 2013 because for some reason 2013 would not work on Windows 10 for me, even after multiple install attempts.
The only issue is IntelliSense is not displaying methods from other forms. For example, when I start typing one of the names of one of my forms, the only thing IntelliSense displays is:
However, the form has dozens of public methods, and the IntelliSense worked fine before in 2013.
Interestingly, I can still call the method if I remember the name by manually typing it, i.e. Form1.TestMethod().
Does anyone know the fix for this? I am using Visual Studio 2015 Update 1.
I have the exact same problem and opened a support incident with Microsoft. They have verified per their answer below, that this is a bug with VS 2015 Update-1. We have a few computers running with just VS 2015(no update 1) that work just fine. I will pass along any further information that I receive from Microsoft.
Response from Microsoft:
"Yes this happens only with Visual Studio 2015 update1. It seems to
be a bug in VS2015 Update1, I am discussing with product team to fix
this issue.
If you just avoid using default instance of forms. Creating a form instance, storing it in a local variable or field, and passing those
references around is easy enough. It's also a much better practice
that will make your code stronger overall.
Dim f As New Form2
f.TextBox1.Text = "Hi"
Related
Trying to install 'Visual Studio 2015 with Update 3' using the .exe installer provided for the visualstudio.com website. I also tried the standard version (without the update).
The black/grey installer opens, the green bar moves along the progress bar once and it crashes. I get a white pop-up window saying 'Microsoft Visual Studio Community with Updates has stopped working'.
I can't seem to find any other situations like mine on Google or StackOverflow.
I have Visual Studio 2017 also installed. Why do I need 2015 too? I'm helping (trying) another student who is using VS2015 and has problems - however, I can't even get it downloaded!
Thanks in advance for any help.
One possible solution is to not worry about 2015 and just help him by using 2017. It's hard to tell for sure if this will resolve your issue, as there is not info on exactly what you are trying to help him with.
If you go this route, I would save out the solution file just after loading it with _vs2017 tacked on the end, or something similar, so that you do not overwrite the info in his solution file. (Edit: The purpose of this is just in case it breaks something for him - it may not be a problem, he may be able to load your 2017 solution file fine). I've moved fluidly between 2017 Community and 2015 Express or Community with some solutions without a problem.
I do realize there are some issues that this may not be a solution for, but it should be an option, especially for those that are more language-based. The main problems with this solution would be if other student is using features or libraries that are deprecated in 2017, or directly struggling with getting VS 2015 features to work.
Go to control Panel -> Programs and features -> turn on windows features ,
Disable .net 3.5
check for windows update,
Then restart the system. Now it will work . 100% working .
Have fun.
I am facing a very, very strange issue in Visual Studio 2015 RTM, while programming a Windows Forms Application.
My Program class, (entry-point-) Main method has a routine that checks if a certain configuration file exists in the current output folder, alerting an error and forcing an Environment.Exit(-1) if otherwise.
I have a UserControl I intend to add to a particular form and... when, in design time, I try to add the built component into it, this happens,
crashing the IDE with it.
Please notice that the message alert was created after a generic exception was caught, back at the entry point (the Log extension method does it).
I'm running a VS2015 RTM version, along with a fresh-from-update Resharper 9.1.3 and PowerTools. This issue has not happened in VS 2013 Premium.
Has anyone here faced something similar?
UPDATE
I just realized how confusing a code in a foreign language can be, so I'll try to explain it the best I can, updating the first image.
UPDATE(2)
It has happened in VS2013 Premium, running a 9.1.2 Resharper and PowerTools. Am I missing something here?
UPDATE(3)
This is not an answer: Catching exception in Main() method
It happens in design time, not in debug mode.
Until quite recently it was possible to click on a method in the VS 2013 Solution Explorer and have the method appear in the code window. That does not appear to be working anymore. Any idea of how to enable this functionality? It was quite useful. For example, in the Solution Explorer view below, clicking on either addBlanks or formatSql would move the code window to the method in question.
It turns out that I have more information about this problem. I completely uninstalled VS 2013 Pro and reinstalled it. Somewhat predictably the problem went away... However, I was getting an error message about the NuGet package manager not being properly installed. To fix this I removed and reinstalled the NuGet package manager. That did resolve the NuGet error message, but the problem with clicking on methods in the Solution Explorer came back. Finally I removed and reinstalled VS 2013 Pro yet another time and now clicking on methods in the Solution Explorer works correctly.
Somehow the original problem reflects some combination of VS 2013 Pro, NuGet, etc.
It is still possible to quickly display a source code file. I am using Visual Studio 2013 Express Update 3.
It might make a difference to highlight/activate the right-most code preview symbol in the Solution Explorer panel:
It is located to the right of the properties screw-wrench symbol.
If this symbol is active, a single click on a file name is sufficient to get the file displayed in the code view. The same applies to methods. Double-click also works, when the preview symbol is not highlighted.
This turned out to be a bug in Visual Studio 2013 Pro Update 3 (and perhaps other versions). Microsoft recognized this bug and has fixed it in VS 2013 Pro Update 4. See https://connect.microsoft.com/VisualStudio/feedback/details/1001072/double-click-in-visual-studio-2013-update-3-solution-explorer-not-working for a discussion and Microsoft's resolution.
We have a mix of VS 2013 Ultimate & Pro in our project. That leads to a problem:
When writing with Ultimate we have stopped adding empty lines between properties & methods because the code lens inserts ~empty rows~ (see pic).
The problem is that it looks like a wall of code when someone using VS Pro reads it without the lens thing.
Question: Is there a way to get VS 2013 Pro to insert empty rows where the code lens would insert its stuff?
You asked Y, I am answering X.
Add the blank lines in the code. It solves the problem in Pro, and it also solves the problem of me (who never used code lens) not knowing which line belongs with which method.
15 references
public MaintenanceSettings Settings
31 references
protected override void Load
...
It's instantly easier to associate a lens with a member.
FYI: in Visual Studio 2015, CodeLens is now also available in Pro, so this issue only affects VS 2013 Pro.
Put the blank line in there.
As well you can vote on the feature here: http://visualstudio.uservoice.com/forums/121579-visual-studio/suggestions/4150271-make-codelens-available-outside-of-ultimate
Microsoft does look at uservoice regarding Visual Studio.
For a couple of weeks now I have been unable to merge Views within Visual Studio 2013 in response to conflicts when getting Source Code from Visual Studio Team Services. I am sure I used to be able to this (we recently moved from Visual Studio Professional 2012 so I cannot be one hundred percent certain - automerging may have been sufficient in the early days of the project).
The "Accept Merge" and move to next change/conflict buttons are all greyed out and inoperable. See screenshot snippet-
This originally only happened with Views, but now seems to affect some other classes. Changes are highlighted and indicated on the scroll bar so the diff tool otherwise appears to be functioning. This only originally affected me, but now affects a new colleague into the team.
I can still either Keep Local Version or Take Server Version but this is rarely sufficient. This leaves me manually altering the local copy to apply changes highlighted by the merge tool. (Edit - See a better workaround in "Second Update" below).
Has anyone come across this before?
Visual Studio 2013 Premium (patch RTM/Update 1/Update 2 - all with the same problem), with Resharper 8.2 (originally 8.0.2) C# and Web Essentials installed. Running on Windows 7 Professional x64.
Project is ASP.NET 4.5 using MVC 5.1.2 (now additionally updated from MVC 5 where the problem first occurred) (upgraded from MVC 4 following the upgrade instructions on the ASP.NET website) in C#, using latest versions of Razor (3.1.2) and Entity Framework (6.1.0 RTM).
Edit: Initially a repair install of Visual Studio 2013 appeared to have fixed the issue. It has now however returned exactly as it was before. Since it took an hour to do the repair I cannot repeatedly do this in order to merge views. I am currently able to round trip the solution between Visual Studio 2012 Update 4 and Visual Studio 2013 in order to do merges in Visual Studio 2012 where it is working normally.
Second Edit: I am currently manually resolving conflicts by selecting the desired code (local/server), saving the merge window and then closing it which will prompt to accept the merge result. This seems to function but is obviously sub-optimal. It may however be helpful for other users.
In the event, installing Resharper 8.1 on top of 8.02 appears to have fixed it fixed it briefly before the problem returned yet again. I had previously completed a repair install of Visual Studio Premium 2013 as well - which briefly seemed to have fixed it before it broke again. I only mention it in case the fix is cumulative.
I am unclear if it was a bug in Resharper that was somehow preventing the merge, or a persistent problem with the installation that the upgrade cleaned up (Resharper removes previous versions and then installs updates, rather than attempting to install over the top). Update - I am extremely confident that this is not related to ReSharper and that it was the configuration of Visual Studio as a result of re-installing the extension and not the extension itself that fixed the issue.
In either case, the issue (for now) seems to have disappeared and this seems to be related to the upgrade, or is an extremely strong co-incidence.
Colleagues with the same versions of Visual Studio and Resharper, working on the same project, the same version of Windows and (in one case) the same hardware were not affected, so it seems likely it is an edge case niche issue caused by corrupted data somewhere.
I have a current working theory that this is related to different patch versions of Visual Studio (for example Visual Studio 2012 Update 2, Visual Studio 2013 RTM, Visual Studio 2013 Update 1, Visual Studio 2013 Update 2. This only affects Visual Studio 2013 for us.
Simple solution I use is carry on with your manual merge process once you are done simply Close the Merge-* tab (the one you are using to merge files) this will bring up a prompt for confirming if you want to Save the changes made (this is the merge changes you made to your local file) click 'yes' Now it comes back to Resolve Conflicts tab and brings up another prompt asking if you want to Accept Merge Result, click 'yes'(this is same as the button Accept Merge)
Since you have VS2012 installed and merge is working there, you can create a link to its TF.exe in VS2013, similar to one on the picture below, and fix the issues there. Set Command to c:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\TF.exe and Arguments to resolve.
You do that in Tools->External Tools.