No Smart Device Application template?

[Roger Strong]

Hi!
I need to create a VB.NET application for a Pocket PC. I've installed
VB.Net, the .NET Compact Framework and the Microsoft Pocket PC 2003 SDK.

Still, there is no "Smart Device Application" template under New
Project/Visual Basic Projects.

I've tried deinstalling and reinstalling everything - still no template.

What am I doing wrong?

[Cor Ligthert]

Roger,

Did you know that there is an active newsgroup
microsoft.public.dotnet.framework.compactframework .

Not that you are not welcome here, however there you have probably a change
on more answers.

I hope this helps?

Cor

"Roger Strong"

Hi!
I need to create a VB.NET application for a Pocket PC. I've installed
VB.Net, the .NET Compact Framework and the Microsoft Pocket PC 2003 SDK.

Still, there is no "Smart Device Application" template under New
Project/Visual Basic Projects.

I've tried deinstalling and reinstalling everything - still no template.

What am I doing wrong?

[Ken Tucker [MVP]]

Hi,

You do have vs.net 2003 pro or higher.

Ken
---------------------
"Roger Strong" <rs*****@yetmans.mb.ca> wrote in message
news:eS**************@TK2MSFTNGP12.phx.gbl...
Hi!
I need to create a VB.NET application for a Pocket PC. I've installed
VB.Net, the .NET Compact Framework and the Microsoft Pocket PC 2003 SDK.

Still, there is no "Smart Device Application" template under New
Project/Visual Basic Projects.

I've tried deinstalling and reinstalling everything - still no template.

What am I doing wrong?

[Herfried K. Wagner [MVP]]

"Roger Strong" <rs*****@yetmans.mb.ca> schrieb:

I need to create a VB.NET application for a Pocket PC. I've installed
VB.Net, the .NET Compact Framework and the Microsoft Pocket PC 2003 SDK.

Still, there is no "Smart Device Application" template under New
Project/Visual Basic Projects.

I've tried deinstalling and reinstalling everything - still no template.

The templates are only included in VS.NET Professional or "better":

<URL:http://msdn.microsoft.com/vbasic/howtobuy/choosing.aspx>
<URL:http://msdn.microsoft.com/vstudio/howtobuy/choosing.aspx>

--
Herfried K. Wagner [MVP]
<URL:http://dotnet.mvps.org/>

[Cor Ligthert]

Herfried,

The templates are only included in VS.NET Professional or "better":

You have you drivers license now.

A car with leather seats is not "better" than one with normal ones, it is a
matter of taste however some find leather seats more comfortable. However it
does not make the car direct "better".

I am glad you showed me that sample from the car this week, now I could show
it too you in your way.

:-)))

Cor

[WALDO]

Cor Ligthert,

A car with leather seats is not "better" than one with normal ones

Yes it is. ;)

Sometimes the greatest solutions come from the simplest logic.
Being told "No" is merely the incentive to do it anyway.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Dick Grier]

Hi,

You need Visual Studio 2003 Professional Edition or higher. Compact
Framework development is not supported under the single-language versions.

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.

[Roger Strong]

"Dick Grier" wrote:

You need Visual Studio 2003 Professional Edition or higher. Compact
Framework development is not supported under the single-language versions.

There are plenty of programming examples on the M$ site covering just Visual
Basic.NET Pocket PC development. They don't give any hint that the product
"Visual Basic.NET" doesn't actually work with them.

The Microsoft site is full of references where you buy VB.NET (done!),
download and install the .NET Compact Framework (done!), and you're ready to
go. Like:

"Moving from eMbedded Visual Basic to Visual Basic .NET"
http://msdn.microsoft.com/library/de...asp?frame=true

Visual Studio.NET is mentioned on other pages - but it's made clear
elsewhere that VB.NET is a Visual Studio.NET language - it's the Visual
Studio programming environment, with just with the one language.

