Is VB.NET reliable , robust ?

[Norman Yuan]

VB.NET is development tool to develop application in .NET. So, you wanto to
do .net development, but want to know if there is something better than
VB.NET?

Is it relaible as tool? yes, or not, depending who you ask. Comparing to use
NotePad (yes, you can use plain text NOtePad to programming for .NET, should
you choose so), it is robust. You can also choose C# as the tool. Since MS
privides VB.NET and C# in the same VS suite, the both can be considered in
the same level, in term of reliable and robust. In .NET world, there isn't
anything else better than VS(C# or VB.NET) as .NET tool.

 

[barret bonden]

Is VB.NET reliable , robust ? I'm contemplating a project on a LAN
with 50 + users hitting a MYSQL backend. I've had good success with Access
and MYSQL , but with far fewer users, of course.
This would be strictly local, no web access at all. Is there any consensus
about what I'm thinking of doing ?

 

[Scott M.]

Not quite, Norman.

VB .NET (and C# and C++ .NET) are languages, not development tools. Visual
Studio is the development tool and it is what you should compare against
other possibilities (like Notepad, etc.).

To answer the OP, absolutely VB .NET is reliable. It's as reliable as the
..NET application platform is.

When you write an application in VB .NET, you are really just writing code
to instruct the .NET Common Language Runtime to do something. It is this
CLR that gets the job done. But, the CLR doesn't actually understand VB
..NET, it understands a language called "Intermediate Language". So, your VB
..NET code gets compiled down to this Intermediate Language and that is what
the CLR looks at to figure out what it is you want to do.

In the end, the fact that you used VB .NET to write your program really
isn't that important. The question really isn't "Is VB .NET reliable and
robust?". The question is "Is the .NET Framework reliable and robust?".

The answer is certainly, yes.

-Scott M.

 

[sloan]

It is reliable.

I would (at the very least) go with VS2005 and the 2.0 framework. I would
skip VS2003 and the 1.1 framework.

VS2008 (The development environment) has an extra feature where it can
target a Framework (3.5, 3.0 or 2.0).

VB.NET is one of the ~languages used to write code for the DotNet Framework.

IT IS VERY RELIABLE.

You might want to take a look at this example:
http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!176.entry

It shows how the backend database can be layered into an application.......

I have several datastores, sql server, access, etc. My DAL returns
IDataReaders and (strong)DataSets.
Thus you can write an application that cares about the backend RDBMS is
(MYSQL in your case) but isn't married or spaghetti'ed to it.

............

 

[sloan]

You might want to see if there is a MYSQL concrete implementation for the
EnterpriseLibrary.Data

Here is a starting place:
http://justindrerup.spaces.live.com/Blog/cns!BB9D3B1D7821820F!568.entry


The EnterpriseLibrary.Data framework is an abstract layer ... there is (at
least) a Sql Server concrete implementation.
However, because it is abstract, other people are able to build custom
providers that implement the abstract library.
Aka, you can probably find a MYSQL concrete, and still use the
EnterpriseLibrary.Data framework to simplify your dataaccess needs.