How to make application work on Symbol MC3000?

Z

zangloma

Has anyone had any experience in programming for Symbol MC3000 which
has Windows CE
4.2 in VS .NET or 2005?
I tried everything I could find on the net, but had no luck in making
the simpliest application work. Best I could get is the "not a valid
Windows CE application" error.
It seems to me that this device needs more than a standard PDAs.
Because I installed
Compact Framework 1.0 and nothing changes.
I would apreciate if someone would tell me everything I need to do to
make application
written in C# work on a Symbol MC3000.

Best regards,
Zarko Stanisavljevic
 
P

Paul G. Tobey [eMVP]

If it's generic Windows CE.NET 4.2, you may have problems targeting it using
VS2005. You should, if Symbol supports it, be able to use VS.NET 2003 and
..NET Compact Framework 1.0 on the device, but this is really a question for
Symbol, as we don't know exactly what's in their OS image (Windows CE is
*not* a single operating system, but a set of components from which the OEM
can choose a set of things they want to have).

Paul T.
 
D

DJMatty

Yeah, the older symbol devices had their own SDK so that you could use
the barcode readers etc. Not played with an MC3000 but I would have
thought that it would be similar, almost all the industrial device
manufacturers that make devices that are Windows CE 4.x or 5.0 that I
have come across have had their own SDK...

Have you tried their developer web site?

Matt
 
D

Dexlex

CE4.2 => VS2003
CE5.0 => VS2005

This is the supported way, but CE4.2 with VS2005 might also work, as it does
with me.

However, the MC3000 series can be to upgraded to WinCE5.0 - contact your
Symbol dealer.

"not a valid Windows CE application" - did you set up a Smart Device
Application (not possible with VS2005 Express)?

Dex
 
Z

zangloma

Thanks guys for all your answers.
But my problem remains. All the things that you mantioned I already
did.
I am using Symbol Mobility Developers Kit v1.3 for .NET and it's
working fine.
It is used to work with the barcode reader, and it adds up barcode
reader in the Toolbox
in VS and also bunch of dll files on the device.
Symbol does have a Symbol SDK, but it only works in combination with
embedded
Visual C++ 4.0, and I would definetily like to avoid switching to
another language. But
that SDK won't install wirhout eVC.
Here is what the Symbol tech support wrote to me:
"Hello Zarko,

Please see the install requirements for the Symbol Mobility
Developer
Kit v1.3 for .NET -

http://devzone.symbol.com/content.cfm?item_id=96DC2AFA-650B-4693-BB35EF8
C47DD8897

Also make sure you have installed DCP V1.1 for the MC3000 from the
devzone -

http://devzone.symbol.com/content.cfm?item_id=A6DE099D-0FC5-4E82-BA28A31
A1EB89153



Kind regards,

Tom Stejskal

L1 CIC Technical Helpdesk
EMEA Customer Operations
Global Services Division
Symbol Technologies, Inc.
www.symbol.com

www.symbol.com/services/contactsupport for your local support number

(e-mail address removed)

Symbol. The Enterprise Mobility Company. (TM)"

So I did that and again nothing. The DCP v1.1 is used for file transfer
between the PC
and the device.
Only interesting thing that I saw was when I visited the second link
that they gave me.
There is a following sentence:
"A DCP can NOT be used to create applications. To create applications
for the MC 3000, download and install theSMDK for eVC4 and the
Microsoft Pocket PC 2003 SDK."
And the part that I find interesting is about Pocket PC 2003 SDK.
Could that be the solution for my problem?
I will give it a shot. And if anyone thinks of something I could try do
tell.
I 'm sure that it has to work with VS.

Best regards,
Zarko Stanisavljevic
 
D

Dexlex

eMbedded Visual C++ is definitely not needed for SMDK V1.3 for .Net, only
for SMDK V1.4 for eVC.

For simple applications you don't need any Symbol SDK at all. The DCP is
only needed to create HEX files for download using the IPL mode of the PDA
for deployment.

Just create a small "Hello World" program (Smart Device Application for .Net
1.0), download it to the device (either by using the debugger or by copying
it to the file system on the device with ActiveSync) and start it - it
should work.

Dex
 
Z

zangloma

I know it should, but it won't.
I believe that the simpliest application ("Hello World"), should work
if I only
deploy Compact Framework 1.0 and the application it self.
But I get ""SmartDeviceApplication1" is not a valid Windows CE
application" error.
Do you maybe know what could be the reason?
 
Z

zangloma

I also just tried Pocket PC 2003 SDK, but it is used with
eVC, too.
I really don't no what to do anymore. I have application that
should without a problems, but it just won't.
 
Z

zangloma

Here is what I just noticed.
When I download application ("Hello World") from my MC3000,
which came with the device and which works on a device, and
try to run it on my PC I get ""Hello.exe" is not a valid Win32
application" which is opposite from the error I get when I run
my application on the device. Also my application works fine
on the PC.
Can it be posible that the VS doesn't create
SmartDeviceApplication correctly? And if it can, then
what should I do about it?

Best regards,
Zarko Stanisavljevic
 
P

Paul G. Tobey [eMVP]

Only if you told it to do the wrong thing. I suppose that, if you want to
spend the day installing things, you could uninstall VS and reinstall it and
see if that makes any difference but I think that it's very unlikely, if you
did everything correctly, that this would happen. You're just running the
default code created by the new project wizard, right? You selected Other
Languages | Visual C# | Smart Device | Windows Mobile 5.0 Pocket PC and then
selected Device Application (1.0) from the list of project types?

