I just found the worst designed Visual Studio 2017 feature
-
In visual studio 2017 there is a memory profiler. You can take memory snapshot at interval of your choice while running a debugging session and compare snapshot for the number of object or bytes taken. Thing is: when you stop debugging because, say, you want to edit a file, it close all the snapshots! :omg: Now, I found a workaround, if you run snapshot comparison (while debugger is running, obviously) the window stay open. But, wait for it, if your snapshot comparison has been detached (in my case floating on the other screen), when you stop debugging it is closed! Losing all data collected again! Look like Microsoft doesn't want us accidentally using the information we just collected. This feature should remain a teaser... :mad: :mad: :mad: :((
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
In visual studio 2017 there is a memory profiler. You can take memory snapshot at interval of your choice while running a debugging session and compare snapshot for the number of object or bytes taken. Thing is: when you stop debugging because, say, you want to edit a file, it close all the snapshots! :omg: Now, I found a workaround, if you run snapshot comparison (while debugger is running, obviously) the window stay open. But, wait for it, if your snapshot comparison has been detached (in my case floating on the other screen), when you stop debugging it is closed! Losing all data collected again! Look like Microsoft doesn't want us accidentally using the information we just collected. This feature should remain a teaser... :mad: :mad: :mad: :((
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
This is called ... garbage collection ;P
-
This is called ... garbage collection ;P
haha so true! :laugh:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
haha so true! :laugh:
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
If you feel like digging in the VS Options, since there is a setting for pretty much everything, the probability is high to have one for keeping the windows open after the end of the debugging session. (and if not, you still have the option : you-are-a-programmer-why-don't-you-write-a-plugin).
-
This is called ... garbage collection ;P
No, it's not! Garbage collection is when some men come with a truck, noisily beat up the trash cans in your alley, dump some homeless sleeping in the dumpster into their truck, then set the dumpster on fire and after that they move on to the next alley.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
No, it's not! Garbage collection is when some men come with a truck, noisily beat up the trash cans in your alley, dump some homeless sleeping in the dumpster into their truck, then set the dumpster on fire and after that they move on to the next alley.
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
Looks like you live in a pleasant area. :rolleyes: Garbage collection usually makes the day of my son (but he is 4).
-
Looks like you live in a pleasant area. :rolleyes: Garbage collection usually makes the day of my son (but he is 4).
Not yet, but we are getting theren
I have lived with several Zen masters - all of them were cats. His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
-
In visual studio 2017 there is a memory profiler. You can take memory snapshot at interval of your choice while running a debugging session and compare snapshot for the number of object or bytes taken. Thing is: when you stop debugging because, say, you want to edit a file, it close all the snapshots! :omg: Now, I found a workaround, if you run snapshot comparison (while debugger is running, obviously) the window stay open. But, wait for it, if your snapshot comparison has been detached (in my case floating on the other screen), when you stop debugging it is closed! Losing all data collected again! Look like Microsoft doesn't want us accidentally using the information we just collected. This feature should remain a teaser... :mad: :mad: :mad: :((
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
Super Lloyd wrote:
You can take memory snapshot at interval of your choice while running a debugging session and compare snapshot for the number of object or bytes taken.
Can you? Wow. I just use it because it makes people sitting around me think I'm doing some really involved stuff. *goes back to playing game on phone*
-
In visual studio 2017 there is a memory profiler. You can take memory snapshot at interval of your choice while running a debugging session and compare snapshot for the number of object or bytes taken. Thing is: when you stop debugging because, say, you want to edit a file, it close all the snapshots! :omg: Now, I found a workaround, if you run snapshot comparison (while debugger is running, obviously) the window stay open. But, wait for it, if your snapshot comparison has been detached (in my case floating on the other screen), when you stop debugging it is closed! Losing all data collected again! Look like Microsoft doesn't want us accidentally using the information we just collected. This feature should remain a teaser... :mad: :mad: :mad: :((
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
It looks cool but pretty useless.. I used a free tool prefix.io for profiling mvc web apps, it's a great tool so far :-)
[Signature space for sale]