Windows Mobile 2003 development in VB6

[cjmUK]

A colleague is wanting to look into developing applications to to run on
some Windows Mobile 2003 devices that we have. This is virgin territory for
us, so I'm trying to find out what tools are available to us.

I was told to look for Windows CE Toolkit for VB6; it did exist at one point
but I certainly can't find it in MSDN anywhere - though there is the
corresponding Windows CE Toolkit for C++.

Does the VB6 Toolkit still exists (under MSDN?) and if not, what other tools
would we need to get started in VB6?

There are a number of reasons to be looking at VB6, but if we were to
modernise, what would the .NET equivalent be? The Mobile Application
Development Tookit? The Windows Mobile 2004 Platform SDK?

Basically, can somebody point us in the right direction?

Thanks

Chris

[Henning]

Post by cjmUK
A colleague is wanting to look into developing applications to to run on
some Windows Mobile 2003 devices that we have. This is virgin territory for
us, so I'm trying to find out what tools are available to us.
I was told to look for Windows CE Toolkit for VB6; it did exist at one
point but I certainly can't find it in MSDN anywhere - though there is the
corresponding Windows CE Toolkit for C++.
Does the VB6 Toolkit still exists (under MSDN?) and if not, what other
tools would we need to get started in VB6?
There are a number of reasons to be looking at VB6, but if we were to
modernise, what would the .NET equivalent be? The Mobile Application
Development Tookit? The Windows Mobile 2004 Platform SDK?
Basically, can somebody point us in the right direction?
Thanks
Chris

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=81460842-47cc-4ff2-9a19-4db96e212d32

/Henning

[cjmUK]

Post by Henning
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=81460842-47cc-4ff2-9a19-4db96e212d32

Henning,

Thanks, but I'd already discovered this - it's a simple, single-form example
of how to use the toolkit - not the toolkit itself. Not having VB6 on this
machine any more I can't say more, but it clearly isn't the 'document' that
it purports to be.

Chris

[Henning]

Post by cjmUK

Post by Henning
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=81460842-47cc-4ff2-9a19-4db96e212d32

Henning,
Thanks, but I'd already discovered this - it's a simple, single-form
example of how to use the toolkit - not the toolkit itself. Not having VB6
on this machine any more I can't say more, but it clearly isn't the
'document' that it purports to be.
Chris