Paul T.
 
Z

zangloma

I must sadly say yes. I did nothing wrong and just couldn't run it.
I decided to switch to embedded Visual C++ 4.0 for my current needs,
and everything works fine, although proggraming is much more dificult.
I just hope that I won't have theese kind of problems when I start to
write
applications in VS2005 for devices that have Windows CE 5.0.
Thanks again for all your trouble.

Best regards,
Zarko Stanisavljevic
 
C

CenGenTech

Zarko,

I had a similar problem when I first started developing for the MC3000.
My applications would work on a Symbol MC9000 and Dell Axim running
Pocket PC but would not run on the MC3000. I contacted Symbol and got
their SDK and it solved the problem. I'm using the Symbol Mobility
Developer Kit for .Net v1.2. Symbol says the SDK is only for the
MC9000 series devices running Pocket PC but one of their Engineers told
me to use it with the MC3000 as well and it did the trick.

When you build your CAB file, which files are you installing on the
device? If the CAB file is built correctly it should be something like
AppName_PPC.ARMV4.CAB and AppName_PPC.ARMV4.DAT. The CAB files will
install the application on the device so it will run properly.

If you have active sync and the device hooked directly to your
development machine, you could also run in debug mode on the device
itself. That would be your best bet because it would deploy everything
to the device for you.

Regards,
Johnny
 
P

Paul G. Tobey [eMVP]

Those are not comparable things. You can't say that, because an eVC program
works, there's something wrong with Visual Studio or the .NET CF. I think
that the problem is still you, with a small chance that it's a corrupt
install of Visual Studio or the SDK. Hundreds or, maybe, thousands of
people are doing this successfully, so it's not a general problem.

Paul T.
 
Z

zangloma

What SDK are you refering to?
I tried to instal Platform SDK for MC3000c42 that I got from Symbol's
site, but it won't start the installation without eVC. And when I'm
deploying
I am doing it from VS, so it transfers everything by it self.
Could you tell me exactly what do you have on your PC, and on your
device. And the exact procedure for creating the empty form that will
work.
Please.

Zarko
 
Z

zangloma

Previous reply was ment for Johnny. :)
And I also don't think that the problem is in VS, but the fact is that
I do everything that needs to be done, and I am pretty sure that
the application would work on any other device, but it just doesn't
work on MC3000.
I hope that Johnny can help me solve this problem, because
working in eVC is not easy at all.

Zarko said:
What SDK are you refering to?
I tried to instal Platform SDK for MC3000c42 that I got from Symbol's
site, but it won't start the installation without eVC. And when I'm
deploying
I am doing it from VS, so it transfers everything by it self.
Could you tell me exactly what do you have on your PC, and on your
device. And the exact procedure for creating the empty form that will
work.
Please.

Zarko
Zarko,

I had a similar problem when I first started developing for the MC3000.
My applications would work on a Symbol MC9000 and Dell Axim running
Pocket PC but would not run on the MC3000. I contacted Symbol and got
their SDK and it solved the problem. I'm using the Symbol Mobility
Developer Kit for .Net v1.2. Symbol says the SDK is only for the
MC9000 series devices running Pocket PC but one of their Engineers told
me to use it with the MC3000 as well and it did the trick.

When you build your CAB file, which files are you installing on the
device? If the CAB file is built correctly it should be something like
AppName_PPC.ARMV4.CAB and AppName_PPC.ARMV4.DAT. The CAB files will
install the application on the device so it will run properly.

If you have active sync and the device hooked directly to your
development machine, you could also run in debug mode on the device
itself. That would be your best bet because it would deploy everything
to the device for you.

Regards,
Johnny
I must sadly say yes. I did nothing wrong and just couldn't run it.
I decided to switch to embedded Visual C++ 4.0 for my current needs,
and everything works fine, although proggraming is much more dificult.
I just hope that I won't have theese kind of problems when I start to
write
applications in VS2005 for devices that have Windows CE 5.0.
Thanks again for all your trouble.

Best regards,
Zarko Stanisavljevic

Paul G. Tobey [eMVP] wrote:
Only if you told it to do the wrong thing. I suppose that, if you want to
spend the day installing things, you could uninstall VS and reinstall it and
see if that makes any difference but I think that it's very unlikely, if you
did everything correctly, that this would happen. You're just running the
default code created by the new project wizard, right? You selected Other
Languages | Visual C# | Smart Device | Windows Mobile 5.0 Pocket PC and then
selected Device Application (1.0) from the list of project types?

Paul T.

Here is what I just noticed.
When I download application ("Hello World") from my MC3000,
which came with the device and which works on a device, and
try to run it on my PC I get ""Hello.exe" is not a valid Win32
application" which is opposite from the error I get when I run
my application on the device. Also my application works fine
on the PC.
Can it be posible that the VS doesn't create
SmartDeviceApplication correctly? And if it can, then
what should I do about it?

Best regards,
Zarko Stanisavljevic
zangloma wrote:
I also just tried Pocket PC 2003 SDK, but it is used with
eVC, too.
I really don't no what to do anymore. I have application that
should without a problems, but it just won't.

Zarko
zangloma wrote:
I know it should, but it won't.
I believe that the simpliest application ("Hello World"), should work
if I only
deploy Compact Framework 1.0 and the application it self.
But I get ""SmartDeviceApplication1" is not a valid Windows CE
application" error.
Do you maybe know what could be the reason?

