Originally Posted by drewprof
Wow that's excellent news about the reverse compiling. I am very good at modeling and have used VB6 professionally as well as C++ in a pure research environment so I understand when to use one versus the other. My problem was this C# since I did not peek into it to see what it is about and of course I have stopped programming right about the time the .net architecture came into the scene. Like GS said, burnout was a factor.
I was checking the web so I can compare the two of them and it seems like C# is not that hard to get up to speed but like FTL said if I am modeling business processes I might be better off with VB
but I am not too sure if this VB
.net is the same thing as VB6.
With time I will figure it out but I welcome your opinions to speed up my decision process, thanks.
.net is radically different from VBA or VB6. I had to take a couple of college courses to make the transition, the entire approach is different, and I would recommend taking at least the introductory. It is much, much tighter code than the old VB
. It is an extremely layered approach, where one object is stacked on top of another to achieve data flow, extremely complex and non-intuitive at first but extremely powerful once one has the hang of it . It creates tons and tons of code for you as you declare and manipulate objects that you can then modify if you desire.
I have coded nothing in C#, but I work with those who do, and they are fanatics. It's basic syntax is typical C so the transition for C/C++ programmers is much easier than from VB6 to VB
.net. It is web-focused C, essentially. In my industry it is being used for man-machine interface stuff, for example, say you had a production line producing chemicals in Houston and you wanted chemists in Chicago monitoring the various pressures and flows of your feedstocks, you would write a C# app that talked to the valves and then put the result into web pages that could be browsed at your lab in Chicago in real time over a web VPN. You could add alerts and graphics and all kinds of other neat stuff. Doing the same thing in VB
.net would take forever. Conversely, say you were a bean counter's dweeb, and you needed to access a million records produced by this C# app, summarize them, slice and dice some stats, and come up with a report that presented production on this line as a cost component of the plant as a whole, you would be insane to do it in C# because the SQL server interface alone would take you a month. So now the engineering dept uses C#, and the accounting and MRP people use VB
.net. But the new beauty of it is, when we are both finished the complementing apps, we can reverse compile into either language so we can now understand what each of us is doing.