Sometimes my class is becoming highlighted for a few second but soon the problem shows again. I tried build cleaaning, restoring visual studio, deleting my pages as I saw some people had similar issues and it was because of the xaml files.
Everything was great until last week.
I haven't noticed the reason of this bug. Also i tried using different namespaces and changed some folders, created new classes. Nothing helped
Please help me fix it as I have a lot of code to be done and my inspiration dies every time I see my class with white color)
This bug appears while using XamarinCommunityToolkit since version 1.3.2
https://github.com/xamarin/XamarinCommunityToolkit/issues/1815
I can't seem to be able to debug. When I try to, I don't get any build errors, and the layout changes to debug mode, but the windows never pops up. I have an orange bar at the bottom of VS, which I think is standard, but nothing happens after that. It's not just in the project I'm working on. I have started a new WFA and tried to debug without adding any code and the same thing happens. Anybody have similar issues?
I've encountered this before. Not sure what causes it, but generally it is one of a couple of things to fix it.
make sure you are building in debug and not release
close VS, go to the project's dir and delete the obj and bin directories. Reopen in VS and rebuild.
there is an option under tools - options - build (iirc) that allows for checking if source is same as code file. However, you should see a message in output window if this is the case.
on the project properties in the build (iirc) you can throttle the pdb file from full debug symbols to no pdb at all. If you are not the only person on the project check this setting still has full pdb enabled (low probability this got changed though)
make sure you're on the right platform that you are building to (x64 vs x32)
...lots more, but a starting place...
Addendum as per comment...
So, those messages are good. It is saying there are no problems (but it sounds like you already know that :) ). I would start with the general debug options you mention. Do this on a hello world app. That way you can troubleshoot the lowest common first. Here are my settings. Try to match them and see if that works. For example, I know "ask before deleting breakpoint" is irrelevant, but "break all processes when one process breaks" is important. So, I just added them all to make it easier to troubleshoot.
ALso, make sure you are getting a red dot here like so in your code in visual studio (I've seen instances where VS won't let you put this here):
Right click on the project
Click on the properties.
go to web.
Check the Box for Enable Edit and Continue .
Hope that helps :)
This is an issue with visual studio 2012. It doesn't ALWAYS show up. I've found that if you stop your program during debugging, or if you close the console window, this will almost always trigger.
However, letting it run to completion isn't enough either, sometimes this just happens.
Also you can build your application in debug mode, go to the output, run the program, and attach to that process. :P
Amazing answers already given but they dont help in the purpose. So here is my finding, no matter if i am late in answering, but it really works for me.
Even if you are developing a web app, just go to the website properties by right-clicking the project and then you see a "Web" tab on left as i have highlighted. Then just check the box saying "Enable Edit and Continue". Thats all you need to do. it works for me!
I had a similar problem, and solution was absolutely dumb. VS was confused with two instances of Internet Explorer in “Browse with” setting. So, I set Google Chrome (any browser) as default, and then set IE as default again. It deleted the other instance of IE (only one remained) and debugging was enabled.
Hope it help!
I had a similar issue.
I added up:
using namespace std;
and this solved the problem
For me, uninstalling the Redgate's Reflector plugin that had expired fixed it. I spent more than 4 hours uninstalling, rebooting, reverting to older code, etc etc..
When my default browser was changed to CHROME, I could no longer debug my User Interface. Setting IE back to the default browser fixed it. Alternatively you can attach the process plug-in during debug.
I had the same problem with my desktop application and as this forum says you should mark your project as a startup project, since visual studio has unmarked. It worked just fine for me an I believe it will help other people that may have this problem, since I believe you have finished this project.
One of my VB .NET Winforms projects wouldn't allow debugging.
This was due to the configuration manager set to 'Release' even though the toolbar dropdown indicated 'Debug'.
You need to select the mode dropdown and select the last option 'Configuration Manager' and ensure that the main project is set to 'Debug' and not 'Release'
Install Microsoft SSDTSetup.exe 450Kb and Close the SSDT tool during install. After installation open the SSDT tool and execute the script task and Component with breakpoint. Worked for me
try checking your output without debugging
Ctrl + F5
good luck
I tried googling, but I couldn't find a fix.
Before, when writing:
console.writeline();, C# would automatically uppercase it to Console.WriteLine();.
Now, by mistake, I somehow deactivated that function. If I write console.writeline(), it doesn't turn it into Console.WriteLine();. Any ideas?
What your looking for is called: Intellisense
The sole goal of this feature is to allow coding to be more productive, smarter, and easier.
You can renable Intellisense by hitting CTRL + J. That will manually reactivate it. Otherwise you'll need to go to:
Tools
Options
Text Editor
Auto List Member
But one of those should address your issue. Otherwise I might suggest running a repair on Visual Studio or Restoring it back to defaults. Cause by default it is enabled and configured correctly.
A known issue can also come from third-party Add Ons that actually handle such data can cause issues with Intellisense so uninstalling such Add Ons, then defaulting Visual Studio should fix it as well.
Example:
Resharp
Visual Assist X
Just Code
Etc.
Basically the ones that handle code completion, quick coding features.
Here is an article from Microsoft Developer Network.
Hopefully that helps.
I'm a fan of the overridden Intellisense behaviour provided by ReSharper. However, I can't seem to get it to display exceptions (anything with the /// <exception cref="SomeExcpetionName"/> xml comment). Does anyone know a way to enable this functionality?
NOTE: This is not an issue related to not including the xml comment file from a dll as it is happening for all classes (even core .Net ones). Plus, any of my own libraries, which I have ensured the XML file is included, are not displaying the exceptions in the comments either.
NOTE 2: I have tried selecting Visual Studio Intellisense instead of the ReSharper Intellisense (via Tools > Options > Text Editor > C# and turning on the Auto list members and Parameter information settings under the Statement completion section). This seemed to bring back the exceptions (after a Visual Studio restart). However, it only works when I bring up Intellisense via tab completion and not when I just bring up the tooltip for a method by hovering over the method call (this used to work... it even works properly for the first few seconds after starting up Visual Studio, but then something disables it again).
Specs:
ReSharper 5.1.3
Visual Studio 2008 Professional
Well after a reinstall that made no difference, I realized that the %appdata%\JetBrains\Resharper\v5.1\vs9.0\UserSettings.xml file was still there (which explains why a reinstall didn't work). I then did a diff on the file with another developer in my group that wasn't having the issue. I found the setting that was causing the issue.
If you wish to have your tooltips (inside of Visual Studio) show the exceptions that a method throws, you must have the following option turned off:
(In Visual Studio via the menu)
Choose ReSharper > Options > Code Inspection > Settings > Color identifiers
Uncheck the option if it is checked (disabled by default)
(In %appdata%\JetBrains\Resharper\v5.1\vs9.0\UserSettings.xml):
Find the <Highlighting Settings> section.
Delete <IdentifierHighlightingEnabled>True</IdentifierHighlightingEnabled> (You could also set it to False, but when you uncheck it via Visual Studio it actually deletes it).
Hopefully this saves some other people from the same headache. I believe this is actually a bug since using colour identifiers should have nothing to do with tool tips/Intellisense displaying possible exceptions. I'll report it to JetBrains.
UPDATE:
This issue has already been reported here.
UPDATE 2:
I was talking about this issue with one of the JetBrains support engineers and he said they'll see what they can do to address the issue in ReSharper 6. (No guarantees, but they are at least considering it).
UPDATE 3:
There is a linked case (same issue) that has been recently updated. The case has been set to a priority of show-stopper and is slated to be fixed for version 7.0.1.
Is there a way to turn off intellisense in Visual Studio 2008? I know about deleting a DLL to turn off intellisense in C++, but that doesn't work for C#. I also know about the preferences but that just turns off the visual display. I want to turn off ALL of intellisense so it does not scan my code at all.
Update 10/14/09: Eric was kind enough to take a look so I sent him some log info. I'll post the resolution here when we get one.
Update: updated title to reflect the changed direction of the thread
Related Question
Turning off Intellisense for a single project in Visual Studio 2008
The guys on the VS team looked at this for me and found a problem with intellisense. Here's their description:
"It looks like both of the files you gave me contain a part of static partial class EntityPropertyDescriptors, and I would guess that all the rest of the 500 files do too. What’s happening is that as we build up our IntelliSense cache, each time we parse one of these files, we see that it has a static class in it, and we decide to see if that static class has any extension methods. In order to look for the extension methods, we look through each method in each part to see if it’s an extension method. This causes us to reparse every file in order to see if the type has any extension methods."
They found a similar problem with VS2010 but are fixing it now. Unfortunately, they are not going to fix it in VS2008, so we are left with the workaround of putting all the partial classes into a single file. They can still be partials, but they must be in the same physical file to get around the problem.
After combining all partial classes into a single file, load time for this problem project when from 30 minutes to about 10 seconds.
Big thanks to Eric Lippert and Kevin Pilch-Bisson for helping me with this.
You need to switch off background compilation.
Here is a HowTo:
http://ira.me.uk/2008/09/01/switch-offon-visual-studio-2008-background-compilation/
Tools -> Options -> Text Editor -> C# -> Advanced -> Show live semantic errors
You will still get error underlining, but you must hit the Build button before they show up.
In tools > options > Text Editor > C# there is a Intellisense section which looks like it does what you want.
Have you tried cleaning your solution from all temporary files created by Visual Studio? Sometimes these files could get corrupted, the chances might especially be high if you migrated from VS 2005.
Close your solution, look for all *.suo and *.ncb files and remove/rename them, and then re-open the solution.
Just another thing to make sure: Are there any third-party add-ins installed? Try to start VS in SafeMode using the /SafeMode command-line option.