Zarko
Dexlex wrote:
eMbedded Visual C++ is definitely not needed for SMDK V1.3 for .Net,
only
for SMDK V1.4 for eVC.

For simple applications you don't need any Symbol SDK at all. The DCP
is
only needed to create HEX files for download using the IPL mode of
the PDA
for deployment.

Just create a small "Hello World" program (Smart Device Application
for .Net
1.0), download it to the device (either by using the debugger or by
copying
it to the file system on the device with ActiveSync) and start it -
it
should work.

Dex


Thanks guys for all your answers.
But my problem remains. All the things that you mantioned I already
did.
I am using Symbol Mobility Developers Kit v1.3 for .NET and it's
working fine.
It is used to work with the barcode reader, and it adds up barcode
reader in the Toolbox
in VS and also bunch of dll files on the device.
Symbol does have a Symbol SDK, but it only works in combination
with
embedded
Visual C++ 4.0, and I would definetily like to avoid switching to
another language. But
that SDK won't install wirhout eVC.
Here is what the Symbol tech support wrote to me:
"Hello Zarko,

Please see the install requirements for the Symbol Mobility
Developer
Kit v1.3 for .NET -

http://devzone.symbol.com/content.cfm?item_id=96DC2AFA-650B-4693-BB35EF8
C47DD8897

Also make sure you have installed DCP V1.1 for the MC3000 from
the
devzone -

http://devzone.symbol.com/content.cfm?item_id=A6DE099D-0FC5-4E82-BA28A31
A1EB89153



Kind regards,

Tom Stejskal

L1 CIC Technical Helpdesk
EMEA Customer Operations
Global Services Division
Symbol Technologies, Inc.
www.symbol.com

www.symbol.com/services/contactsupport for your local support
number

(e-mail address removed)

Symbol. The Enterprise Mobility Company. (TM)"

So I did that and again nothing. The DCP v1.1 is used for file
transfer
between the PC
and the device.
Only interesting thing that I saw was when I visited the second
link
that they gave me.
There is a following sentence:
"A DCP can NOT be used to create applications. To create
applications
for the MC 3000, download and install theSMDK for eVC4 and the
Microsoft Pocket PC 2003 SDK."
And the part that I find interesting is about Pocket PC 2003 SDK.
Could that be the solution for my problem?
I will give it a shot. And if anyone thinks of something I could
try do
tell.
I 'm sure that it has to work with VS.

Best regards,
Zarko Stanisavljevic



Dexlex wrote:
CE4.2 => VS2003
CE5.0 => VS2005

This is the supported way, but CE4.2 with VS2005 might also work,
as it
does
with me.

However, the MC3000 series can be to upgraded to WinCE5.0 -
contact your
Symbol dealer.

"not a valid Windows CE application" - did you set up a Smart
Device
Application (not possible with VS2005 Express)?

Dex


Has anyone had any experience in programming for Symbol MC3000
which
has Windows CE
4.2 in VS .NET or 2005?
I tried everything I could find on the net, but had no luck in
making
the simpliest application work. Best I could get is the "not a
valid
Windows CE application" error.
It seems to me that this device needs more than a standard PDAs.
Because I installed
Compact Framework 1.0 and nothing changes.
I would apreciate if someone would tell me everything I need to
do to
make application
written in C# work on a Symbol MC3000.

Best regards,
Zarko Stanisavljevic
 
C

CenGenTech

I downloaded the file SMDK-M-1.02.03.exe from Symbol's website. The
SDK is for the MC9000 series devices. I installed the SDK and then
created a new project as follows:

- File > New Projects > Visual C# Projects > Smart Device Application
- The Smart Device Application Wizard is displayed and I select Pocket
PC (not Windows CE) and
Windows Application as the project type.
- I then add the Symbol.dll reference
- Add a lable - Hello World and deploy to Pocket PC Device

That's it. It works for me!

Regards,
Johnny

- In the New Project dialog I selected Visual C# Projects
zangloma said:
What SDK are you refering to?
I tried to instal Platform SDK for MC3000c42 that I got from Symbol's
site, but it won't start the installation without eVC. And when I'm
deploying
I am doing it from VS, so it transfers everything by it self.
Could you tell me exactly what do you have on your PC, and on your
device. And the exact procedure for creating the empty form that will
work.
Please.

Zarko
Zarko,

I had a similar problem when I first started developing for the MC3000.
My applications would work on a Symbol MC9000 and Dell Axim running
Pocket PC but would not run on the MC3000. I contacted Symbol and got
their SDK and it solved the problem. I'm using the Symbol Mobility
Developer Kit for .Net v1.2. Symbol says the SDK is only for the
MC9000 series devices running Pocket PC but one of their Engineers told
me to use it with the MC3000 as well and it did the trick.

When you build your CAB file, which files are you installing on the
device? If the CAB file is built correctly it should be something like
AppName_PPC.ARMV4.CAB and AppName_PPC.ARMV4.DAT. The CAB files will
install the application on the device so it will run properly.

If you have active sync and the device hooked directly to your
development machine, you could also run in debug mode on the device
itself. That would be your best bet because it would deploy everything
to the device for you.

Regards,
Johnny
I must sadly say yes. I did nothing wrong and just couldn't run it.
I decided to switch to embedded Visual C++ 4.0 for my current needs,
and everything works fine, although proggraming is much more dificult.
I just hope that I won't have theese kind of problems when I start to
write
applications in VS2005 for devices that have Windows CE 5.0.
Thanks again for all your trouble.

