I am familiar with visual basic and currently play with vb 2005. I can to some extent create apps for my pocket pc but it seems that the standard syntax for creating and writing to a file on the pocket pc is quite different that that of writing to my computers hard drive.
I have a book on the way but I am struggling to find info, tutorials, or any other support on the web that discusses this.
There is so much vb code on the net for creating apps that run on a pc they practically write themselves. Not for ppc though. The code is sometimes quite different and very hard for me to find. File system code in particular is what I need. For example: Say I want to create a file on my pc harddrive called "steve.txt" and in the file write the name "steve" This is a piece of cake for pc based visual basic but for the pc the syntax changes drastically it seems.
try google books as well. basically you install vb and the pocket pc sdk for the os(s) your aiming your app for. make a build and test it on different devices after your testing in the emulation environment...
try google books as well. basically you install vb and the pocket pc sdk for the os(s) your aiming your app for. make a build and test it on different devices after your testing in the emulation environment...
jd
eMBedded VB isn't needed if you are using VB.Net 2005. You can develop, debug and deploy applications directly from the IDE. All the additional SDK's aren't needed anymore if you have Visual Studio 2005 Standard or better.
Embedded vb is not only no longer necessary but good luck even finding it. It is pretty much obsolete and out of the game. Even though vb2005 can make apps for the ppc it used different language for certain things like writing sequential files to memory for example. For a pc you might use an "Open" statement to create a file. If you select a ppc project in vb2005 though, it simply no longer recognizes "open" as a usable statement. It uses things like "System.IO.file... etc." these appear to be the commands in lieu of normal statements like "open and close."
Embedded vb is not only no longer necessary but good luck even finding it. It is pretty much obsolete and out of the game. Even though vb2005 can make apps for the ppc it used different language for certain things like writing sequential files to memory for example. For a pc you might use an "Open" statement to create a file. If you select a ppc project in vb2005 though, it simply no longer recognizes "open" as a usable statement. It uses things like "System.IO.file... etc." these appear to be the commands in lieu of normal statements like "open and close."
Therein lies my problem.
Well, the main problem you're going to have here is you're simply going to need to learn how the .Net framework operates, that's all. Yes, it's an uphill learning curve but I think you'll figure it out. Sometimes it can be frustrating when you're used to simple constructs like "Open myfile for output as #1". I definitely feel your pain there.
However, even with .Net you can minimize the complexity, you just need to dig a little. Vs2005's IDE sure does make writing PPC code easier. emVB was "OK" but since you were really writing vbscript (in a VB6 IDE) half the functionality simply did not work. The IDE would let you write & compile the code but you had to run it on the device (or emuulator) before you could even find out.
Just go C# :D
File operations aren't that different. It seems most people are using c based languages such as C++ and C#. You'll find much more support if you take the time to learn one of these languages then if you try to stumble around with vb.net.
For Pocket PC I'd really suggest learning C++ as these wimpy processors take so long to load the .NET runtime to start .net applications.
__________________
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. - My Website
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
I don't believe in atheists therefore atheists don't exist.
Just go C# :D
File operations aren't that different. It seems most people are using c based languages such as C++ and C#. You'll find much more support if you take the time to learn one of these languages then if you try to stumble around with vb.net.
I "stumble" around with VB.Net just fine, mate. My rules-engine (which drives a large time&attendance application is completely written in VB.Net). C# is a poor knock-off of the C-language, IMHO. I use both (C# and VB.Net) extensively and if given a choice I'll write it in VB.Net. The IDE implementation of VB is superior with it's incremental compiler and tighter integration with Intellisense.
Choose which language you like guy ... just don't assume that using VB.Net is "stumbling around", please. Some of us (30-year experienced) software professionals just plain like it!
I am familiar with visual basic and currently play with vb 2005.
Sorry CodeBubba, I know VB.net very well also but I was responding to oversteve who sounds like he is stumbling around in it... From my experience (I may not have 30 years but I do have experience) C based languages are much easier for people to learn. When I said stumble around I meant learn on your own. You can't deny that most .NET applications are written in C#, most programming books are in C#, you have java, javascript, actionscript, and many more languages based off of the c syntax. I think it's very worthwhile for every developer to learn how to get around in c style code.
B^)
__________________
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts. - My Website
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
I don't believe in atheists therefore atheists don't exist.
Sorry CodeBubba, I know VB.net very well also but I was responding to oversteve who sounds like he is stumbling around in it... From my experience (I may not have 30 years but I do have experience) C based languages are much easier for people to learn. When I said stumble around I meant learn on your own. You can't deny that most .NET applications are written in C#, most programming books are in C#, you have java, javascript, actionscript, and many more languages based off of the c syntax. I think it's very worthwhile for every developer to learn how to get around in c style code.
B^)
No problem.
No doubt, learning C-like languages is a good idea but that they are "easier" is debatable. Let's just agree to disagree about that. ;)
As far as books go, I've found an adequate number of them using both languages. Seems to depend on the type of subject-matter. I might say that "most" are C#, but I wouldn't say that's a large "most". From what I've found at the bookstore in recent days it might be 55/45 in favor of C#.
Either languages is fine, really - particularly in .Net. They both do, essentially, the same thing.
If you're a VB fan then Basic4PPC would seem to be a very similar fit....
__________________
You'd have thought that someone would have put a sig here To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
VB is easy. .Net is huge and takes a while to learn. At the top of your code page add the line "Imports System.IO.File". Then you can call all the file system objects without having to put system.io.file in front of all of them. "Imports system...." works for any branch of the .NET tree that you are using in your project and make a lot of object calls from.
Imports System.IO.File
Public Class PocketTune
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
System.IO.File.Open("c:\tesst", IO.FileMode.Create)
Open("c:\tesst", IO.FileMode.Create)
SerialPort1.Open()