this is really giving me headaches, ever since I installed the last update pack, visual studio[2012] keeps removing white space at the end of each line when I save a file.
it's fine if I'm working on personal projects, but not when working on team projects where code changes are reviewed that gives reviewers hard time for so many changes made turn out to be white spaces
I can't find any settings that turns this off, there're some posts online mentioning about injecting a piece of macro in the IDE to stop this from happening. Seriously? I can't believe Microsoft delivers such a bad feature that there's no way to turn it off...
can anyone here help me out please?
please note it's Visual studio 2012
Related
I have a problem with VS 2019 editor for a while, but it became a real problem lately.
Specifically, with the editor open, I cannot navigate to objects / classes and their methods or properties
You can see example in the screencast below.
https://www.screencast.com/t/0ceZ4C3TabY
I have the latest version, 16.10.2
This happens on two different PC's.
The problem started in a previous update, but I don't know which. I noticed it few times ago, but I didn't paid attention.
Does anyone else encountered it, and knows any solution?
Thank you
The problem was finally fixed in 16.10.3
I encountered today that with one of the latest releases of Visual Studio, it seems that the collaps / expand function now has a third state for the summary block.
When I expand the '#region Methods' (see pictures) all methods are displayed only with three dots [...]
Why aren't the method names displayed anymore as it was before?
Is it possible to have it the old way again?
Is there a setting?
I already tried to find a setting for it in the options, but couldn't find any when searching for the following words:
collaps
expand
summary
threestate
This seems to be a small bug in Visual Studio.
After I restarted Visual Studio, the behaviour is gone.
(Obviously I should have done that before asking questions...)
The diagnostic tools in Visual Studio 2019 Community have stopped working. It shows it's recording the CPU profile but whenever I pause the program to see the results, the tools say "There is no data in the current set of filters."
It was working at one point, and as far as I'm aware, I didn't change anything. And if I go into the Filter drop down menu it shows everything except "Hide native code" is selected.
How can I fix this?
A recent Windows update has apparently added a second problem to the original NVIDIA Display adapter issue.
See this ticket in Microsoft Developer Community: No Data in CPU Usage Tool, Windows Update related
Recently a Windows Update broke the CPU Usage tool in Visual Studio
where no data is collected. After analyzing the tool will report,
“There is no data in the current set of filters”. This is due to a bug
in the Windows ETW subsystem such that profiling events are not
emitted, we are working with the Windows ETW team to root cause the
issue and create a fix. As this affects ETW, the underlying system
which creates the profiling data, this will affect any ETW profiler:
Visual Studio, PerfView, WPA, XPerf, etc.
This is also discussed in the Microsoft Developer Community link in Andrey's answer, profiling CPU still states no user code was running. Scroll down to Mar 17, 2021.
It seems that there is now another underlying root cause besides the
original NVIDIA one which is breaking ETW profiling system wide. This
means any ETW profiler (Visual Studio, WPA, PerfView, etc) will be
affected since all of them rely on the same ETW system. Unfortunately
the EnableTraceEx2 system call returns success and we end up with no
profiling data in the resulting trace which is making debugging
difficult. I’m engaging with the Windows team that owns the ETW
subsystem and will most likely need additional diagnostics once we
figure out what our next steps are. In the meantime if anyone has paid
product support licenses feel free to engage with that as well,
hopefully working together we can uncover the root cause. Once I get
more information from the ETW team I’ll report back, until then stay
tuned.
Hi folks, just wanted to let everyone know that we have engaged with
the Windows ETW team on this and they are investigating. It seems like
a recent Windows Update may have caused this issue and they are
working with an internal customer in Xbox who has a repro. When I have
more info on the cause, workaround, and fix I will let everyone know.
In the mean time stay tuned.
I've found an answer here. For now, the only solution seems to be disabling NVIDIA Display Adapter in Device Manager and reboot.
In my case the other sampling profilers, e.g. AMD μProf didn't work well either with that driver.
I have been having this issue for months and no fixes have worked but using the Visual Studio Installer I ran repair on the IDE and now profiling works properly.
Edit: This didn't permanently fix the issue. But going to "Virus and threat-detection settings" and disabling "Real-time detection" allows it to collect data now too.
Edit2: My first appears to be the root cause for this and there is a MSFT solution here
I've spent the better part of about forty eight hours dealing with this issue. I've read all that is said about it on this forum. (Which isn't much.) And I've read all about it elsewhere. And I still have not found a solution.The problem.
It's simple. My project builds successfully. When I start the debugger, I get the endless blue loading circle. It never launches into the browser.
If you know what the issue is, please do share I would be grateful.
Thanks,
CM
For the record, what worked for me, was running my program in a terminal. Completely bipassed Visual Studio's buggy UI.
I don't know what caused the infinite blue loading circle.
And I don't care.
I'm moving on.
Thanks,
CM
I'm experiencing some strange behaviour with my ASP.NET MVC 5 application, running on Visual Studio Ultimate 2013, in Windows 8 Professional, and using MongoDB 2.6 as the database.
Originally, there was one solution; let's call this Alpha. Then, I copied the solution (literally copied and pasted in Windows Explorer), to create a new solution; let's call this one Bravo. I changed the solution and project name and all associated filenames, then edited the content of Bravo significantly such that it appeared very different to Alpha when the application was run in a browser.
The strange behaviour is as follows. If I am working with Bravo in Visual Studio, and I run it in a browser, then everything appears as would be expected with Bravo. However, if I then load Alpha in Visual Studio, and then I run Bravo, then the website that is displayed is actually that represented by the code in Alpha, not Bravo. If I then close Visual Studio instance running Bravo, restart it, and then run the Bravo application, the website displayed is back to the expected version for Bravo.
So, it seems that there is still something remaining in Bravo that is referencing Alpha. If I load up Alpha, then something is being loaded into memory which overrides the data which Bravo provides during the application launch. Only when I restart Visual Studio and refresh this memory with Bravo, does it run with the updated version of Bravo, rather than the original version of Alpha.
Similarly, if I have Alpha loaded in Visual Studio, and then load the Bravo solution in another instance of Visual Studio, then run Alpha - it displays what I would expect to appear from Bravo.
Any ideas on what is causing this behaviour, or how I might investigate this further?
Thanks :)
Sergey is correct.
I have this happen all the time, when going back and forth between web solutions that I host in IIS, I always have to change the paths back and forth. This started with VS 2012 and continued in VS 2013.
I can't find much information on why it is happening or how to correct it. There are only work-arounds as far as I can tell.
Workaround and info on the bug request
another potential post on same subject.
I personally, just manually change it back and forth.