Best regards,
Zarko Stanisavljevic

Paul G. Tobey [eMVP] wrote:
Only if you told it to do the wrong thing. I suppose that, if you want to
spend the day installing things, you could uninstall VS and reinstall it and
see if that makes any difference but I think that it's very unlikely, if you
did everything correctly, that this would happen. You're just running the
default code created by the new project wizard, right? You selected Other
Languages | Visual C# | Smart Device | Windows Mobile 5.0 Pocket PC and then
selected Device Application (1.0) from the list of project types?

Paul T.

Here is what I just noticed.
When I download application ("Hello World") from my MC3000,
which came with the device and which works on a device, and
try to run it on my PC I get ""Hello.exe" is not a valid Win32
application" which is opposite from the error I get when I run
my application on the device. Also my application works fine
on the PC.
Can it be posible that the VS doesn't create
SmartDeviceApplication correctly? And if it can, then
what should I do about it?

Best regards,
Zarko Stanisavljevic
zangloma wrote:
I also just tried Pocket PC 2003 SDK, but it is used with
eVC, too.
I really don't no what to do anymore. I have application that
should without a problems, but it just won't.

Zarko
zangloma wrote:
I know it should, but it won't.
I believe that the simpliest application ("Hello World"), should work
if I only
deploy Compact Framework 1.0 and the application it self.
But I get ""SmartDeviceApplication1" is not a valid Windows CE
application" error.
Do you maybe know what could be the reason?

Zarko
Dexlex wrote:
eMbedded Visual C++ is definitely not needed for SMDK V1.3 for .Net,
only
for SMDK V1.4 for eVC.

For simple applications you don't need any Symbol SDK at all. The DCP
is
only needed to create HEX files for download using the IPL mode of
the PDA
for deployment.

Just create a small "Hello World" program (Smart Device Application
for .Net
1.0), download it to the device (either by using the debugger or by
copying
it to the file system on the device with ActiveSync) and start it -
it
should work.

Dex


Thanks guys for all your answers.
But my problem remains. All the things that you mantioned I already
did.
I am using Symbol Mobility Developers Kit v1.3 for .NET and it's
working fine.
It is used to work with the barcode reader, and it adds up barcode
reader in the Toolbox
in VS and also bunch of dll files on the device.
Symbol does have a Symbol SDK, but it only works in combination
with
embedded
Visual C++ 4.0, and I would definetily like to avoid switching to
another language. But
that SDK won't install wirhout eVC.
Here is what the Symbol tech support wrote to me:
"Hello Zarko,

Please see the install requirements for the Symbol Mobility
Developer
Kit v1.3 for .NET -

http://devzone.symbol.com/content.cfm?item_id=96DC2AFA-650B-4693-BB35EF8
C47DD8897

Also make sure you have installed DCP V1.1 for the MC3000 from
the
devzone -

http://devzone.symbol.com/content.cfm?item_id=A6DE099D-0FC5-4E82-BA28A31
A1EB89153



Kind regards,

Tom Stejskal

L1 CIC Technical Helpdesk
EMEA Customer Operations
Global Services Division
Symbol Technologies, Inc.
www.symbol.com

www.symbol.com/services/contactsupport for your local support
number

(e-mail address removed)

Symbol. The Enterprise Mobility Company. (TM)"

So I did that and again nothing. The DCP v1.1 is used for file
transfer
between the PC
and the device.
Only interesting thing that I saw was when I visited the second
link
that they gave me.
There is a following sentence:
"A DCP can NOT be used to create applications. To create
applications
for the MC 3000, download and install theSMDK for eVC4 and the
Microsoft Pocket PC 2003 SDK."
And the part that I find interesting is about Pocket PC 2003 SDK.
Could that be the solution for my problem?
I will give it a shot. And if anyone thinks of something I could
try do
tell.
I 'm sure that it has to work with VS.

Best regards,
Zarko Stanisavljevic



Dexlex wrote:
CE4.2 => VS2003
CE5.0 => VS2005

This is the supported way, but CE4.2 with VS2005 might also work,
as it
does
with me.

However, the MC3000 series can be to upgraded to WinCE5.0 -
contact your
Symbol dealer.

"not a valid Windows CE application" - did you set up a Smart
Device
Application (not possible with VS2005 Express)?

Dex


Has anyone had any experience in programming for Symbol MC3000
which
has Windows CE
4.2 in VS .NET or 2005?
I tried everything I could find on the net, but had no luck in
making
the simpliest application work. Best I could get is the "not a
valid
Windows CE application" error.
It seems to me that this device needs more than a standard PDAs.
Because I installed
Compact Framework 1.0 and nothing changes.
I would apreciate if someone would tell me everything I need to
do to
make application
written in C# work on a Symbol MC3000.

Best regards,
Zarko Stanisavljevic
 
Z

zangloma

Thanks.
I'll try that wright away.
I'll let you know what happened.

Zarko said:
I downloaded the file SMDK-M-1.02.03.exe from Symbol's website. The
SDK is for the MC9000 series devices. I installed the SDK and then
created a new project as follows:

- File > New Projects > Visual C# Projects > Smart Device Application
- The Smart Device Application Wizard is displayed and I select Pocket
PC (not Windows CE) and
Windows Application as the project type.
- I then add the Symbol.dll reference
- Add a lable - Hello World and deploy to Pocket PC Device

