I know, I know, I'm digressing. 

However, I've seen a couple of references in this thread about installers
people use and I wanted to jump in here and throw my two cents into the
discussion. 

I have for years now used a really simple desktop app installer which seems
to have been built expressly for FoxPro. I've used it for almost 20 years
now and I love it. One of the best purchases I've ever made. 

InstallCreator 2 by Clickteam is one of the easiest GUI install creators
that I've looked at it and it takes just seconds to select files and create
an installer package. Put all your files in a distribution folder, pick that
folder, set the name of your icons, choose the preferred installation
folder, set any license or user information you want to include, check a box
to add an installer and check other box to auto-run your application after
installation. Click build and you are done. 

http://www.clickteam.com/install-creator-2

Free version available, Full Version $59 and Pro version runs $149 I think.
I use the Full Version and it serves my needs perfectly. You can map
installation files to multiple folders, you can pick and choose graphically
which files to install and which ones to ignore. I think the pro version
allows you to create multiple installations based on demo and registered
versions in the same installer package. 

I've even used it to create mini-installers which I include in my
application folder. I can either run those at the end of the installation
process, or I can just put them in the main program folder to run only if
necessary. 

Paul H. Tarver
Email: [email protected] 

-----Original Message-----
From: ProfoxTech [mailto:[email protected]] On Behalf Of Paul
Hill
Sent: Wednesday, November 29, 2017 11:27 AM
To: [email protected]
Subject: Re: [NF] C# Apps Deployment

On 29 November 2017 at 16:45, Dave Crozier <[email protected]> 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.

--
Paul

[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to