I can't help but feel misled and ripped off.

[Roger Strong]

"Dick Grier" wrote:

You need Visual Studio 2003 Professional Edition or higher. Compact
Framework development is not supported under the single-language versions.

There are plenty of programming examples on the M$ site covering just Visual
Basic.NET Pocket PC development. They don't give any hint that the product
"Visual Basic.NET" doesn't actually work with them.

The Microsoft site is full of references where you buy VB.NET (done!),
download and install the .NET Compact Framework (done!), and you're ready to
go. Like:

"Moving from eMbedded Visual Basic to Visual Basic .NET"
http://msdn.microsoft.com/library/de...asp?frame=true

Visual Studio.NET is mentioned on other pages - but it's made clear
elsewhere that VB.NET is a Visual Studio.NET language - it's the Visual
Studio programming environment, with just with the one language.

I can't help but feel misled and ripped off.

[Dick Grier]

Hi,

Sorry.

I too think some of the information is less than helpful. Naturally, as a
(mostly) VB programmer, I'd like you to be able to do what you want to do.
Microsoft decided that Compact Framework development was something that
demanded something more than the minimum investment in tools. This seems to
have changed a little bit in Visual Studio 2005 (Whidbey).

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.

[Dick Grier]

Hi,

Sorry.

I too think some of the information is less than helpful. Naturally, as a
(mostly) VB programmer, I'd like you to be able to do what you want to do.
Microsoft decided that Compact Framework development was something that
demanded something more than the minimum investment in tools. This seems to
have changed a little bit in Visual Studio 2005 (Whidbey).

Dick

--
Richard Grier (Microsoft Visual Basic MVP)

See www.hardandsoftware.net for contact information.

Author of Visual Basic Programmer's Guide to Serial Communications, 4th
Edition ISBN 1-890422-28-2 (391 pages) published July 2004. See
www.mabry.com/vbpgser4 to order.

[Roger Strong]

"Dick Grier" <di**************@msn.com> wrote

Microsoft decided that Compact Framework development was something that
demanded something more than the minimum investment in tools.

Right. But the .NET Compact Framework Developer extensions are freely
downloadable on their site - something mentioned in their VB.Net examples.
There's no disclaimer stating "Visual Basic.NET examples do not work with
the product called Visual Basic.NET", or "Where we tell you to upgrade from
Embedded Visual Basic to Visual Basic.NET, we really mean some other
product - no, seriously."

Microsoft isn't being "less than helpful" - they're being very dishonest.

[Roger Strong]

"Dick Grier" <di**************@msn.com> wrote

Microsoft decided that Compact Framework development was something that
demanded something more than the minimum investment in tools.

Right. But the .NET Compact Framework Developer extensions are freely
downloadable on their site - something mentioned in their VB.Net examples.
There's no disclaimer stating "Visual Basic.NET examples do not work with
the product called Visual Basic.NET", or "Where we tell you to upgrade from
Embedded Visual Basic to Visual Basic.NET, we really mean some other
product - no, seriously."

Microsoft isn't being "less than helpful" - they're being very dishonest.

[Ken Halter]

Roger Strong wrote:

Right. But the .NET Compact Framework Developer extensions are freely
downloadable on their site - something mentioned in their VB.Net examples.
There's no disclaimer stating "Visual Basic.NET examples do not work with
the product called Visual Basic.NET", or "Where we tell you to upgrade from
Embedded Visual Basic to Visual Basic.NET, we really mean some other
product - no, seriously."

Microsoft isn't being "less than helpful" - they're being very dishonest.

To be fair though, the download page for that SDK says:

"5. Install Visual Studio .NET 2003
In order to develop applications in C# or Visual Basic .NET for Pocket
PC 2003, you must install Visual Studio .NET 2003 before installing the
SDK."

SDK for Windows Mobile 2003-based Pocket PCs
http://www.microsoft.com/downloads/d...displaylang=en

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..