That's it. It works for me!

Regards,
Johnny

- In the New Project dialog I selected Visual C# Projects
zangloma said:
What SDK are you refering to?
I tried to instal Platform SDK for MC3000c42 that I got from Symbol's
site, but it won't start the installation without eVC. And when I'm
deploying
I am doing it from VS, so it transfers everything by it self.
Could you tell me exactly what do you have on your PC, and on your
device. And the exact procedure for creating the empty form that will
work.
Please.

Zarko
Zarko,

I had a similar problem when I first started developing for the MC3000.
My applications would work on a Symbol MC9000 and Dell Axim running
Pocket PC but would not run on the MC3000. I contacted Symbol and got
their SDK and it solved the problem. I'm using the Symbol Mobility
Developer Kit for .Net v1.2. Symbol says the SDK is only for the
MC9000 series devices running Pocket PC but one of their Engineers told
me to use it with the MC3000 as well and it did the trick.

When you build your CAB file, which files are you installing on the
device? If the CAB file is built correctly it should be something like
AppName_PPC.ARMV4.CAB and AppName_PPC.ARMV4.DAT. The CAB files will
install the application on the device so it will run properly.

If you have active sync and the device hooked directly to your
development machine, you could also run in debug mode on the device
itself. That would be your best bet because it would deploy everything
to the device for you.

Regards,
Johnny

zangloma wrote:
I must sadly say yes. I did nothing wrong and just couldn't run it.
I decided to switch to embedded Visual C++ 4.0 for my current needs,
and everything works fine, although proggraming is much more dificult.
I just hope that I won't have theese kind of problems when I start to
write
applications in VS2005 for devices that have Windows CE 5.0.
Thanks again for all your trouble.

Best regards,
Zarko Stanisavljevic

Paul G. Tobey [eMVP] wrote:
Only if you told it to do the wrong thing. I suppose that, if you want to
spend the day installing things, you could uninstall VS and reinstall it and
see if that makes any difference but I think that it's very unlikely, if you
did everything correctly, that this would happen. You're just running the
default code created by the new project wizard, right? You selected Other
Languages | Visual C# | Smart Device | Windows Mobile 5.0 Pocket PC and then
selected Device Application (1.0) from the list of project types?

Paul T.

Here is what I just noticed.
When I download application ("Hello World") from my MC3000,
which came with the device and which works on a device, and
try to run it on my PC I get ""Hello.exe" is not a valid Win32
application" which is opposite from the error I get when I run
my application on the device. Also my application works fine
on the PC.
Can it be posible that the VS doesn't create
SmartDeviceApplication correctly? And if it can, then
what should I do about it?

Best regards,
Zarko Stanisavljevic
zangloma wrote:
I also just tried Pocket PC 2003 SDK, but it is used with
eVC, too.
I really don't no what to do anymore. I have application that
should without a problems, but it just won't.

Zarko
zangloma wrote:
I know it should, but it won't.
I believe that the simpliest application ("Hello World"), should work
if I only
deploy Compact Framework 1.0 and the application it self.
But I get ""SmartDeviceApplication1" is not a valid Windows CE
application" error.
Do you maybe know what could be the reason?

Zarko
Dexlex wrote:
eMbedded Visual C++ is definitely not needed for SMDK V1.3 for .Net,
only
for SMDK V1.4 for eVC.

For simple applications you don't need any Symbol SDK at all. The DCP
is
only needed to create HEX files for download using the IPL mode of
the PDA
for deployment.

Just create a small "Hello World" program (Smart Device Application
for .Net
1.0), download it to the device (either by using the debugger or by
copying
it to the file system on the device with ActiveSync) and start it -
it
should work.

Dex


Thanks guys for all your answers.
But my problem remains. All the things that you mantioned I already
did.
I am using Symbol Mobility Developers Kit v1.3 for .NET and it's
working fine.
It is used to work with the barcode reader, and it adds up barcode
reader in the Toolbox
in VS and also bunch of dll files on the device.
Symbol does have a Symbol SDK, but it only works in combination
with
embedded
Visual C++ 4.0, and I would definetily like to avoid switching to
another language. But
that SDK won't install wirhout eVC.
Here is what the Symbol tech support wrote to me:
"Hello Zarko,

Please see the install requirements for the Symbol Mobility
Developer
Kit v1.3 for .NET -

http://devzone.symbol.com/content.cfm?item_id=96DC2AFA-650B-4693-BB35EF8
C47DD8897

Also make sure you have installed DCP V1.1 for the MC3000 from
the
devzone -

http://devzone.symbol.com/content.cfm?item_id=A6DE099D-0FC5-4E82-BA28A31
A1EB89153



Kind regards,

Tom Stejskal

L1 CIC Technical Helpdesk
EMEA Customer Operations
Global Services Division
Symbol Technologies, Inc.
www.symbol.com

www.symbol.com/services/contactsupport for your local support
number

(e-mail address removed)

Symbol. The Enterprise Mobility Company. (TM)"

So I did that and again nothing. The DCP v1.1 is used for file
transfer
between the PC
and the device.
Only interesting thing that I saw was when I visited the second
link
that they gave me.
There is a following sentence:
"A DCP can NOT be used to create applications. To create
applications
for the MC 3000, download and install theSMDK for eVC4 and the
Microsoft Pocket PC 2003 SDK."
And the part that I find interesting is about Pocket PC 2003 SDK.
Could that be the solution for my problem?
I will give it a shot. And if anyone thinks of something I could
try do
tell.
I 'm sure that it has to work with VS.

