General information
Category:
COM/DCOM and OLE Automation
Brian-
>I'm struggling with figuring out what a good second language to become familiar with would be. I was thinking of maybe VC++ or the newer C#. Since I've never had a "formal" programming background, either one will probably be equally as daunting.
Actually C# is _much_ less daunting than VC++, IMO. It's not so easy to shoot yourself in the foot, for one *g*.
I'm sure I shouldn't admit this, but I found C# to be something of a struggle to shift into the syntax. Not the trivial stuff like semicolons end a line, but bigger stuff, like terminology ("constructors", for a simple example), and the event binding was a little weird. I still haven't totally grokked that yet. It got easier when I stopped trying to translate everything into VFP terms, though. And I think it's just damned cool. Plus, I'm grateful I don't have to learn VB now. ;-)
I see there's a C# group here.
>Not to mention there's a whole lot of unproven technology in it. But, it'll be a fun project, and I envy that you have a .NET application in your lap. *g*
>
>
>Maybe not in my lap yet, but it would be nice if I could get a bit more involved instead. Perhaps an after-hours project is in order...
What's funny is what I'm hearing from my VB friends is that companies are very wary of dumping code into .NET. (Though no doubt there's a huge variation in attitude out there.) The folks I know really doing stuff are software house and control's vendors...people who have control over the choice and who are C++ shops. Warning, this all just anectodatal evidence and so it worth spit. *s*
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only