Issues with creating a new WPF X# program

[wriedmann]

Hi Chris,
yes, you are right.
Maybe we should also specify that there are two groups of "new" class libraries:
- the System Classes and the RDD Classes that are simply evolutions of the current VO libraries, compiled for AnyCPU
- the SQL Classes and the GUI classes that are completely rewritten based on ADO.NET (SQL classes) and Windows Forms (GUI classes), so they may not be 100% compatible to the original transported VO classes. Specially for the GUI classes there should be noted that 3rd party libraries like bBrowser and SEUIXP may be completely rebuilt - don't know about ReportPro.

And I don't know id these libraries are also part of the non-subscriber distribution.

Wolfgang
P.S. IMHO the new, Windows Forms based GUI classes are really interesting, and I don't understand why not more people talks about them

[Chris]

Hi Wolfgang,

We aren't really advertising them yet (the Windows.Forms based VOGUI classes), because they are not bullet proof yet, to be used widely, and they do require a lot of changes in existing code currently, due to the strong typing. But we have thought about improvements in this area and have already found and fixed several things in the last months, and after 2.12 is out, I think we will start pushing more also on this front.

.

[wriedmann]

Hi Chris,
personally I do think that these GUI classes will be the way to go for new applications for experienced VO developers when developing speed counts.
Developing with Windows Forms and/or WPF the development speed goes down to much - and this is why for example Andreas has opted to develop new individual applications using the (old) GUI classes, even when starting development in X# (and we have some of them in production now).
Using WPF for us has only a sense if the customer is willing to pay for it, but not if money counts.
Wolfgang

[Chris]

Hi Wolfgang,

Is it really? Even after you build a set of base classes that offer the standard needed functionality to your forms etc? I know several VO developers who have created many new apps in Windows.Forms with X# (and even in vulcan!).

I think Windows.Forms is missing those nice basic (data handling) features we have in the GUI classes, but this can be implemented once and reused everywhere..

.

[wriedmann]

Hi Chris,
there are a lot of things in the VO GUI classes that are working very well: from databinding to a dataserver, pictures and multilingual support.
It would be a lot of work to add all these things to Windows Forms - and why we should spend that time?
One of the most important things that will have to be done for the new GUI classes is the bBrowser....and then ReportPro 2, I think.
I'm using much more the ListView control in the last times, but Andreas prefers the bBrowser.
Wolfgang

[Karl-Heinz]

[...]
Maybe we should also specify that there are two groups of "new" class libraries:
- the System Classes and the RDD Classes that are simply evolutions of the current VO libraries, compiled for AnyCPU
[...]

i guess it´s a typo and you meant:

- the System Classes and the RDD Classes that are simply evolutions of the current VO libraries, compiled for x86 only

instead of:

- the System Classes and the RDD Classes that are simply evolutions of the current VO libraries, compiled for AnyCPU

regards
Karl-Heinz

[wriedmann]

Hi Karl-Heinz,
no, I meant it exactly that way:
XSharp.VORDDClasses.dll and XSharp.VOSystemClasses.dll are AnyCPU.

xsruntime.png (85.26 KiB) Viewed 454 times

VORDDClasses.dll and VOSystemClasses.dll are x86.

Wolfgang

[Karl-Heinz]

Hi Wolfgang,

>> VORDDClasses.dll and VOSystemClasses.dll are x86.

yes, that´s what i meant.

To be honest, the whole thread is a bit confusing

regards
Karl-Heinz