>John,
>thanks for the comments. Hearing from people that have used it makes a difference. I also received a reply from someone at the company. I didn't mention it but the almost unusable help file was another reason. I am going to contact them and see if I can get the fixed version and take another look at it.
>
>One question. We have to send a lot of updates over the internet these days. What would you estimate the total size in K Bytes it would add to my system.
>
>Thanks again,
>John.

John,
There are two dll's that need to be loaded onto system, they are CommWrapper4managed.dll at 1316KB and NetExtenderSupport.dll at 32KB. These will rarely change, like VFP runtimes.

There are two files compiled into your application, ClrExtenderProcedures.prg at 17KB and netCLRClasses.VCX at 324KB. The .VCX references other vcx's that may or may not be needed. It looks like the maximum additional size to be around 700KB, but I believe that can be reduced to the 324 KB or less, depending on features used.

Since I just got this, I haven't spent much time trying to reduce it's footprint. But, now that my curiosity is piqued I think that I will map out the Vcx's and see.

John.


I spent sometime today checking this out. By separating ClrExtenderProcedures.prg into it's individual functions and procedures, I was able to compile only the procedures actually used. I also copied the netCLRClasses.vcx and removed the classes that were in it for purposes other than accessing the CLR. The result was that my application for the card readers went from around 700KB to 75KB.

I hope this is helpfull.

John.