I am a Powerbuilder programmer. Thanks to Chris Tacke's book and the PPC
newsgroups, I wrote a complex(sort of) eVB app that now needs to be ported
to C# (No, not VB.Net ).
I need some suggestions regarding the suggested or common practice for .Net
Windows App programming. I already realized that the programming style has
to change(I cannot refer to open forms and its controls and properties like
I am used to).
I am getting this book "The .NET languages : a quick translation guide by
Bisch" - might help.
Please bear with me as I am new to this style of programming (e.g. waiting
on a form to close in Main function).
Some questions that arise are
1) Should I have a GLOBAL connection object, just like I used to in eVB ?
2) Now I can actually close(read unload) forms - right ? Please say yes.
3) What are the main memory intensive objects I should be careful with (not
to overuse)
4) Is it ok or normal to have global variables of each form and to set them
in the constructor of that form so that they can be used to manipulate
objects(explicitly will convert these to public) within a form ? Or is there
any recommended or accepted OO approach.
More to come as I keep exploring this ocean of .Net
Any kind of suggestions, hints and links are appreciated.
Thank You
---------------------------
Srinivas R. Loka
---------------------------
|
Similar Threads
