Archived

This topic is now archived and is closed to further replies.

daerid

Arguments for using C# over VB6

Recommended Posts

I need some. I am currently developing a CRM software application using VB6 for the company that I work for. I''ve run into a few snags using it, and would really like to convert the project over to C#. What I need is information I can use to support my statement that it would be an efficient and cost-effective move to make. I''d like to get some links / articles and such, if possible. Thanks in advance!

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Why not use VB.NET and try the upgrade/conversion wizard. VB.NET is close enough to VB that you can make the change quicker.

Share this post


Link to post
Share on other sites
Because I despise BASIC style languages with a passion, and I also have quite a bit of experience in C#

Share this post


Link to post
Share on other sites
Switching from VB6 to C# is more than just changing the language. The application built with C# run under the .NET environment. This might or might not be something you like. Under .NET there is not much difference between the programming languages, as they all have to share a specific feature-set.

Comparing the syntax and the features of VB to C# I''d always use C# (which in fact I do *g*). To me, VB code is less readable with all its END this END that stuff. Coming from a C++ backround I like those curly brackets. Depending on what you have to do in your project, C# can win extremely as it has unsafe codeblocks, which allows some kind of low-level messin''.

However, I repeat myself: switching to .NET is mor than changing the language.

Regards,

Andre

Share this post


Link to post
Share on other sites
I know all that. What I need are arguments for convincing the decision makers in my company that it''s a good idea. That is all.

I know exactly what is required.

Share this post


Link to post
Share on other sites
quote:
Original post by daerid
What I need are arguments for convincing the decision makers in my company that it''s a good idea.

tell them it will save them money.

Share this post


Link to post
Share on other sites
tell them:

- you can get the job done better and faster, due to your experience in C#.

- the use of .Net will help with maintenence issues in the future, as .Net will be is Microsoft''s primary technology push over the next 2-3 years.

- this project can serve as a proof of concept for C# .Net projects, and help other company members make the transition when the time comes (something to look at written in the company''s style and with a resident expert to ask questions).

- you can get the job done better and faster.

- did I say: you can get the job done better and faster.

Share this post


Link to post
Share on other sites
quote:
Original post by Xai
tell them:

- you can get the job done better and faster, due to your experience in C#.

- the use of .Net will help with maintenence issues in the future, as .Net will be is Microsoft''s primary technology push over the next 2-3 years.

- this project can serve as a proof of concept for C# .Net projects, and help other company members make the transition when the time comes (something to look at written in the company''s style and with a resident expert to ask questions).

- you can get the job done better and faster.

- did I say: you can get the job done better and faster.




Nice! Thanks

Share this post


Link to post
Share on other sites
I dont get it if your going fast vb.net to c#, why not just jump straight to Java. Its more stable effecient and interchangable against platforms.

no offense but Java still rules way over c# and its handicapps. Or does MS say that its enhancements.

my 2 cents well maybe 1/2 a penny

Share this post


Link to post
Share on other sites
quote:
Original post by nick5454
Java. Its more stable effecient


And you base this on...?
quote:

and interchangable against platforms.


What''s that supposed to mean, anyway?

...and that is why I believe linux must be destroyed.

Share this post


Link to post
Share on other sites
quote:
Original post by nick5454
I dont get it if your going fast vb.net to c#, why not just jump straight to Java. Its more stable effecient and interchangable against platforms.


VB.NET? Where was this mentioned?

quote:

no offense but Java still rules way over c# and its handicapps. Or does MS say that its enhancements.

my 2 cents well maybe 1/2 a penny

None taken. I just think you're wrong (my $0.02).

PS: I hate Java more than I hate BASIC languages.

[edited by - daerid on May 8, 2003 7:29:19 PM]

Share this post


Link to post
Share on other sites
on a clear day you can c for miles

quote:

why not just jump straight to Java. Its more stable effecient and interchangable against platforms.



LOL! are you on drugs?

"We are what we repeatedly do. Excellence, then, is not an act, but a habit." - Aristotle

[edited by - fusi0n on May 8, 2003 7:47:47 PM]

Share this post


Link to post
Share on other sites
just go to vb.net if it is already in vb

EDIT: i mean, come on, vb is not for games specifically(that is changing tho), its for applications. seems to me, your business wants an application, not a game.

------------------------------------------------------------
I really need to update this signature...

[edited by - demonrazor2003 on May 9, 2003 10:29:51 AM]

Share this post


Link to post
Share on other sites
How bout