Best regards,
Zarko Stanisavljevic



Dexlex wrote:
CE4.2 => VS2003
CE5.0 => VS2005

This is the supported way, but CE4.2 with VS2005 might also work,
as it
does
with me.

However, the MC3000 series can be to upgraded to WinCE5.0 -
contact your
Symbol dealer.

"not a valid Windows CE application" - did you set up a Smart
Device
Application (not possible with VS2005 Express)?

Dex


Has anyone had any experience in programming for Symbol MC3000
which
has Windows CE
4.2 in VS .NET or 2005?
I tried everything I could find on the net, but had no luck in
making
the simpliest application work. Best I could get is the "not a
valid
Windows CE application" error.
It seems to me that this device needs more than a standard PDAs.
Because I installed
Compact Framework 1.0 and nothing changes.
I would apreciate if someone would tell me everything I need to
do to
make application
written in C# work on a Symbol MC3000.

Best regards,
Zarko Stanisavljevic
 
Z

zangloma

Johnny,
nothing again. I 'm stuck and just can't move.
I guess I'll let a little time to pass, and then try again.
Just tell me is the SMDK-M-1.02.03.exe the only thing
that you instal, because every SDK that I have seen on
Symbol's site was ment to be used with eVC.
For example there are: Platform SDK for MC3000c42v1.0,
Platform SDKv1.01.06 for MC9000c42, etc.
Do you use any of theese, or just SMDK for .NET?

Regards,
Zarko
Thanks.
I'll try that wright away.
I'll let you know what happened.

Zarko said:
I downloaded the file SMDK-M-1.02.03.exe from Symbol's website. The
SDK is for the MC9000 series devices. I installed the SDK and then
created a new project as follows:

- File > New Projects > Visual C# Projects > Smart Device Application
- The Smart Device Application Wizard is displayed and I select Pocket
PC (not Windows CE) and
Windows Application as the project type.
- I then add the Symbol.dll reference
- Add a lable - Hello World and deploy to Pocket PC Device

That's it. It works for me!

Regards,
Johnny

- In the New Project dialog I selected Visual C# Projects
zangloma said:
What SDK are you refering to?
I tried to instal Platform SDK for MC3000c42 that I got from Symbol's
site, but it won't start the installation without eVC. And when I'm
deploying
I am doing it from VS, so it transfers everything by it self.
Could you tell me exactly what do you have on your PC, and on your
device. And the exact procedure for creating the empty form that will
work.
Please.

Zarko

CenGenTech wrote:
Zarko,

I had a similar problem when I first started developing for the MC3000.
My applications would work on a Symbol MC9000 and Dell Axim running
Pocket PC but would not run on the MC3000. I contacted Symbol and got
their SDK and it solved the problem. I'm using the Symbol Mobility
Developer Kit for .Net v1.2. Symbol says the SDK is only for the
MC9000 series devices running Pocket PC but one of their Engineers told
me to use it with the MC3000 as well and it did the trick.

When you build your CAB file, which files are you installing on the
device? If the CAB file is built correctly it should be something like
AppName_PPC.ARMV4.CAB and AppName_PPC.ARMV4.DAT. The CAB files will
install the application on the device so it will run properly.

If you have active sync and the device hooked directly to your
development machine, you could also run in debug mode on the device
itself. That would be your best bet because it would deploy everything
to the device for you.

Regards,
Johnny

zangloma wrote:
I must sadly say yes. I did nothing wrong and just couldn't run it.
I decided to switch to embedded Visual C++ 4.0 for my current needs,
and everything works fine, although proggraming is much more dificult.
I just hope that I won't have theese kind of problems when I start to
write
applications in VS2005 for devices that have Windows CE 5.0.
Thanks again for all your trouble.

Best regards,
Zarko Stanisavljevic

Paul G. Tobey [eMVP] wrote:
Only if you told it to do the wrong thing. I suppose that, if you want to
spend the day installing things, you could uninstall VS and reinstall it and
see if that makes any difference but I think that it's very unlikely, if you
did everything correctly, that this would happen. You're just running the
default code created by the new project wizard, right? You selected Other
Languages | Visual C# | Smart Device | Windows Mobile 5.0 Pocket PC and then
selected Device Application (1.0) from the list of project types?

Paul T.

Here is what I just noticed.
When I download application ("Hello World") from my MC3000,
which came with the device and which works on a device, and
try to run it on my PC I get ""Hello.exe" is not a valid Win32
application" which is opposite from the error I get when I run
my application on the device. Also my application works fine
on the PC.
Can it be posible that the VS doesn't create
SmartDeviceApplication correctly? And if it can, then
what should I do about it?

Best regards,
Zarko Stanisavljevic
zangloma wrote:
I also just tried Pocket PC 2003 SDK, but it is used with
eVC, too.
I really don't no what to do anymore. I have application that
should without a problems, but it just won't.

Zarko
zangloma wrote:
I know it should, but it won't.
I believe that the simpliest application ("Hello World"), should work
if I only
deploy Compact Framework 1.0 and the application it self.
But I get ""SmartDeviceApplication1" is not a valid Windows CE
application" error.
Do you maybe know what could be the reason?

Zarko
Dexlex wrote:
eMbedded Visual C++ is definitely not needed for SMDK V1.3 for .Net,
only
for SMDK V1.4 for eVC.