Sorry, posted the link without checking :(

Seem that eMbedded Visual Basic has gone the same way as VB6, the only
alternative beeing the "new" VB. You can't get it from MS any moore. MS's
ways are mysterious, on a minimal target you have to drag along a
'compacted' version of the Flamework. Taking much moore space than any app.

/Henning

[Ginny Caughey]

Chris,

The modern tool for mobile development in VB would be Visual Studio and
VB.NET.
--
Ginny Caughey
Device Application Development MVP

Post by cjmUK
A colleague is wanting to look into developing applications to to run on
some Windows Mobile 2003 devices that we have. This is virgin territory
for us, so I'm trying to find out what tools are available to us.
I was told to look for Windows CE Toolkit for VB6; it did exist at one
point but I certainly can't find it in MSDN anywhere - though there is the
corresponding Windows CE Toolkit for C++.
Does the VB6 Toolkit still exists (under MSDN?) and if not, what other
tools would we need to get started in VB6?
There are a number of reasons to be looking at VB6, but if we were to
modernise, what would the .NET equivalent be? The Mobile Application
Development Tookit? The Windows Mobile 2004 Platform SDK?
Basically, can somebody point us in the right direction?
Thanks
Chris

[cjmUK]

Post by Ginny Caughey
Chris,
The modern tool for mobile development in VB would be Visual Studio and
VB.NET.

I don't see any project templates in VS2008 - surely there is an additional
toolkit/SDK to add mobile device support?

CJM

[Tom Shelton]

Post by cjmUK

Post by Ginny Caughey
Chris,
The modern tool for mobile development in VB would be Visual Studio and
VB.NET.

I don't see any project templates in VS2008 - surely there is an additional
toolkit/SDK to add mobile device support?
CJM

VS2008 Pro, it's called a smart device project.

[CY]

Hmm, this is sorta .not link, but maybe better age 2005...

http://www.danielmoth.com/Blog/2005/11/getting-started-with-net-compact.html

dunno VB6 directly to mobile but can this contraption be wrapped for
vb6, maybe... did something like that with jni to go java-fortran,
ehhm, well, got a bit c too, but it worked.... eventually.

//CY

[DickGrier]

You need the Pro Edition or higher, and you have to install the appropriate
(free) SDK. See:
http://msdn.microsoft.com/en-us/windowsmobile/default.aspx).

Dick

[DickGrier]

Hi,

This toolkit was replaced by eVB 3.0. eVB support ended with PocketPC 2002.
All Microsoft development has moved to Visual Studio .NET (and, is by far --
IMO-- superior to the earlier products). The current version of Visual
Studio 2008 (an 2010, soon) required the Professional Edition or higher for
mobile development. You could use the Standard Edition or higher of VS 2003
and VS 2005.

There are a couple of other, lower cost, alternatives. One is NSBasic (see:
http://www.nsbasic.com/ce/).

Dick

[Abhishek]

You need eVB. u can still target upto WM 5.0 using eVB, but you will need to
mod the eVB and install eVB runtimes on the target device.

here is the 'hack'
http://www.omnisoft.com/articles/spevb/default.asp



"DickGrier" <***@msn.com> wrote in message news:***@TK2MSFTNGP04.phx.gbl...
| Hi,
|
| This toolkit was replaced by eVB 3.0. eVB support ended with PocketPC
2002.
| All Microsoft development has moved to Visual Studio .NET (and, is by
far --
| IMO-- superior to the earlier products). The current version of Visual
| Studio 2008 (an 2010, soon) required the Professional Edition or higher
for
| mobile development. You could use the Standard Edition or higher of VS
2003
| and VS 2005.
|
| There are a couple of other, lower cost, alternatives. One is NSBasic
(see:
| http://www.nsbasic.com/ce/).
|
| Dick
|
| --
| Richard Grier, Consultant, Hard & Software 12962 West Louisiana Avenue
| Lakewood, CO 80228 303-986-2179 (voice) Homepage: www.hardandsoftware.net
| Author of Visual Basic Programmer's Guide to Serial Communications, 4th
| Edition ISBN 1-890422-28-2 (391 pages) published July 2004, Revised July
| 2006.
|

[Nobody]

If you want to compete and use less resources, try Embedded Linux:

http://en.wikipedia.org/wiki/Embedded_Linux

[Paul G. Tobey [eMVP]]

And all you have to do is build an Embedded Linux OS for your Pocket PC 2003
and get it loaded, before you even write your application. No problem!

Paul T.

Post by Nobody
http://en.wikipedia.org/wiki/Embedded_Linux
.

[Richard Mueller [MVP]]

Post by cjmUK
A colleague is wanting to look into developing applications to to run on
some Windows Mobile 2003 devices that we have. This is virgin territory for
us, so I'm trying to find out what tools are available to us.
I was told to look for Windows CE Toolkit for VB6; it did exist at one
point but I certainly can't find it in MSDN anywhere - though there is the
corresponding Windows CE Toolkit for C++.
Does the VB6 Toolkit still exists (under MSDN?) and if not, what other
tools would we need to get started in VB6?
There are a number of reasons to be looking at VB6, but if we were to
modernise, what would the .NET equivalent be? The Mobile Application
Development Tookit? The Windows Mobile 2004 Platform SDK?
Basically, can somebody point us in the right direction?
Thanks
Chris

The classic vb solution for mobile devices was embedded vb (eVB). This is no
longer supported. Windows Mobile (the new OS on mobile devices) no longer
includes the vb runtime. You used to be able to install the runtime
yourself, but other things are no longer supported. Your only option now is
.NET, which is completely different. There is no wizard for converting eVB
code to VB.NET.

[cjmUK]

Thanks for all the responses.

I've spoken to my colleague and basically ushered him away from VB6. We have
certain systems we interact with that are vb6-era technology, but this is
not one of those cases. So the only reason to stick with VB6 is because
these guys are familiar with it - which in this scenario is not a good
enough excuse.

We have enough copies of VS2008, so .NET is clearly the way to go - so
either they will have to commission me to do the work or they will have to
modernise their skill-set.

Thanks

Chris

[Karl E. Peterson]

So the only reason to stick with VB6 is because [the programmers] are
familiar with it - which in this scenario is not a good enough excuse.

LOL!

We have enough copies of VS2008, so .NET is clearly the way to go - so either
they will have to commission me to do the work or they will have to modernise
their skill-set.

Spoken like a true consultant...