RE: Sharing a database file

2015-11-11 Thread piers.williams
platforms have eventually got right over a 35+ year maturation cycle. Or is your single-file database already (somehow) happy with multi-thread/multi-user access? From: Greg Keogh Sent: Wednesday, 11 November 2015 1:20 PM To: ozDotNet Subject: Re: Sharing a database file Thanks everyone, I'll

Re: Sharing a database file

2015-11-10 Thread osjasonroberts
Hi Greg, just wrote this blog post yesterday - might be of use: http://dontcodetired.com/blog/post/Painless-NET-Windows-Service-Creation-with-Topshelf.aspx if you go the Win Service route. Jason Roberts Journeyman Software Developer Twitter: @robertsjason Blog: http://DontCodeTired.com Plu

Re: Sharing a database file

2015-11-10 Thread Greg Keogh
Thanks everyone, I'll stir all the ideas in a pot, cook it overnight and see what's floated to the top in the morning. The LocalDb option is something I forgot existed and I may use it in a different project. Using a hidden console app seems easiest at the moment, as the installer can add the singl

RE: Sharing a database file

2015-11-10 Thread 罗格雷格博士
:57 PM To: ozDotNet Subject: Re: Sharing a database file With the “SQL Server has too many dependencies that aren’t available”, which dependencies are the issue? Have you considered the localdb option? It’s targeted pretty much right at what you’re describing. Pardon, I was a bit vague there .

Re: Sharing a database file

2015-11-10 Thread DotNet Dude
Yeah what are these dependencies you speak of? Sql server is a windows service already ;) On Wednesday, 11 November 2015, Greg Low (罗格雷格博士) wrote: > With the “SQL Server has too many dependencies that aren’t available”, > which dependencies are the issue? > > > > Have you considered the localdb

Re: Sharing a database file

2015-11-10 Thread Greg Keogh
> > With the “SQL Server has too many dependencies that aren’t available”, > which dependencies are the issue? > > Have you considered the localdb option? It’s targeted pretty much right at > what you’re describing. > Pardon, I was a bit vague there ... the servers running these apps don't come wi

RE: Sharing a database file

2015-11-10 Thread 罗格雷格博士
-express.aspx Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3 8676 4913 fax SQL Down Under | Web: www.sqldownunder.com<http://www.sqldownunder.com/> From: Greg Low (罗格雷格博士) Sent: Wednesday, 11 November 2015 3:52 PM To: ozDotNet Subject: RE: Sha

Re: Sharing a database file

2015-11-10 Thread Thomas Koster
On 11 November 2015 at 15:16, Greg Keogh wrote: > Howdy again, I'm thinking aloud about a problem here in case there is > lateral thinking available. > > We have a mature app that uses a single-file database that is locked. Now > new apps want to use this file as well, but how can they share it?

RE: Sharing a database file

2015-11-10 Thread 罗格雷格博士
With the “SQL Server has too many dependencies that aren’t available”, which dependencies are the issue? Have you considered the localdb option? It’s targeted pretty much right at what you’re describing. Regards, Greg Dr Greg Low 1300SQLSQL (1300 775 775) office | +61 419201410 mobile│ +61 3

Re: Sharing a database file

2015-11-10 Thread William Luu
Maybe a self-hosted API using something like NancyFX? Eg: http://blog.amosti.net/self-hosted-http-service-in-c-with-nancy-and-topshelf/ and also https://github.com/NancyFx/Nancy/wiki/Self-Hosting-Nancy This is also pretty interesting too: http://www.onegeek.com.au/articles/a-nancy-net-microservic

RE: Sharing a database file

2015-11-10 Thread Eddie de Bear (Gmail)
Option 2: A windows service (as far as .Net is concerned) is any executable assembly that exposes a class derived from ServiceBase. I normally have my services written as a Console Application. Then, when the console app is run, if it’s an interactive session then I manually start the servi

Re: Sharing a database file

2015-11-10 Thread Mark Hurd
Because the functionality of setting up and installing a Windows Service is almost "out-of-the-box" available now, and has been available fairly easily since the start of the .NET Framework AFAIR, I'd go for that if at all possible. We have a range of "agents" that require a console to auto-logon