Replies: 2 comments 2 replies
-
Hi Matt, I have used SQLite for something similar, works well for me. I use System.Data.Sqlite and raw ADO.NET to minimize dependencies and footprint |
Beta Was this translation helpful? Give feedback.
0 replies
-
We use SQLite too and store the database under the (hidden) .vs folder with the solution that it belongs to. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm building an extension that records the history of specific activities within Visual Studio. I'm fine with capturing the information, but seek advice on how and where to store it locally.
I'm looking at up to ~100 events per day and a couple of KB of data for each event.
Where should I store this on disk? (A subdirectory of
Environment.SpecialFolder.ApplicationData
?)Flat files or a Database?
If a database, what do you recommend?
It's not data I want or expect the user ever to need to look at or edit (as the extension will show appropriate summary versions), but I'm not concerned about securing it or obfuscating it either.
What might I have not thought about that I need to consider?
Do you have experience with something similar? Can you share your chosen option, why you chose it, and if you'd do the same today?
Thoughts, help, suggestions, and examples? - All welcome :)
Maybe, one day, I'll log all this information back to a remote server, but I'd like to start simple and keep all the data on the machine.
Beta Was this translation helpful? Give feedback.
All reactions