VB.Net advice needed

[Andy.I]

Hi

I've just finished a collegue cource in beginning Vb.net programmeing, and
was supposed to take an advanced cource in VB.net next semester learning
more abour object oriented programming. But this cource is terminated.
By options now is to either take a cource in C# or a cource in ASP.Net with
vb.net as language of choice. What would be most benefitial? The C# is
targeted on developers with Java/C++ experience, and the ASP.Net on vb.net
prorgrammers.
Are there any drawbacks with ASP.Net? I realise it is not the same as
Windows development, but I will learn mote VB, and for OOP programming I
have some good learning books.
Please advice

/A.

 

[niklas.arbin]

It may not look like it at first, but VB.Net and C# are very very
similar. If you know vb it's very easy to learn c# and vice versa....

As a developer you need both courses. Do you really have to choose
between them?

/Niklas

Andy.I skrev:

 

[Andy.I]

You mean between the C# and Asp.net? This semester I have to choose.
The problem is that the instructor says that the C# cource could be a bit
much since I have no OOP experience (such as Java or C++).
So if ASP.net can be useful i should take this, and maybe OOP with VB.net
next semester instead in paralell with the C# cource?

/A.

 

[niklas.arbin]

VB.Net is OOP too.

The earlier you start thinking "object oriented" the better. Asp.net is
also entirely based on OOP.

To put it like this... It's not optimal to mix languages during your
education, but it can be done. You should not learn asp.net before you
understand OOP, it will give you much more when you understand those
concepts(But who am I to say you won't learn oop during the asp.net
course) .

A course you have studied in VB you shouldn't study in c# if you want
to learn something.

c# oop and vb.net oop is exactly the same.

/Niklas

Andy.I skrev:

 

[Martin Milan]

Hi

I've just finished a collegue cource in beginning Vb.net programmeing,
and was supposed to take an advanced cource in VB.net next semester
learning more abour object oriented programming. But this cource is
terminated. By options now is to either take a cource in C# or a
cource in ASP.Net with vb.net as language of choice. What would be
most benefitial? The C# is targeted on developers with Java/C++
experience, and the ASP.Net on vb.net prorgrammers.
Are there any drawbacks with ASP.Net? I realise it is not the same as
Windows development, but I will learn mote VB, and for OOP programming
I have some good learning books.
Please advice

Hi Andy,

Personally, I would advise you to look at C#. You're new to programming,
and learning a "semi-colon" language would be a good experience for you.
As for OOP, whether you work in C# or VB.Net it's all the same idea -
same concepts.

Don't misunderstand me though, there's no real reason to go in one
direction over the other - VB would be perfectly useful for you as
well...

Martin.

 

[Martin Milan]

You mean between the C# and Asp.net? This semester I have to choose.
The problem is that the instructor says that the C# cource could be a
bit much since I have no OOP experience (such as Java or C++).

Ridiculous!

VB.Net fully supports OOP, and it's just as necessary to use it in well
designed VB.Net programs as it is in C#. It's the task at hand that
would make you start thinking about OOP, not the language you're using.

Your instructor sounds like one of the "VB is a toy language" brigade.
In VB6 he might have had an argument, but in VB.Net he's just wrong.

So if ASP.net can be useful i should take this, and maybe OOP with
VB.net next semester instead in paralell with the C# cource?

