Menu
I'm hunting for a bug, and it would be really helpful if I could dump the contents of the objects my Locals Window to a file so that I could compare it in Notepad++ with another object record that works correctly. The problem is this: we are not sure if there is a bug in code or a discrepancy in the record.
Is there some way to save a object/variable to disk?
I found this extension, but sadly it is only for VS 2010, and I have 2012.
299
From the File menu, choose Save File As, and then click the drop-down button next to the Save button.
By default, VS Code requires an explicit action to save your changes to disk, Ctrl+S.
You can use serialization to persist an object's data between instances, which enables you to store values and retrieve them the next time that the object is instantiated. In Visual Basic, to store simple data, such as a name or number, you can use the My. Settings object.
In the Documents folder you'll find another one called Visual Studio, followed by a year. In this folder there will be one called Projects. Your work is saved in this folder. In the 2019 version, you may have to create your own folder structure.
You could use the ObjectDumper extension. It's also available as a NuGet package.
129
I'm a bit late to the party but I created a Visual Studio extension called Object Exporter that does exactly what you're looking for. It will export any object in your debugging windows (currently only limited to the locals window) to JSON, XML or CSharp object initialization code.
Here's the extension: Visual Studio Marketplace > Object Explorer
And here's an accompanying blog post: Exporting Objects from the Visual Studio Debugger
44
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
