I can give you a few recommendations if you do decide to do it yourself.
Use a parser generator of some sort. If you took computer science classes
in school, you probably used Lex and Yacc. Something similar to that will
make it *much* easier for you, I think, rather than writing a parser
entirely by hand. I happen to have used PCCTS, which you can look up on
the Web, but there are many around, most coming from the academic world.
I've used that for a number of different parsing projects, so I had a head
start in getting it to work and the grammar for a REG file is pretty
simple.
If you're writing your own parser, it's *well* worthwhile to use a
*standard* REG file format. There are lots and lots of things that you
could do a little better than the old REGEDIT4 format, but there are
numerous advantages to using a standard, well-known format (not the least
of which is that you can export a section of the registry in this format
from Remote Registry Editor...
Paul T.
José Joye said:
:-(
Ok, this was the impression I had.
So... Let's have our hands dirty!
- José
"Paul G. Tobey [eMVP]" <p space tobey no spam AT no instrument no spam
DOT com> wrote in message news:%
[email protected]...
You'll have to write one. Our devices have one that I wrote to do that,
but there's nothing from Microsoft to accomplish it.
Paul T.
Hello,
I'm looking (without success so far) for a tool on CE that can read a
".reg file" and update the windows registry accordingly.
Thanks!
José