The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: C++ .Net code... Which is easier?


  • Subject: RE: C++ .Net code... Which is easier?
  • From: "Ian Lowe" <ian@xxxxxxxxxxxxxxxxxx>
  • Date: Mon, 6 Dec 2004 14:13:55 -0000


> From: Mal Lansell [mailto:mlansell@xxxxxxx]
>
> I use Visual Studio .NET to build my code - I just don't rely on any
of
> the
> .NET "features" to get anything done.  It should be very
easy to get
it to
> compile for Xbox, but there are a couple of (minor) areas to watch
for:

Good to know, I shouldn't have too many difficulties then :)

> 1) The config items are saved in the registry.  There is code to save
to
> disk instead, but this is currently only used when compiled for
PocketPC -
> you would need to change the #ifdefs to use this on Xbox (I'll make
this
> runtime selectable in the next release!)

Not too bad - the XBMC has a nicely defined mechanism for getting
configuration information - there's the xml file for main config items,
and a SQLLite DB for the more involved stuff. It's probably best to be
xbmc-friendly in the storage of config options.

> 2) I use Winsock, but I don't know what is available on Xbox (well, I
know
> what's in the official XDK, but are you using that or running some
Linux
> variant?)

Nope, it's the official XDK alright - and xbmc seems to have a specific
xwinsock class exposing all the functions needed to send/receive
messages.

> When you get it working, it might be nice to roll your changes back
into
> the lib - the more platforms the merrier ;-)

I'll await the public scrutiny with trepidation!

Ian.




xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.