I just installed the DK on my system, and guess what, All samples are in
C#. Oh well, Too bad for the poor VB Orphans.

Curt wrote:

Curt, I saw your post about UniObjects in the U2 forum. I'm wondering
why language-specific syntax is so important. The properties and
methods should be the same regardless of language. I'm guessing you
just want some plug n play code. At the risk of making it tough for
you, I think you'll learn the library better you go through the mental
effort of extracting what you need from the C# code and writing the
code yourself in VB.NET.

Personally I use mv.NET which has great examples in both languages.
I'll be happy to help with this.

In any case:
http://www.google.com/search?q=%22convert+C%23+to+VB%22

Good luck
Tony
TG@ removethisNebula-RnD.com

I can translate the samples just fine. The problem is, the Imports do
not work in VB, even though the Usings are working just fine in C#

2005 is so frustrating. I have years in vb6 and I'm stuck in my ways. I
can write stuf in VB6 in minutes, the same thing in 2005 takes Days do
to the 'minor' changes they made. IMHO MS has distroyed VB. They took C
and wrapped VB syntax around it.





In article <mts4c25rvq5leipnp6n4ohdrt3has3jhfi (AT) 4ax (DOT) com>, g6q3x9lu53001
@sneakemail.com.invalid says...

Thanks Anyway, I did some Googling and found what I needed.

Curt wrote:

A word of advice with regard to migrating to vb.net...

Your first mistake will be in comparing vb.net to vb6 - your best bet is to
try and forget most of what you are used to with vb6.

It's more of a relearn than a migration, this take time - you have to learn
the basics of the dotnot framework as well.

You will find, though that you can write code as quickly using vb.net as you
did in vb6 (quicker in some cases) and the resulting code is more manageable
as well.

Good luck.

Regards
Simon

--
================================
Simon Verona
Dealer Management Service Ltd
Stewart House
Centurion Business Park
Julian Way
Sheffield
S9 1GD

Tel: 0870 080 2300
Fax: 0870 735 0011

"Curt" <junkmail (AT) junkmail (DOT) com> wrote

"Simon Verona" <nomail (AT) nomail (DOT) zzz> wrote

it. It's worth it but it's hard to convince yourself while you are
struggling up the steep mountain. Maybe it's because I'm a dinosaur but I
was at least six months before I could code without the book open on the
desk. Two books really - VB.Net and VS. There are two books that worked for
me . One is paper and the other is an e-book.

Visual Basic 2005 Programmer's Reference, Rod Stephens, Wrox. This is a
thousand pages. It starts by teaching the IDE then swings into VB.

If you download VB 2005 Express - and it is well worth doing - you get
an e-book with it that is pretty good. To get the best from it you need to
have two monitors so the book is always open while you are struggling with
VB. In my case a lot of the struggle was the so-called best practice of
using very descriptive names for methods and every thing else. Yes, they
help when you read them but they certainly are easy to misspell.

An unpopular opinion that seems to be inching its way into my mind is
that when you know what you are doing with dot net then you can forget about
Pick. For new development that is - if you have to support legacy code
that's another story.

BobJ

Curt wrote:
Hi Curt,

If you get hold of the Universe Client CD-ROM, version 10.1b (being the
current version),
you will find the VB.NET sample directories have been populated with
sample code.

If you are unable to get the CD-ROM, post an e-mail address and I will
zip it all up
and send to you.

Do not use my e-mail address listed here, it is very dead...

Cheers, Barry

Curt wrote:
Hi Curt,

Barry again,

I found the following free tool invaluable when using dot.net

http://www.aisto.com/roeder/dotnet/

Get reflector for dot.net, you can load C# code and then switch to VB
mode, reflector
will do the conversion for you.

This is just the tip of what reflector can do. You can dig into the MS
dot.net code and
see how things work (or should be done), plus many other tools.

I do not write dot.net code without it.

Enjoy, Barry

This is becoming a more valuable dot net help group than the dot net groups.
Reflector is awesome! Thanks.
BobJ

<bgraetz (AT) bigpond (DOT) net.au> wrote