scheduled for late 2006.
Backwards compatibilityIn response to a question about backward compatibility, Andy Allred, Test Manager for Windows Embedded, said that code developed for LHe that has dependencies satisfied in XPe "should" work.
"We are trying to maintain backwards compatibility with EEFs (Embedded Enabling Features) wherever possible, so perhaps some new LHe EEFs will be backported to XPe," commented Allred. However, he also pointed out that there may be new EEFs or features that leverage technologies only available in Longhorn and these won't be compatible with XPe.
Same codebase, consistent skill setsJay Kramer, Program Manager for Embedded, noted that LHe and LH Pro will share the same codebase so that developer skills or tools applicable to one will work for both.
"Keeping these skill sets the same is one of our primary goals in XPe and LHe," said Kramer.
Command line build utility?Another chat participant asked if LHe would have a command line build utility, adding that this would "help immensely in our development cycle."
Allred noted that this is a common request. "While we're not ready to discuss the details of LHe here, the ability to build from a command line is high priority," he said.
A work in progressKramer said that the embedded group is "always listening for feedback on what features we should be looking at adding or enhancing for our next release."
The feedback link is
here.
Related stories: 
