I am a newbie...please help me..

[zach007]

Dear Experts,

I am going to start creating an application using VB 6 for Pocket PC.....what should I do at the beginning please..??..Is there any good source/URL to have a look please...????

Thanks,

Jennifer

[si_the_geek]

I'm afraid you can't use VB6.

The closest match is eVB (a free download from MS, as part of an old version of "Embedded Visual Tools"), which uses VBScript. There are a few differences in coding, and eVB is not supported on PocketPC 2003 or later.

VB.Net has the Compact Framework which allows you to write for Pocket PC devices, and I would recommend using this if you can.

[zach007]

Which version of VB.NET please..???...any version..???...

And by the way with VB.NET...I really confused between VB and VB.NET...what is the different...???...When I have to use VB and also when I have to use VB.NET...???

[zeek840]

Well what a question? I will probably get shot down by many people on this forum for this answer but...

The difference between VB and VB .NET is in it's fullest sense THE .NET FRAMEWORK. VB represents unmanaged code i.e bad coding can could cause problems with other apps that you may be running. VB.NET is 100% managed code that is to say that it is managed by the common language runtime. Dont misunderstand it still uses API but with classes from the .NET framework. No more calls to 'Kernal32Lib' unless you want to that is. VB.NET has significantly improved development time. Here are some of the benefits with VB.NET

Free Threading or any kind of threading for that matter i.e delegates(Type safe pointers, bit like c++)
Inheritance
Polymorphism

to name but a few. But as for your question about when should you use which...Well it's a matter of what your best at and whether you want to stick to what you know. I personnally prefer VB.NET, making the migration to .NET for a vb programmer would not be that difficult. A few different concepts to learn and some syntax changes and your away. Plus the fact that most of the vb syntax is still supported. But of course this is just my opinion!!

[si_the_geek]

I don't think you'll get shot down for that zeek', it sounds good to me.


One other thing to mention is that VB6 (or earlier) aren't supported anymore, so if you want your app's to be 64Bit compatible, or safe for the next version of Windows (or the one after) then .Net is the way to go.

[Shaggy Hiker]

To get back to VB versus VB.NET, it may help if you realize that VB.NET (the 2002 version, I think) was called VB7 within MS. However, VB.NET is not really an upgrade to VB6, though it was originally intended to be. I heard the story of that from the head of the VB7 team (who happens to be my brother-in-law). Eventually, they realized that they couldn't do .NET (with the runtime and managed code and all) while maintaining true backward compatibility with VB6. I guess that was a bit of a blow to Bill, but he lived with it.

So VB.NET2002 came out, and it was so-so. Then VB.NET2003 showed up, and it was much better. In both of those, there was an upgrade wizard that would do a really bad job of converting existing VB6 code into VB.NET code.

Now there is VB.NET2005, which may have an easier upgrade path from VB6. All three of the VB.NET versions (2002, 2003, and 2005) are often just called VB.NET, which can confuse people pretty well. Right now, most people who just say .NET are generally talking about 2003, though the number who are working with 2005 is increasing all the time.

If you are getting one, you will probably have to get 2005, and that's probably a good thing. The CF will come with most versions of 2005, though you will want to check, since I think somebody said it was not included with the Express Edition.

[zach007]

I don't think you'll get shot down for that zeek', it sounds good to me.

No you wont get shot down....It is very usefull for me...for the beginner...to learn about vb matters...

Thanks for your postings....I appreciated...