From: Boudewijn Lutgerink
VFP and .NET
Friday, August 28, 2009 8:24:14 AM
This message was rated by:
# Ratings: 1
The guys and gals at eTecnologia are working hard in making the next update of the NetCompiler available.
Right now there is one bug in a sample that ships with the product, they want to make sure that this bug is fixed before shipping it.
What we may expect on new features is this:
Some fixes in the VFP Forms designer, including Visual Inheritance.
The property sheet now has a combo Tree that displays the nested controls, like VFP does.
Coming with the next update is a sample called VFPNetControls01.
In this sample the following features are shown:
Net controls can now be hosted in vfp forms.
Visual inheritance for those controls is supported.
Auto event binding is automatic.
The IDE is improved. Error markers give you better and more useful error descriptions.
The call stack window, that one that tells you what the path to the error is, is now no longer confused by attaching and detaching to and from processes.
Debug info for the loops (IF, Do While, For EndFor) is improved.
Abbreviations, the famous 4 letter words, now work in the command window.
PARAMETERS are now supported in the top level procedure.
So you can call your executable with parameters.
You can now invoke a prg just by doing SomePrg([params]).
This means more of your code compiles without errors.
Catched (with CATCH TO) exceptions are now similar to VFP Exceptions with the same properties.
A new property InnerException in the Exception object, gives you access to the underlying .NET Exception object.
LOCAL now supports dot syntax for types to be more compatible with VFP as in: LOCAL oInfo as MsGraph.Chart.
This syntax is valid only for LOCAL variables.
TLOCAL only supports NameSpace::Type syntax for consistency with the rest of the language.
PUBLIC vars are now working.
A new command ADD PROPERTY is available in classes.
This let you add new properties at design time to an inner object (eg an object in a form).
The added property becomes an structural property associated with the object, and therefore is inherited by any subclass.
The syntax is: ADD PROPERTY
.Object.NewProperty [AS SomeType] [= expression]
As said, eTecnologia is debugging one of the samples, so they are certain you receive a working thing.
This bug seems to be a mean beast, some patience is appreciated and once this update is available a loud applause is well received.
Stay tuned, we're back after the commercials.
Truth is a hallucination that the majority of people agreed upon. . . So why do I keep on questioning "the truth"?
Posted by Boudewijn Lutgerink @ 8/28/2009 8:24:14 AM