CODEWITHSUNDEEP
c#dll
Danil Eroshenko
Danil Eroshenko

Reputation: 490

Better solution to store data for dll assembly

I'm developing a dll that is supposed to be commonly used (in nuget for example). Simple description: my DLL simplifies message exchange with a particular service. It allows to send a request, then retrieve a response. Service is asynchronous and it can create a response in a hour or a day after accepting a request, so after making a request my dll calls service every few minutes to check out for response. The problem is that the app that uses the dll can be restarted therefore storing a request queue in memory isn't a good option (I don't want to lose info about requests). Neither is serializing it to file, because I can't know for sure where my dll will be used - it could be pc app, mvc. My main options is: serialize to file, but give an option to set a address where to place serialized files via web/app.config or make a user to think about it. But maybe there is some better solution about how to store requests queue?

Upvotes: 1

Views: 536

Answers (1)

Chrille
Chrille

Reputation: 1453

I would put theses type of configuration or data files in a subfolder to the %appdata% folder. You will have write access to files in this folder and the documentation is extensive. Read more here.

in C# you can easily get this folder using:

var appdata = Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData);

Or use Program Data:

var programdata = Environment.GetFolderPath(Environment.SpecialFolder.CommonApplicationData);

Upvotes: 1

Related Questions