Would you like to help improve the next version of Windows Embedded?
The Embedded Windows team works hard to provide customers with the best quality experience. We gather feedback by holding customer calls, attending events, conducting surveys and reviews, and by employing other types of feedback mechanisms.
However, limitations in time and resources make it is impossible to collect all the feedback customers have about our product. This sometimes makes it challenging for us to know where to direct our efforts (e.g., What features to further componentize or how to improve the quality of tools such as Target Designer).
A number of Microsoft products provide users the opportunity to participate in the Customer Experience Improvement Program (CEIP). CEIP enables all users to provide automated feedback about a particular Microsoft product. All a user has to do is opt-in (agree to help Microsoft) and usage data is automatically collected about the products usage.
This feedback is then used by Microsoft to help improve the quality, reliability, and performance of Microsoft software and services. It does so by collecting information from you – the customer – that help us identify the features you use most and identify the most common problems encountered.
We are currently brainstorming if CEIP should be included in future versions of the Embedded Windows developer tools. We would be interested in collecting data to help us better understanding things such as
- What are the most common components our customers are shipping?
- What are the common third-party drivers being included?
- How often are the various tool features (e.g., Help, Visibility Settings, etc.) being used?
- What kind of tool error/warning messages are users encountering the most?
Participation would be completely optional and would only be included with the developer tools and NOT on the runtime image.
So the question for you is, if we included CEIP in future versions of our development tools, would you choose to opt-in (agree to send data to the Embedded Windows team about how you use the tool)? If not, why not?
- Randy
Comments
Anonymous
August 17, 2007
Would you like to help improve the next version of Windows Embedded? The Embedded Windows team works...Anonymous
August 24, 2007
At work, I'm a .NET developer. At home, I'm a .NET developer. But when it comes to embedded programming, I'm a Linux developer. Listen carefully. I use and program Mac, Linux and Windows, but I always champion Microsoft products. Except when it comes to Windows Embedded. To convert me to Windows embedded platform, I need a FREE embedded dev/tool-kit (or one that costs no more than $99 retail - that's the magic price point). You have free versions of Visual Studio and SQL Server Express. Why on earth can't you have a FREE or low cost Windows embedded dev/tool kit. Can you do this? At least for x86 systems? And without removing any ease-of-programming features? By the end of the 2007 calendar year? That's what I want to know! Otherwise, it's back to Linux. Thanks and Godspeed!Anonymous
August 24, 2007
ShermB, We do have a free trial version for your download. The dev/tool-kit never expires while the run-time expires in 120 days after the first deployment. You can download here: http://www.microsoft.com/windows/embedded/eval/trial.mspx. Actually our team (to be exact, myself) is investigating on this very issue: how can we improve hobbyists' experience? what we can do for them? If you have more to share on the need, or other comments, we would love to hear. It'll greatly help us to build the business case. You can email us at wecrt@microsoft.com. Thank you! WeijuanAnonymous
September 06, 2007
Weijuan, thank you for your response (I've been on vacation).
- Does "run-time expires" mean that I cannot continue to delpoy updates to a device and expect the device to work after the trial period has ended? Even if the device is developed for personal use?
- I know that this is probably not the right place to bring up the following issue, but here it is. The Windows Embedded Training Partner Program requires a minimum of two trainers to attend Train-the-Trainer (TTT) sessions. From my viewpoint, requiring two trainers appears to be an arbitrary requirement. As a consultant (and former instructor), why can't I -- just one person -- gain access to the benefits of the Training Program? Why is Microsoft discriminating against sole proprietors or other businesses that are only interested in training a single employee. TTT should at least provide for the potential of allowing an Exception for some companies (sole proprietor) or individuals (say a community college professor) or similar situations. Thanks for any help you can provide. (fyi: I've also sent this question via Windows Embedded Contact Us)
- Anonymous
September 10, 2007
ShermB, Hope you had a good vacation. Here are answers to your questions:
- When the run-time built from the trial version expires, it'll bug check (or blue screen). You can not boot the run-time any more. It doesn't matter if it's developped for personal use or not.
- I'll forward your feedback to our Marketing peers in charge of the partner/TTT program. If I hear any response from them, will let you know. Weijuan
- Anonymous
September 11, 2007
ShermB brought up a question about the Windows Embedded training program, which provides training partners with free curriculum for Windows XPe and Windows Embedded CE. Our top priority is to ensure a quality experience for the developers seeking training. Requiring a two-trainer minimum is meant to ensure a strong commitment to Windows Embedded training. Ideally developers can find training classes on a regular schedule, nearby, from quality trainers, throughout the year. We have made exceptions for great companies or universities doing great work, and will continue to do so on an as-appropriate basis. If you're interested, go ahead and request a Training Partner Application from mswepp@microsoft.com. It'll get sent to me, and we can talk. Thanks, Sondra Webber Sr. Marketing Manager Windows Embedded Partner Program