For simple applications you don't need any Symbol SDK at all. The DCP
is
only needed to create HEX files for download using the IPL mode of
the PDA
for deployment.

Just create a small "Hello World" program (Smart Device Application
for .Net
1.0), download it to the device (either by using the debugger or by
copying
it to the file system on the device with ActiveSync) and start it -
it
should work.

Dex


Thanks guys for all your answers.
But my problem remains. All the things that you mantioned I already
did.
I am using Symbol Mobility Developers Kit v1.3 for .NET and it's
working fine.
It is used to work with the barcode reader, and it adds up barcode
reader in the Toolbox
in VS and also bunch of dll files on the device.
Symbol does have a Symbol SDK, but it only works in combination
with
embedded
Visual C++ 4.0, and I would definetily like to avoid switching to
another language. But
that SDK won't install wirhout eVC.
Here is what the Symbol tech support wrote to me:
"Hello Zarko,

Please see the install requirements for the Symbol Mobility
Developer
Kit v1.3 for .NET -

http://devzone.symbol.com/content.cfm?item_id=96DC2AFA-650B-4693-BB35EF8
C47DD8897

Also make sure you have installed DCP V1.1 for the MC3000 from
the
devzone -

http://devzone.symbol.com/content.cfm?item_id=A6DE099D-0FC5-4E82-BA28A31
A1EB89153



Kind regards,

Tom Stejskal

L1 CIC Technical Helpdesk
EMEA Customer Operations
Global Services Division
Symbol Technologies, Inc.
www.symbol.com

www.symbol.com/services/contactsupport for your local support
number

(e-mail address removed)

Symbol. The Enterprise Mobility Company. (TM)"

So I did that and again nothing. The DCP v1.1 is used for file
transfer
between the PC
and the device.
Only interesting thing that I saw was when I visited the second
link
that they gave me.
There is a following sentence:
"A DCP can NOT be used to create applications. To create
applications
for the MC 3000, download and install theSMDK for eVC4 and the
Microsoft Pocket PC 2003 SDK."
And the part that I find interesting is about Pocket PC 2003 SDK.
Could that be the solution for my problem?
I will give it a shot. And if anyone thinks of something I could
try do
tell.
I 'm sure that it has to work with VS.

Best regards,
Zarko Stanisavljevic



Dexlex wrote:
CE4.2 => VS2003
CE5.0 => VS2005

This is the supported way, but CE4.2 with VS2005 might also work,
as it
does
with me.

However, the MC3000 series can be to upgraded to WinCE5.0 -
contact your
Symbol dealer.

"not a valid Windows CE application" - did you set up a Smart
Device
Application (not possible with VS2005 Express)?

Dex


Has anyone had any experience in programming for Symbol MC3000
which
has Windows CE
4.2 in VS .NET or 2005?
I tried everything I could find on the net, but had no luck in
making
the simpliest application work. Best I could get is the "not a
valid
Windows CE application" error.
It seems to me that this device needs more than a standard PDAs.
Because I installed
Compact Framework 1.0 and nothing changes.
I would apreciate if someone would tell me everything I need to
do to
make application
written in C# work on a Symbol MC3000.

Best regards,
Zarko Stanisavljevic
 
C

CenGenTech

That's really all I had to install from Symbol. I can send you the SDK
if you would like.

Do you have the application functioning on another device?

Regards,
Johnny
Johnny,
nothing again. I 'm stuck and just can't move.
I guess I'll let a little time to pass, and then try again.
Just tell me is the SMDK-M-1.02.03.exe the only thing
that you instal, because every SDK that I have seen on
Symbol's site was ment to be used with eVC.
For example there are: Platform SDK for MC3000c42v1.0,
Platform SDKv1.01.06 for MC9000c42, etc.
Do you use any of theese, or just SMDK for .NET?

Regards,
Zarko
Thanks.
I'll try that wright away.
I'll let you know what happened.

Zarko said:
I downloaded the file SMDK-M-1.02.03.exe from Symbol's website. The
SDK is for the MC9000 series devices. I installed the SDK and then
created a new project as follows:

- File > New Projects > Visual C# Projects > Smart Device Application
- The Smart Device Application Wizard is displayed and I select Pocket
PC (not Windows CE) and
Windows Application as the project type.
- I then add the Symbol.dll reference
- Add a lable - Hello World and deploy to Pocket PC Device

That's it. It works for me!

Regards,
Johnny

- In the New Project dialog I selected Visual C# Projects
zangloma wrote:
What SDK are you refering to?
I tried to instal Platform SDK for MC3000c42 that I got from Symbol's
site, but it won't start the installation without eVC. And when I'm
deploying
I am doing it from VS, so it transfers everything by it self.
Could you tell me exactly what do you have on your PC, and on your
device. And the exact procedure for creating the empty form that will
work.
Please.

Zarko

CenGenTech wrote:
Zarko,

I had a similar problem when I first started developing for the MC3000.
My applications would work on a Symbol MC9000 and Dell Axim running
Pocket PC but would not run on the MC3000. I contacted Symbol and got
their SDK and it solved the problem. I'm using the Symbol Mobility
Developer Kit for .Net v1.2. Symbol says the SDK is only for the
MC9000 series devices running Pocket PC but one of their Engineers told
me to use it with the MC3000 as well and it did the trick.

When you build your CAB file, which files are you installing on the
device? If the CAB file is built correctly it should be something like
AppName_PPC.ARMV4.CAB and AppName_PPC.ARMV4.DAT. The CAB files will
install the application on the device so it will run properly.

