So I just upgraded to Visual Studio 2017, and sure enough I encountered a few problems. The most recent one is the XAML designer is refusing to show colored syntax highlighting. Here's a picture:
I have tried resetting my settings through Tools->Import and Export Settings->Reset All Settings. However, this did nothing but reset my layout. Is anyone else experiencing this? How can I fix it?
I think the font's or the settings for the XAML highlighting are missing. The easiest thing that I suggest you trying, which is already available to you is:
1)Go to Start
2)Search and run Visual Studio Installer
"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe"
3)You are going to have 3 options depending on the version you have installed
4)You will have 3 Buttons. Click the hamburger menu button (3rd).
5)Select Repair.
That should repair the installation and I believe it should work just fine!
I see you already have an accepted answer but I have discovered a much easier way to resolve the issue that worked for me on both of the machines where I was being affected by it.
I simply opened up Tools -> Options, expanded Environment, clicked on Fonts and Colors and then changed my Theme from Dark to Blue and clicked OK.
The XAML window then reflected the new settings and had proper syntax highlighting. I then switched it back to Dark (because real developers use a dark theme) and the syntax highlighting has worked ever since.
Good luck.
Every time we open Visual Studio, the following tab is opened:
Is there a way to disable this behavior?
Perhaps to ask this in a more generic way, in which it would be helpful in other applications, can you disable extensions/dependencies from screwing with your Visual Studio layout?
The web page should pop up only once, when you have installed NServiceBus for the very first time via Nuget. It popping up every time is an anomaly and I agree, is very annoying. That said, we are in the process of removing the Visual Studio Popup starting from Versions 6.1.0 and above. You can find the details of that change here: https://github.com/Particular/NServiceBus/pull/4280
For the current version that is annoying you, i.e. the solution that you're opening that's causing this behavior, can you have a look at the init.ps1 from the nuget package and check to see the registry keys are present?
Feel free to reach out to us directly by opening a support incident here:
https://particular.net/support
Hope this helps. Cheers.
My colleagues and I had the same problem a few years ago.
You can disable the pop up manually by setting a registry string value at:
[HKEY_CURRENT_USER\Software\NServiceBus\{Major.Minor}]
Called MachinePrepared with a value of true.
I've installed Visual Studio 2012 after reformatting my computer.
When I open a xaml file in a new empty wpf project, it opens it in a regular code editor and doesn't let me choose Design View (the option is just not there).
Right-clicking the xaml file and choosing "View Designer" opens a new code window instead of a new designer window. (yes, the same code window is actually opened twice)
Right-clicking the xaml file and choosing "Open With" shows that I'm missing the Xaml UI designer editor. (it doesn't show anywhere on the list)
I've tried running "devenv.exe /ResetSkipPkgs" and "devenv.exe /resetuserdata" and Repairing visual studio's installation all together (both by re-installing and the Repair button in the installation wizard).
Nothing seems to help.
Anyone familiar with the problem and knows how to fix?
Something else to try, I know a lot of folks disable the designer for performance reasons. This is done with a file extension association in visual studio. I'm wondering if the reverse may help you?
If you right click a XAML file in your solution and select Open with...
... You should see XAML UI designer as an option! select it and click 'Set as default'.
Hopefully that works for you.
I am just guessing, but my experience with VS2012 is, that sometimes it cannot access the registry, because it fails to set an owner for the newly created registry keys.
Without owner noone but the System can access those Keys.
I used resplendence Registrar Registry Editor Trial Version to Fix the broken Keys.
I would especially check
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0
and
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\11.0\XamlEditor
because you can find all the settings there.
In addition i experienced this error only on recently reformatted win 7 systems.
And all of them have ssd's, but i am not sure if it only occurs on systems where no "old" harddrive is. But i found some people on msdn who also experienced issues whith VS2012 and having only a ssd in the system.
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 think this is just happening to me, but every time I start my project in VS I have to do devenv.exe/resettsettings otherwise the intellisense doesn't work. Does anyone know any special reasons as to why?
These options should be enabled:
Tools->Options->Text Editor->C#->General->Auto list members
Tools->Options->Text Editor->C#->General->Parameter information
Tools->Options->Text Editor->C#->Intellisense->Show completion list after a character is typed
If it doesn't work try this:
Tools->Import and export settings->Reset all settings
after many posts, I can solve this problem well:
Execute developer prompt command for visual studio 2012 --> gacutil /u Microsoft.VisualStudio.CSharp.Services.Language.Interop
solved the problem for me.
Close the current Tab (in which Intellisense is not working) and reoppen it. Many times this was enough for me, boring, but enough.