Friday, 8 May 2009

.NET Micro Framework moves to Developer Devision

The .NET Micro Framework Team has posted some interesting news on their blog with regard to the current rumors around .NET MF.

The .NET Micro Framework Team is moving into the Developer Devision and is additionally thinking about new business models including a larger engagement of the community; however Microsoft will carry on providing initial guidance and the necessary tools - from my point of view a necessary prequisite if the .NET Micro Framework is still to be a success.

Stay tuned as the exact business model is to be defined in the near future.

So long and thanks for all the fish!
Read more! Post this to a friend!

Thursday, 7 May 2009

.NET Micro Framework code to be given to the community?

Rumor, has it that Microsoft is planning to give the source code for the .NET Micro Framework to the community and shall be withdrawing from this business. As for the financial business model it is said that royalties will be terminated and the porting kit will be made available free of charge.

Microsoft will however carry on supporting existing customers as well as hold on to their lifecycle support pledge. New customers, wanting to sport their devices with the .NET Micro Framework are then to be supported by the community.

The question is (if the rumor is true): Are we looking at the beginning of the end of the .NET Micro Framework or will this blow new life in to it? And I guess only the exisiting community around the .NET Micro Framework can give the answer to this.

So long and thanks for all the fish!
Read more! Post this to a friend!

Windows Embedded CE 6.0: Catalog file issue

Hi folks,

you might have noticed, that the new catalog file format in Windows Embedded CE 6.0 does not have a GUID as a unique identifier anymore. Instead the unique id is now a string. When using the Catalog Editor to create a new catalog item, it will check whether this id is unique and tell you so if it isn’t. However if you switch to the source view to edit your catalog item, this check is no longer performed. Now if you specify a unique id that is in fact not unique, your catalog item will no longer appear in the catalog nor will any subdirectories you might have created be displayed anymore in the Catolog Editor.

To avoid this problem of multiple unique identifiers it is recommended that you choose your unique id as follows:

Item:<Vendor name>:<unique description>:<BSP name>

Have fun!
Read more! Post this to a friend!

Wednesday, 6 May 2009

Windows Marketplace for Mobile

Hi folks,

Microsoft has just started their Windows Marketplace for Mobile. Thereby Microsoft enables Windows Mobile application developers to easily manage and distribute their applications. If you want to post your application you need a valid tax number and a Windows-Live ID. Furthermore you need to pay $99 US for up to 5 applications and an additional $99 US for each additional application and acknowledge the “Application Provider Agreement”. Now you can distribute your application. In return you get 70% of the profit from your applications.

The Marketplace itself will be launched in the second half of 2009 as a competitor to similar offers form Apple and Google.

Further information can be found at the Marketplace’s FAQ page.

Have fun!
Read more! Post this to a friend!

Free Onsite Windows Embedded ½ Day Workshops Sydney, Australia on the 1st Thursday of every month

Hi Folks,

Don’t miss the next upcoming free Windows Embedded ½ Day Workshops held in Sydney, Australia on May 7th 2009 and on the first Thursday of every month.

Location:
Ground floor-Microsoft
1 Epping Rd, North Ryd
NSW (Exit off Delhi Rd)
Sydney, Australia

Description:
Microsoft will be hosting a Windows Embedded Workshop on the first Thursday of every month. Join us and receive the latest information on Microsoft Windows Embedded products, with a special focus on Windows Embedded Standard. (Formally known as XP Embedded) This workshop is to help you better understand the features and benefits of Windows Embedded, and how you can deploy it on your embedded systems. This workshop sponsored by DSTA is held especially for Embedded Systems Engineers/Developers, Project Managers, Technical Decision Makers and others who are interested in using Windows Embedded in their current or future projects.

This is a great opportunity for you to learn how to integrate Windows Embedded technologies with your custom platform, and learn effective techniques to rapidly bring your products to market. We will demonstrate the process of Windows Embedded Standard image creation using Embedded Toolkit on a Virtual PC as well as on the real hardware.

Further information:
http://www.microsoftembeddedseminars.com/about.aspx?seminarid=231

Overview of MS seminars offerings:
http://www.microsoftembeddedseminars.com/home.aspx

Have fun!
Read more! Post this to a friend!

Tuesday, 5 May 2009

Microsoft Auto 4.0 RTM released

Hi folks,

Microsoft released its next-generation in-vehicle platform Microsoft Auto 4.0 RTM (codename Bristol). As Microsoft Auto 3.0 and 3.1, Microsoft Auto 4.0 is again a PDK that installs on top of Windows Embedded CE 6.0 R2. New features include:

  • Added support for Intel Architecture Processors including Atom Z5xx series which offer an industrial temperature range (ARM- and SH-based processors were already supported in MS Auto 3.1).

  • Common head unit functionality such as standard interfaces for broadcast radio tuners and standard for CD playback and ripping
These new features enable developers to create integrated multifunction systems with reduced complexity, lower cost and faster time to market.

Microsoft also launched a new worldwide partner program. If you read our previous posts on Microsoft Auto you already know that EB is among the first certified training partners for MS Auto to provide technical education to help automakers and suppliers deliver the next innovations in vehicle
  • Infotainment

  • Navigation

  • Communication
Devices.

If you want more information, check out www.microsoft.com/auto.

Have fun!
Read more! Post this to a friend!

Friday, 1 May 2009

Windows CE and SDK names

Hi folks,

imagine the following scenario: You, as an application developer for Windows CE, get yet another Custom Platform SDK from your BSP vendor. So far so good but upon installation of this particular Custom Platform SDK you see that its installation name is something totally generic like “WinCE SDK (ARMV4I)”. This wouldn’t really pose a problem if it was the only Custom Platform SDK installed on your machine. But as you can easily see it will be a huge problem if you have 5, 10 or even more Custom Platform SDKs installed. Now it is nearly impossible to remember which SDK belongs to which platform.

So is there a way to rename a Custom Platform SDK upon installation without asking the BSP vendor for a new one with an appropriate name? We tried different things to figure out a solution for this problem:
  • Looking for the name of the Custom Platform SDK in the registry – unsuccessful

  • Patching the SDK .msi installer file with Orca – unsuccessful

  • Studying the SDK installation process with Sysinternals Process Monitor – BINGO

Names and other information about installed Windows CE Custom Platform SDKs can be found in the file:
C:\Program Files\Microsoft Visual Studio 8\VC\vcpackages\WCE.VCPlatform.config
All you need to do after changing the name in the above file is to restart Visual Studio and your Custom Platform SDK will appear with your new name.

As you can see it is important for BSP developers to always export Custom Platform SDK with descriptive names!

Have fun!
Read more! Post this to a friend!