It can port to Max OS X, Free BSD and soon linux w/ Mono.
Its ablitiy to easily manage code in all respects of versioning.
GAC or Global Cache Assembly can store both a 1.0 and a 1.1 or other version of the same library. Unlike the down falls of other langauges it knows what version it needs to run if you place the correct parameters in the config files.

The ablity to leverage de-centralized programming. IE you work on a good multi-thread scheme and I will program the networking Async.... Then when complete the pieces will place together like legos because each of them can see the scope of the others. No more memory leaks ...... w/ GC......

Not interupted like Java so you get the speed of C/C++ code not a scripting language. The packaging a deployment is easier noting that it looks at the dependances of the application and tells you what is missing.

Its a free compiler if you want to write in notepad and pass cmd line params. It can handle COM+ and ActiveX controls. It can make COM+ or ActiveX controls. Its easy to declare unmarshalled /unmanaged data types or parameters to exsiting dlls.

Most interfaces are Async.... Which allows for better planing to moving to a fully functional application that hits desktops. Its built-in ablities to use any stream that could be a memory,file or network......

Using Pointers without masked internal references like VB6.


There are plenty more

Share this post


Link to post
Share on other sites
This isn''t a language comparison thread (or at least it wasn''t intended to be).

I prefer to work in .NET and C# for Business Desktop Applications and Client / Server Database software.

I need to convince my superiors that developing my current application in C# is a good idea.

Share this post


Link to post
Share on other sites
quote:
Original post by nick5454
and to repeat they both suck

Thank you for that insightful contribution to this thread.

...and that is why I believe linux must be destroyed.

Share this post


Link to post
Share on other sites
Hmm, I''m not intimately familiar with C# or VB, but I assume C# does have classes. The reusability of code that comes with classes is enormous. When coupled with distributable header files, you could speed up your entire operation. Find some examples of code that was written twice, and then tell them that you could write it once, more efficiently, and store it in a central library. Moving on to new versions and new projects can be much faster, because you can reuse common code components. Also, argue that by switching to a more powerful language, you''ll gain respect from prospective employers. Personally, I really would take a company that works in C++ much more seriously than one that only does VB. Also, you could do some performance tests. Rewrite a key portion of your app in C# and test it''s performance against VB. I''ll bet my ass it''ll be faster. Basically, you need to convince him that doing it this way is going to (a) be cheap now (b) be profitable in the long run. Good luck man, and may your path be free of VB ickyness.

Share this post


Link to post
Share on other sites
quote:
Original post by Ishan
Personally, I really would take a company that works in C++ much more seriously than one that only does VB.


I''m the only programmer here, and my favorite language is definitely C++.

However, I really, really, really, really would HATE to do this project in C++. It would take me years.

C# is definitely the sensible way to go.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
quote:

Personally, I really would take a company that works in C++ much more seriously than one that only does VB. Also, you could do some performance tests. Rewrite a key portion of your app in C# and test it''s performance against VB. I''ll bet my ass it''ll be faster.
[/QUOTE]

Umm no, have you actually used VB.NET? The differences between VB6 and VB.NET are about as far as C# to C. There is absolutely no major performance differences between C# and VB.NET and they are completely interchangeable within a given solution. Welcome to .NET!

The only thing C# supports over VB.NET that I have found to be usefull is Unsafe code blocks, which doesnt apply here.

The OP doesnt like VB fair enough, but dont start this whole C# is better than VB (.NET) crap.

[QUOTE]
the use of .Net will help with maintenence issues in the future, as .Net will be is Microsoft''s primary technology push over the next 2-3 years.
[/QUOTE]
That is a damm good reason. Microsoft has risked the whole company on this .NET thing, it will prevail ...

Another good one is that when middleware companies release .NET tools, you will be able to buy one version of the software and use it accross many products (without any stupid com issues). Look at Crystal reports. You can use it C# for one project, VB.NET in the next ...

Share this post


Link to post
Share on other sites
Tell them "dude, I am the only programmer here! I would definitely use C#!" but of course, in a more polite way.
If they don''t agree, they are not trusting you.
If they don''t agree, ask them:
"Tell me the reasons why you want to use VB6 over C#?"
And they will give you a bunch of reasons, and I hope you can counter every single one of them.


And I still see "C++" and "Java" popping around...
I wonder what comes next, "use ASM"? "C"?

Share this post


Link to post
Share on other sites
.NET Winforms is quite possibly the smoothest GUI toolkit I''ve ever used. (though it''s a shame that it doesn''t have something like Swing''s layout managers)

Bear in mind, though, that I find VB''s forms interface to be more awkward, and unintuitive than win32.

I''m hip because I say "M$" instead of "MS".

Share this post


Link to post
Share on other sites