visual foxpro - Converting multiple VFP9 classes to C# -
let me start saying have not programmed in heavily oo programming language since java in college (i graduated in december 2005). since i've graduated have been programming foxpro 2.5 - vfp9. now, company work pushing convert of our foxpro applications c#.
my part of project converting our report parsing application. in vfp9 consists of 5-6 forms (none of carried on have created new c# front-end replace it), single base class contains of our standard methods, , approximately 575 individual parser classes (some of nothing set few parser specific variables/properties , call needed base classes). of parsers contain own custom methods still use , interact base methods , global properties.
now question...
from design standpoint, our new c# front-end spawn multiple executables (3-5 exes) call our new c# base/parser class libraries (dlls). original thought have 1 solution/project base_code.cs , other 575 parser.cs files (h1.cs, h2.cs, h3.cs, etc). however, need capability build each .cs file independently of others may updating base_code.cs while co-worker updating h1.cs.
how best structure this? keep 1 solution create 576 projects or create 576 solutions using same namespace team attempting currently?
there several global variables/properties use throughout base code , each parser (these passed in front-end application) file paths, file names, etc. static needs taken consideration when thinking of design.
edit example **
the c# front-end queueing system , file/status viewer. front-end "queues" reports pick throughout day. report @ top of list determines dll needed. front-end application , dlls separate.
example: h00001_2342318.msg - call h00001 dll h00002_3422551.msg - call h00002 dll
each h00001, h00002, etc (575 dlls in total) use methods in base dll.
if have update h00001 dll, need without having rebuild 575 dlls.
it sounds want "plugin" kind of architecture. lets drop in / update dlls (assemblies) without recompiling main app.
e.g. http://code.msdn.microsoft.com/windowsdesktop/creating-a-simple-plugin-b6174b62
and related.
Comments
Post a Comment