If you have active sync and the device hooked directly to your
development machine, you could also run in debug mode on the device
itself. That would be your best bet because it would deploy everything
to the device for you.

Regards,
Johnny

zangloma wrote:
I must sadly say yes. I did nothing wrong and just couldn't run it.
I decided to switch to embedded Visual C++ 4.0 for my current needs,
and everything works fine, although proggraming is much more dificult.
I just hope that I won't have theese kind of problems when I start to
write
applications in VS2005 for devices that have Windows CE 5.0.
Thanks again for all your trouble.

Best regards,
Zarko Stanisavljevic

Paul G. Tobey [eMVP] wrote:
Only if you told it to do the wrong thing. I suppose that, if you want to
spend the day installing things, you could uninstall VS and reinstall it and
see if that makes any difference but I think that it's very unlikely, if you
did everything correctly, that this would happen. You're just running the
default code created by the new project wizard, right? You selected Other
Languages | Visual C# | Smart Device | Windows Mobile 5.0 Pocket PC and then
selected Device Application (1.0) from the list of project types?

Paul T.

Here is what I just noticed.
When I download application ("Hello World") from my MC3000,
which came with the device and which works on a device, and
try to run it on my PC I get ""Hello.exe" is not a valid Win32
application" which is opposite from the error I get when I run
my application on the device. Also my application works fine
on the PC.
Can it be posible that the VS doesn't create
SmartDeviceApplication correctly? And if it can, then
what should I do about it?

Best regards,
Zarko Stanisavljevic
zangloma wrote:
I also just tried Pocket PC 2003 SDK, but it is used with
eVC, too.
I really don't no what to do anymore. I have application that
should without a problems, but it just won't.

Zarko
zangloma wrote:
I know it should, but it won't.
I believe that the simpliest application ("Hello World"), should work
if I only
deploy Compact Framework 1.0 and the application it self.
But I get ""SmartDeviceApplication1" is not a valid Windows CE
application" error.
Do you maybe know what could be the reason?

Zarko
Dexlex wrote:
eMbedded Visual C++ is definitely not needed for SMDK V1.3 for .Net,
only
for SMDK V1.4 for eVC.

For simple applications you don't need any Symbol SDK at all. The DCP
is
only needed to create HEX files for download using the IPL mode of
the PDA
for deployment.

Just create a small "Hello World" program (Smart Device Application
for .Net
1.0), download it to the device (either by using the debugger or by
copying
it to the file system on the device with ActiveSync) and start it -
it
should work.

Dex


Thanks guys for all your answers.
But my problem remains. All the things that you mantioned I already
did.
I am using Symbol Mobility Developers Kit v1.3 for .NET and it's
working fine.
It is used to work with the barcode reader, and it adds up barcode
reader in the Toolbox
in VS and also bunch of dll files on the device.
Symbol does have a Symbol SDK, but it only works in combination
with
embedded
Visual C++ 4.0, and I would definetily like to avoid switching to
another language. But
that SDK won't install wirhout eVC.
Here is what the Symbol tech support wrote to me:
"Hello Zarko,

Please see the install requirements for the Symbol Mobility
Developer
Kit v1.3 for .NET -

http://devzone.symbol.com/content.cfm?item_id=96DC2AFA-650B-4693-BB35EF8
C47DD8897

Also make sure you have installed DCP V1.1 for the MC3000 from
the
devzone -

http://devzone.symbol.com/content.cfm?item_id=A6DE099D-0FC5-4E82-BA28A31
A1EB89153



Kind regards,

Tom Stejskal

L1 CIC Technical Helpdesk
EMEA Customer Operations
Global Services Division
Symbol Technologies, Inc.
www.symbol.com

www.symbol.com/services/contactsupport for your local support
number

(e-mail address removed)

Symbol. The Enterprise Mobility Company. (TM)"

So I did that and again nothing. The DCP v1.1 is used for file
transfer
between the PC
and the device.
Only interesting thing that I saw was when I visited the second
link
that they gave me.
There is a following sentence:
"A DCP can NOT be used to create applications. To create
applications
for the MC 3000, download and install theSMDK for eVC4 and the
Microsoft Pocket PC 2003 SDK."
And the part that I find interesting is about Pocket PC 2003 SDK.
Could that be the solution for my problem?
I will give it a shot. And if anyone thinks of something I could
try do
tell.
I 'm sure that it has to work with VS.

Best regards,
Zarko Stanisavljevic



Dexlex wrote:
CE4.2 => VS2003
CE5.0 => VS2005

This is the supported way, but CE4.2 with VS2005 might also work,
as it
does
with me.

However, the MC3000 series can be to upgraded to WinCE5.0 -
contact your
Symbol dealer.

"not a valid Windows CE application" - did you set up a Smart
Device
Application (not possible with VS2005 Express)?

Dex


Has anyone had any experience in programming for Symbol MC3000
which
has Windows CE
4.2 in VS .NET or 2005?
I tried everything I could find on the net, but had no luck in
making
the simpliest application work. Best I could get is the "not a
valid
Windows CE application" error.
It seems to me that this device needs more than a standard PDAs.
Because I installed
Compact Framework 1.0 and nothing changes.
I would apreciate if someone would tell me everything I need to
do to
make application
written in C# work on a Symbol MC3000.

Best regards,
Zarko Stanisavljevic
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top