On 29 November 2017 at 16:45, Dave Crozier DaveC@flexipol.co.uk wrote:
People far and wide!
In VFP we are all used to writing the app, generating an .exe and placing it on a server for everyone to use in a network environment, no problem.
I do exactly that in my main C# app. 1000+ installs with no problems (other than the usual security rights issues etc).
Being somewhat of a philistine, up until my machine when "Pete Tongue" last week I have always used Visual Studio 2008 for my C# development but decided to "upgrade" my development environment to Visual Studio 2012 as it has a lot more features. So far so good apart from when you come to deploy your package as 2012 doesn't have an inbuilt deployment packager but a free paired down version of Installshield is available or you can use the VS2012 On Click deployment facility which I have never used before.
Why not 2017? You're missing a lot.
Anyone got any ideas, or will I have to resort to the good old or newer (in my case) Inno Setup.
I use the Nullsoft installer. It's a glorified unzip really. The only real difference is that I run the database upgrade utility at the end.
Hints and pointers appreciated. The biggest problem with this app is that there are a set of third party .dll's that have to be installed and registered on the local machine as simply placing them in the executable folder on the server doesn't work ... as it would do with VFP.
Hmmm. That should work fine. C# is no different to Fox in this respect. I use 3rd party dlls (zip library, report engine) without registering them.