Choice of permanent storage for ClickOnce and multiple processes/threads


hello,

i'm unsure if right forum question relates several different areas.

i have application written using .net 4.0 using visual studio 2013 (mostly c#). deployed using clickonce .net framework prerequisite. because of environments , customers application deployed number of prerequisites needs kept @ minimum.

several instances of application can ran @ same time. processes/instances need share data placed in application clickonce data directory. done using xml-files application trying synchronize use of these files using mechanism similar lock files. unreliable , not robust "coarse". solution needed. seemed logical sql server compact edition. understand ce provide mechanisms sharing data , synchronizing access  it. possible distribute files needed part of clickonce application (not requiring user install separate package requiring administrator previliges). however, seems if ce being discontinued in favor of sql server localdb , localdb should used instead. localdb solves problems requires separate installation administrator previliges. i'd rather not require of customers.

so question is: best option me here? goal have reliable , shareable data store requires no separate installation , administrator previliges , can deployed part of clickonce-application.

thanks in advance!

/johan



Visual Studio Languages  ,  .NET Framework  >  Visual C#



Comments

Popular posts from this blog

Azure DocumentDB Owner resource does not exist

job syspolicy_purge_history job fail in sqlserver 2008

Trying to register with public marketplace error with 'Get-AzureStackStampInformation'