Always great to see your name Richard. I hope all is well. Well, I was afraid of this. With some careful manipulation of registry and environment variables I think I can support both v3.4.9 and v3.4.10 on a single system. But loading .NET v1.1 SDK onto a system that already has all of the other higher .NET releases isn't a good idea.
Source isn't shipped with our utilities and to my knowledge jBase doesn't support a way to securely deploy a package with source that gets injected into the compiler (no MV DBMS does but I really wish they did!). So we need to deploy object-only and it looks like our download page simply needs to separate out each supported jBase release. Unless someone has a better idea, I'll reinstall each release into separate vmWare environments. Thanks again, T > From: Richard Kann > > Actually 3.4.10 and the earlier releases are different > object code. I discovered that the hard way. > > Richard Kann > > Simon Verona wrote: > > Tony > > > > I don't know a great deal about 4.1 so my comments > > relate to 3.4 only. > > > > MingW is included with the 3.4 release as a "free" > > compiler. I wouldn't use this though, and the > > preferred option is the Microsoft DotNet compiler > > (just install the Full DotNet 1.1 SDK available from > > the Microsoft web site - use 1.1 and not one of the > > later versions). I believe the release notes state > > that MingW is not for "production" use (though I could > > be wrong). > > > > I believe that in general the object code produced is > > compatible with any 3.4 system (though I'm never fully > > convinced and always ship source code and compile on > > the target system before automatically deleting it). > > > > Beyond that I can't think of anything that would cause > > you problems - unless you've used some functionality > > that is specific to 4.1 and not available in 3.4 (but > > I'm sure that the compiler and some testing would > > easily identify these). > > > > HTH > > > > Simon > > > > > > > > -----Original Message----- > > From: Tony G > > > > We have requests for NebulaXLite (rich Excel > > spreadsheets from BASIC) on v3.4 for Windows but the > > original build was done on v4.1 for Windows. I moved > > the accounts to the target system and executed > > UpdateMD. I can see all files and compile programs. > > It looks like it's ready to go. > > > > As expected, LISTF shows some files as type J4, and > > I'm wondering if there is anything lingering in this > > environment that might cause grief. I especially > > don't want to give clients a full account for > > installation and cause them grief with a v3/4 hybrid. > > If required I could easily just create accounts in v3, > > move code over, and not confuse it with anything from > > v4. > > > > The 4.1 system had Java and VC++ but the 3.4 system > > has no Java but does have mingw. Because of this an > > error is displayed for %JRELIB% in jDiag, but I think > > this can be ignored. No? > > > > Can I expect object-only code that is generated in > > this environment to work in any target 3.4 system? > > Would there be a mingw/VC++ issue? Does it matter if > > this is 3.4.10 and some targets are 3.4.9? > > > > Thank you kindly. > > > > Tony Gravagno > > TG@ nospamNebula-RnD.com > > Nebula R&D sells mv.NET and other developer utilities worldwide > > and provides related development services > > > > Many articles of interest to jBase developers: > > no!spamNebula-RnD.com/blog > > Enquiries about NebulaXLite for jBase v3,4,5 welcome: > > removeNebula-RnD.com/products/xlite.htm > > Visit PickWiki.com ! --~--~---------~--~----~------------~-------~--~----~ Please read the posting guidelines at: http://groups.google.com/group/jBASE/web/Posting%20Guidelines IMPORTANT: Type T24: at the start of the subject line for questions specific to Globus/T24 To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en -~----------~----~----~----~------~----~------~--~---
