cross-compiling).
As far as I can tell, I did. I compiled with the "StandardSDK", "WIN32
(WSE Emulator) Debug", "Standard SDK Emulator" settings. Currently (just
ethernet switch driver" component. No idea why though.
I used it to see if the installation went O.K. Seeing that it was not able
to emulate anything I had to assume something went wrong. As the suggested
solution was to re-install that was less than helpfull. The net result was
Nope. Currently will not work for me ...
That was kind of my intention all along. But the higher the cost of the
I actually need becomes.
and working on my phone (Yay!).
created earlier from my PC using the RAPI functions) in a listview. I allso
does not close" (just minimizes/hides the app) problem too.
hand) I can say I have successfully done my first steps. :-)
please indicate which newsgroup and message).
Post by Paul G. Tobey [eMVP]We're working back in the distant past for me with eVC4, but I recall there
being an add-on download that would install the emulator's Ethernet adapter.
If I remember right, this was something that MS extracted from Virtual PC and
made available. Maybe it came with one of the eVC service packs. You could
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4a4ed1f4-91d3-4dbe-986e-a812984318e5
and, if that does not work, b) look around and see if you cannot find some old
references in the newsgroups to the emulator Ethernet component. You can use
GoogleGroups Advanced Search to search newsgroups
microsoft.public.windowsce.*.
Again, though, what you are trying to do, given the equipment you have
(WM6.1), is, in my opinion, a complete waste of your time. What you will end
up with is an emulation of something that you do not have, that does not work
the way your actual target works, etc.
"Standard" is a complete and total misnomer. Microsoft stepped on itself
with the name of that SDK and has misled hundreds of people into thinking
that because this thing says "Standard" on it that it means that it is like an
average device. That's total garbage. Uninstall the Standard SDK
completely; I say it is absolutely useless. If you are determined to use
tools that are eight years out of date, eVC, then at least install the Pocket
PC 2003 SDK for it. That's a distant relative to the device that you
actually have, at least. Standard SDK has no relationship with your actual
device AT ALL.
No, there is no THE EMULATOR. There are emulators for various device
classes. The only emulator that makes sense for you is the one for WM6.1,
since that is the actual target device. Windows CE is not AN operating
system. it is a set of operating system components that can be assembled in
an almost-infinite number of ways by a device vendor. it is not possible to
emulate A Windows CE device with a single emulator, for this reason.
You're using something that is a dumb 'product', the Standard SDK, that
Microsoft finally abandoned because it was so silly. And, you are trying to
use it as a basis for development of a Windows Mobile application, when
Windows Mobile devices have many behaviors that the Standard SDK emulator
does not. That's the shortcut I am talking about. Use the real emulator for
the real device class you actually have, and you will get useful results.
Yes, Quick Basic came from MS, too. Are you going to use that? You have a
modern device, three generations later than the emulator that comes with eVC4
for devices of the same general type (NOT STANDARD SDK -- uninstall that
stupid thing!, but Pocket PC Emulator), but you are trying to use the wrong
SDK, the wrong emulator, and the wrong development environment to write your
code. You are off the map. It is possible to make it work, but you do not
have the level of experience with the tools and target platforms to make it
practical to do this. Robert has done this for years and, for him, yes, it is
practical.
Paul T.
Post by R.WieserHello Paul,
I checked, but allready have SP4 installed (was not sure if it was SP3 or
SP4).
At the momemnt of my writing that I did not know that. I was in the
assumption that the "standard SDK" was usable to test code without any
regard to a specific device (a sort of "minimum requirements" environment).
I was not sure I could (and did not want to meddle around in something that,
at last, worked), but allready thought about it. I will probably do it
directly after finishing this mesage.
Allready done. Its what I used as target for those "hello world" and
DBase-viewer apps I mentioned earlier.
Than its too bad its still part of and installed by default by the EVC4
package and, with no real (for a beginner) mentioning of the other options.
Probably, yes. If I cannot find an assembler that I can use to create
Pocket-PC executables with I will probably try and see if I can use it to take
a peek into an EVC4 generated executable generate one myself. You will be
amazed what Quick Basic still can do.
Yes, I am that kind of a hobbyist. :-)
"Off the map" ? Not quite. I tried to make sense of what that "Standard
SDK" could mean/do for me. Without adequate information I had/have no
other choice than to try, and if that does not work, ask. I did (hence these
posts), and currently can conclude (with you guys help, thanks) that its
prety-much worthless.
I allready did install the "Pocket PC 2003 SDK", which enabled me to get
that first "Hello world!" app working on my phone. I think that also did
put me "on the map" again.
I am not sure at what level you regard something to work, but I currently can
write apps that run on my device. I will probably keep doing that for some
time to see what I can make and when EVC4/Pocket PC 2003 SDK becomes
restrictive (instead of aiding). At that point its early enough to think
about spending money on VS2005 or VS2008.
Regards,
Rudy Wieser
Paul G. Tobey [eMVP] <paultobey _at_ earthlink _dot_ net> schreef in
there
adapter.
and
could
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4a4e
d1f4-91d3-4dbe-986e-a812984318e5
old
use
Post by Paul G. Tobey [eMVP]I know. That's one of the many reasons that many of us hounded Microsoft to
drop that SDK. It just sounds like "here you go. this is all you need".
Now you should be able to select the PPC2003 Emulator as the target, set the
processor type to the emulator, and try your code on the processor. I think
that Robert is right about the network card being the issue with the emulator
not starting correctly.
eVC has not even been updated in five years, but I know what you mean.
That's sort of the hazard of making a big mistake with a free product; it
never really leaves the market, so users keep reliving the mistake
indefinitely.
Development tools that cannot debug on the target device are useless for
anything 'real'. Yes, you can play around and maybe it is not too big a deal
for something like a Today screen extension, since you cannot really debug
those using application tools anyway. Even if I am just screwing around with
a device, trying to add something that would help me a little or fix a minor
problem with the default code, I value my time too highly to live without
single-stepping, variable inspection, etc. It would not be too many of my
hours before the cost of VS would be paid for.
I am glad you have got something to work with, at least!
Paul T.
Post by Paul G. Tobey [eMVP]You're replying to Robert, not to me!
The emulation environment itself is failing, not the operating system
running inside it, so there is no way for the failure handling you describe to
work (the OS never runs, so it cannot display an error). Yes, it is dumb that
the environment does not present a reasonable message telling what the common
causes of the problem are. I presume that, since emulators are just
slightly-valuable tools, not actual targets that you can sell code for, MS
never really did a complete test of every possible set up.
Paul T.
You are a special case. Maybe I am better at generating unusual bugs than you
are! I am sure Rudy will balance more in your direction.
Paul T.
Post by R.WieserHello Paul,
My apologies to you both.
Yes, thats what I ment. I allways assumed that when the
emulator-environment could not create a certain (not quite essential)
component (because of missing dependencies) it would just create a dummy one
instead
break if they would be started on any other computer than my own ...
I think the applicable term is "defensive programming" ?
Regards,
Rudy Wieser
Paul G. Tobey [eMVP] <paultobey _at_ earthlink _dot_ net> schreef in
to
that
common
There does not have to be a connected socket to some other machine, but there
has been a problem where an active and connected network adapter was needed
for networking to function in the emulator. That is, if you had an Ethernet
port on your PC, it had to actually be connected to an active network, or, if
you had a WiFi port, it had to be connected to a network, or if all you had
was dial-up Internet connectivity, you had to connect that. If none of those
were true, network emulation would not work in the emulator. It just has to
do with how the network emulation functions. I thought that that was fixed
around the time of CE4.2, but perhaps not...
Paul T.
Submitted via EggHeadCafe
SharePoint 2010 Using External List
http://www.eggheadcafe.com/tutorials/aspnet/71ee360f-d781-48d6-8243-769d96b45064/sharepoint-2010-using-external-list.aspx