|
|
you could always try Delphi.Net - the change from native to .net is via single include !
|
|
|
|
|
.NET executables are pretty small. Thinking about it, .NET pretty much did what Delphi has done few years, allow you package components and code into external libraries.
Word of advice though, don't even bother trying to write a fair sized application in Delphi for NET, the IDE is horribly unstable and is greedy for memory. You would be better of using C# Builder (which we are using with great success), or VS of course.
|
|
|
|
|
Good ol' Delphi. It was a great language/compiler ... the only reason we're not all Delphi developers is that Borland was lacking the corporate marketing power of Microsoft.
But that's just my two cents and probably nowhere near accurate ...
|
|
|
|
|
My first language was C#... so i do kick kiddies;) for using VB
I can have my cake and eat it too.
|
|
|
|
|
...and I kick you for knowing too few programming languages.
You're lacking experience, kiddie!
____________________________________
There is no proof for this sentence.
|
|
|
|
|
I've seen (not used) every version of VB (even VB for DOS), I've got to say the thing I hate most about VB is the syntax, it's ugly, apart from VB.net, VB was never an OO language and people abused it for it's easy of use and allowed unqualified users to become programmers overnight was generally gave VB a bad name because of the horrendous applications that were created.
We made the buttons on the screen look so good you'll want to lick them. Steve Jobs
|
|
|
|
|
With you on the syntax . I came from assembler to C . C was nice , such a clean syntax . Then C++ , similarly nice and clean . Then VC++ , ok now it gets murkey , the language is ok but MFC has some dodgy choices . Then came C# , nice and clean with a class library written by a team who understood how developers think. But C# V2 (This time its personal) is starting to worry me , can't put my finger on it but its starting to feel like it there is a VB mind in the background somwhere with a few more options arbitrarily dropped in . If we end up supporting 1 based arrays , thats it I'm off to Java land .
|
|
|
|
|
Ah yes, Syntax... C++/CLI has some great Syntax! I program in
C++/CLI. I've not programmed in C#. I was thinking it was a
grown up VB; until I recently converted a really complex C#
control to C++/CLI. I have changed my mind about C#; but I still
perfer C++. Call me a traditionalist. Still... the syntax strains
my patience. One has an enum class and one can not use that
enum class as an array index without casting to int (YUG!)
somearray[(int)EC_Whatever::theenum] -- that is easy to read!? HA!
But.. this is about VB... I only use it when I need to. (Inside
Word or Excel -- and that is not true VB.)
WedgeSoft
|
|
|
|
|
As some one whos worked with C++, C# and Java .. I find VB syntax to be an atrocity.
I hate reading it, I hate having to glance at it casualy as I read MSDN guides trying to get to C# code.
Curly brackets forever!
|
|
|
|
|
Yeah, it makes my eyes water
We made the buttons on the screen look so good you'll want to lick them. Steve Jobs
|
|
|
|
|
norm .net wrote: I've got to say the thing I hate most about VB is the syntax, it's ugly
That's a matter of taste, isn't it? I have worked with C family of languages since 1993 (before that mostly Basic, Assembly and Fortran), but still don't like the syntax. Yet, the syntax is pretty low on my list of priorities - C is ugly but highly portable, efficient and good for system programming. C++ is even uglier, but scales like a champ and enables high level abstraction at little cost. Java and C# are ugly, but ... ehm they are just ugly Perl is the ugliest, but does the job for some quick and dirty scripts.
Anyway, if you find a language with Pascal syntax and C++ semantics, please let me know
|
|
|
|
|
norm .net wrote: (even VB for DOS)
I played around with the DOS version a loooong time ago. I think it was the tech preview called Escher. Man, that's a blast from the past!
- S
50 cups of coffee and you know it's on!
|
|
|
|
|
|
|
Long back i migrated from GWBasic to QBasic and then to VB3, after that i droped it, coz i learned C++.
-Prakash
|
|
|
|
|
I use Visual Basic .NET but not VB6
It's part of an app we inherited.
|
|
|
|
|
I haven't used either VB6 or VB.NET for years, but for office automation VBA is often the way to go. Also, VBScript proved pretty useful for some build automation scripts.
|
|
|
|
|
Nemanja Trifunovic wrote: proved pretty useful for some build automation scripts
My build environment starts as a C++ app that presents a UI for changing version/build numbers. That app in turn starts a VBScript that runs the build process. The script does part of its work in script and part in batch files (the batch files do a couple of SourceSafe operations; 'nuff said). The script also re-invokes the original C++ app with a command line parameter to do some post-build cleanup that was just ridiculously slow in script.
Oh, what a tangled web...
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: Oh, what a tangled web...
I use VB scripts to deploy .NET web applications, it is easy and flexible. But you have to learn it first. It is also dangerous, dum people should not try it .
|
|
|
|
|
I think there is a need for a "Yes, I used VB before, but I know C/C++, so don't call me stupid" club.
|
|
|
|
|
|
...and I think there is a need for a club called "Yes, I use VB and love it! And don't care, if you call me stupid!!!"
|
|
|
|
|
They can join any "There's a dark spot in my past" club.
____________________________________
There is no proof for this sentence.
|
|
|
|
|
Back in the day, I used to use VB 6 to test my COM objects. Building a test harness in VB was so much quicker than writing the code in C++.
Now I'm working with a team who use VB.NET. Whilst I write all my code in C#, I still need to be able to read and write VB code. Even worse, I have to teach the team how to do things like ASP.NET and they want to do it in VB rather than C#.
|
|
|
|