[Ken Halter]

Roger Strong wrote:

Right. But the .NET Compact Framework Developer extensions are freely
downloadable on their site - something mentioned in their VB.Net examples.
There's no disclaimer stating "Visual Basic.NET examples do not work with
the product called Visual Basic.NET", or "Where we tell you to upgrade from
Embedded Visual Basic to Visual Basic.NET, we really mean some other
product - no, seriously."

Microsoft isn't being "less than helpful" - they're being very dishonest.

To be fair though, the download page for that SDK says:

"5. Install Visual Studio .NET 2003
In order to develop applications in C# or Visual Basic .NET for Pocket
PC 2003, you must install Visual Studio .NET 2003 before installing the
SDK."

SDK for Windows Mobile 2003-based Pocket PCs
http://www.microsoft.com/downloads/d...displaylang=en

--
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep all discussions in the groups..

[Roger Strong]

"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote

To be fair though, the download page for that SDK says:

"5. Install Visual Studio .NET 2003
In order to develop applications in C# or Visual Basic .NET for Pocket
PC 2003, you must install Visual Studio .NET 2003 before installing the
SDK."

To be fair though, step five above simply refers to the proper installation
order. In many places VB.NET is described a Visual Studio.NET language -
It's the Visual Studio programming environment, with just with the one
language. I assumed step 5 refered to "The Visual Studio language you are
using."

This is a fair assumption after reading many programming examples on the
Microsoft site that refer only to VB.NET, and after visiting the download
page from another page which *explicitly* states that VB.NET *DOES* work
with the compact framework:

http://msdn.microsoft.com/library/de...asp?frame=true

Moving from eMbedded Visual Basic to Visual Basic .NET
Microsoft Corporation

August 2003

Applies to:
Microsoft® Windows® Pocket PC 2002
Microsoft® eMbedded Visual Basic®
Microsoft® .NET Framework
* Microsoft® Visual Basic® .NET *
Microsoft® .NET Compact Framework
Microsoft® Visual Studio® .NET

Summary: Learn how to move Microsoft Windows Pocket PC 2002 software
development from Microsoft eMbedded Visual Basic to the Microsoft .NET
Framework and ***Visual Basic .NET***. The release of the .NET Compact
Framework enables mobile application development to make use of the same
tools and languages used in server and desktop application development. (36
printed pages)

[Roger Strong]

"Ken Halter" <Ken_Halter@Use_Sparingly_Hotmail.com> wrote

To be fair though, the download page for that SDK says:

"5. Install Visual Studio .NET 2003
In order to develop applications in C# or Visual Basic .NET for Pocket
PC 2003, you must install Visual Studio .NET 2003 before installing the
SDK."

To be fair though, step five above simply refers to the proper installation
order. In many places VB.NET is described a Visual Studio.NET language -
It's the Visual Studio programming environment, with just with the one
language. I assumed step 5 refered to "The Visual Studio language you are
using."

This is a fair assumption after reading many programming examples on the
Microsoft site that refer only to VB.NET, and after visiting the download
page from another page which *explicitly* states that VB.NET *DOES* work
with the compact framework:

http://msdn.microsoft.com/library/de...asp?frame=true

Moving from eMbedded Visual Basic to Visual Basic .NET
Microsoft Corporation

August 2003

Applies to:
Microsoft® Windows® Pocket PC 2002
Microsoft® eMbedded Visual Basic®
Microsoft® .NET Framework
* Microsoft® Visual Basic® .NET *
Microsoft® .NET Compact Framework
Microsoft® Visual Studio® .NET

Summary: Learn how to move Microsoft Windows Pocket PC 2002 software
development from Microsoft eMbedded Visual Basic to the Microsoft .NET
Framework and ***Visual Basic .NET***. The release of the .NET Compact
Framework enables mobile application development to make use of the same
tools and languages used in server and desktop application development. (36
printed pages)