- #1
- 67,068
- 19,907
Is there a good way to think about the namespace/object/class/method paradigm when transitionig from non OOP C programming to Visual C# programmig? I've written Tcl/Tk GUI apps for manufacturing test fixtures in the past, but now I need to interface with multiple VISA instruments with National Instruments Measurement Studio and Visual C#.
I'd just like to get a better overall intuition for how C# program structure works, and when I would think about classes, methods and so on.
Thanks for helping out with some intuitive keys...
I'd just like to get a better overall intuition for how C# program structure works, and when I would think about classes, methods and so on.
Thanks for helping out with some intuitive keys...