To be honest, I would leave the development as it is unless the EXE is
excruciatingly slow to start. With fast networks and fast servers, I wouldn't
think that would be that big of a deal. I'm not sure what cutting it up buys
you because you still have to kick off the people who are in that particular
module, so you might have to do that overnight too.
You could just create complete stand-alone EXEs that are called by a main
program they wouldn't have to be dlls. If there are common programs to each,
they would be included at build time into the EXE. But again, I don't know
what this really buys you.
If it were me, I would leave it as a big, single EXE.
--- On Fri, 11/7/08, Kurt Wendt <[EMAIL PROTECTED]> wrote:
From: Kurt Wendt <[EMAIL PROTECTED]>
Subject: Splitting of Distributable VFP System
To: profox@leafe.com
Date: Friday, November 7, 2008, 5:42 PM
Hello there folks,
I've been doing a little research recently on a problem with
regards to a system here at my new job. I work within the Apparel
industry. And, the application originally started as a FoxBASE++ system.
They are beginning to move to more of a Windows based system (they are
even creating a completely new version of their system based upon C# &
.Net - although I am not involved with that). However, on the VFP front,
they have been creating a new version of the system based upon Forms,
with much less PRG's. But, here in lies the problem.
Previously when they would distribute their system to their
clients - they would give them mostly FXP files - so their clients
can't' so easily look at the code. (Of course, someone with ReFox still
could - but, that's another story.) And, with their current systems that
have been pulled into VFP with minimal changes - and only a couple of
forms designed in VFP - they distribute an EXE to their clients, with
most of the rest of the system being FXP's. The EXE is not too big - at
like 1.4MB, since the rest is all just FXP's.
But, their new system, based almost completely on screens/Forms
- is now compiled into a single EXE application that is around 14MB -
and GROWING! So, the problem is two-fold. A 14MB EXE takes longer to
load each time a user wants to run it. But, the problem really is with
regards to upgrades. With the older system, fix a single program, then
upload that FXP to the client - and you don't have to kick everyone off
the client's system to install it. But, with the new app that is a big
EXE file - you must kick everyone off the system for each and every
upgrade. Or, in this case - they MUST do the upgrades at night!
As such, I was recently doing a little research into what
possibilities existed to split up the Windows EXE system into chunks.
Part of the concept was to split based upon functionality - like a chunk
specific to Order screens, another for Pick Tickets, another for
Invoicing, etc.
It seems that the most logical way to do this would be to create
separate project files for those chunks, which would include the
specific forms/screens - then compile those chunks as DLL's that would
be called from the main EXE distribution file. However, the creation and
calling of DLL's is not something I have done in the past. And, from the
research I did - it seems to require a certain amount of complexity to
implement - including the creation of OLE public class user-defined
classes in either program (.prg) files or visual class library (.vcx)
files. Then, after discussing this with one of the developers here - I
found out that the DLL's option poses another complication. Their
existing system relies on a LOT of Public variables (and, yeah - I don't
think that's the best thing to do either, creating a lot of pub vars -
but, I didn't create the original system) - and I was told that the
screens within the DLL's would NOT be able to see those var's. So, that
pretty much means the DLL idea is not a viable option.
I also read up a little on FoxPro link-library files (FLL's).
But, my research didn't turn up much on how to do this, and whether it
was really viable.
So - I am turning to this mailing list in hopes of getting ideas
for a possible solution!
I look forward to hearing replies from the group. FYI - I am
writing this e-mail at 5:40pm on a Friday night - so, I won't be able to
reply back to anyone until Monday - should someone post a reply soon.
Thanks,
Kurt
P.S. Just an FYI. This is my first posting to the list, so I am a newbie
here. But, not a newbie to VFP - as I have been working with it since
the initial Foxbase+ release! Am back in a fulltime job now, doing VFP
development - although I have been in-and-out of VFP developing over the
years, including 2.5 years as a fulltime Mr. Mom - although, at that
time I developed a system for my own uses - to track artwork, new
artists, review of artwork, and data to rebuild the gallery hosted on
Yahoo - which you can find here:
http://Gallery-3D.com/
(And - yes, I am one of the artists in the gallery - as I also do 3D CG
besides FoxPro, and I also teach classes in 3D at FIT here NYC.)
Too bad I found this wonderful mailing list so late in life - I really
could have used it about 2 years ago!!!
Anyway - sorry for the extra little [OT] stuff, at least the main topic
is ON topic!
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://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.