To be perfectly frank with you, I think what you really need to do is
have a look at a couple of tutorials (google for 'em) on VB.Net and C#,
and look at how each uses classes. I think what you see there will
reassure you...

(To be even more frank, you might want to do a few tutorials before
going into the course. It's really not an unreasonable expectation for
you to have the basics down in either language in a weekend...)

Martin.

 

[Bruce W. Darby]

Andy,

Since you are pursuing an education in VB.Net, the logical step would be to
move further in that direction by taking the ASP.Net as it will give you a
better grounding in how to move from Windows-based programming to ASP
programming in Visual Basic. IMHO, this will make you a more valuable VB
programmer to a prospective employer by not locking you into a narrow aspect
of the VB language. This will also give YOU more options when you finish
school. Of course, this is just my own personal opinion and is subject to
repudiation and ridicule at any moment without prior notice. Gotta LOVE
those disclaimers. LOL Good luck in your decision, whichever direction you
choose.

 

[RobinS]

For what it's worth, I agree with Bruce. You'll learn some VB.Net
that you can then turn around and leverage into VB Winform apps.
And there's a lot of ASP jobs out there.

Robin S.
----------------------

 

[Master Programmer]

Andy

I would just learn C#. Its pretty common knowledge that VB.NET is very
likely to be discontinued in the next release of Visual Studio because
of the lack of interest in it. I can confirm this as I have a friend
at Microsoft that mentioned it to me.

Good luck with the course.
Steve Ray Irwin

 

[code_munger]

I heard that as well, plenty of posts in this newgroup as well. It
would'nt surprise me.

Peter

 

[Andy.I]

If Vb.net is to be discontinued, why is it so information regarding Vb 9
(Orcas) on the VB site at MSDN?

 

[Tim Patrick]

You may have heard it, but it's not true. "Steve Ray Irwin" has heard no
such thing from his "friend." As proved by other posts, he just doesn't like
VB.NET, and would like to see it go away. That's all. I have already done
some early testing with the next version of Visual Basic (cool new features
in it, by the way), so it's pretty clear to me that it exists.

 

[RobinS]

Because it's not going to be discontinued. That guy is
just trolling. He's bitter over his inability to learn
new concepts and apply them effectively.

Robin S.
-----------------------------------------

 

[Master Programmer]

Yes, thats the replacement for the VB.NET language. Its still going to
be called VB (like last time) but there are major syntax and language
changes planned..... making the current language obsolete.

The Grand Master

 

[Tim Patrick]

There are no syntax features slated for deprecation in the Orcas release.
There are some language changes planned, but they are all additions to existing
VB2005 syntax. If you choose not to use the new features, you won't even
notice the difference in syntax.

 

[RobinS]

Thanks for posting that. I was wondering about Orcas, and its
impact on the projects I'm working on.

Robin S.
-----------------------------

 

[Tim Patrick]

I should qualify what I said a little. There will be no deprecated language
features in VB-Orcas, but there haven't been any deprecated language features
in any of the VB releases since VB.NET 2002 came out. It's a pretty safe
statement to make. Microsoft made their cut of language features when they
jumped to .NET. For instance, they removed GoSub/Return at that time. Microsoft
has no reason to remove language grammar that they worked hard to included
in .NET. (Personally, I would like to see the While/End While statement removed
from the language, since it is fully replaced by Do/Loop.)

However, there may be "breaking changes" in the .NET Framework classes in
the Orcas release timeframe. Microsoft periodically modifies specific class
features from release to release, and some of these changes can impact specific
programs. You can find lists of these changes on the MSDN web site (http://msdn.microsoft.com/netframework/programming/breakingchanges/).
But they have nothing to do with the VB language. These breaking changes
impact both VB and C# equally.

 

[RobinS]

Thanks for the clarification. I'll check out the link.

But they have nothing to do with the VB language. These breaking
changes impact both VB and C# equally.

It's good to see that Microsoft is an Equal-Opportunity Annoyer.

Robin S.
----------------------------------------

 

[RobinS]

Interestingly enough, that link came up and said it was no longer
available, and I was being redirected to this one

http://msdn2.microsoft.com/en-us/netframework/aa570326.aspx

which is "Breaking Changes in .Net Framework 2.0." So it's
actually diffs between 1.0/1.1 and 2.0. Maybe they will update
it when it gets closer to releasing Orcas?

Robin S.
-----------------------------

 

[Cor Ligthert [MVP]]

Tim,

I have the idea that a breaking change is for the VB team one of the very
important things not to let that happen. I think that they will build direct
an upgrade wizard if there is the slightlest change for that.

Just my gues

Cor