Windows CE .NET Interview Questions & Answers

Windows CE .NET Interview Questions

Do you like to switch your career? Here's our recommendation on the important things to need to prepare for the job interview to achieve your career goals in an easy way. Windows CE .NET is a version of Operating System where it is used in space constraint devices like mobile phones. For that the devices should have at least 4MB ROM, 2MB RAM, PC slot, and should weigh less than 1 lbs. Demand to this technology is increasing every day. There is huge demand for jobs related to Windows CE .NET anywhere. One can check the availability of the job across cities including Mumbai, Delhi, Bangalore, Pune and Hyderabad. Follow Wisdomjobs page for Windows CE .NET job interview questions and answers page to get through your job interview successfully.

Windows CE .NET Interview Questions And Answers

Windows CE .NET Interview Questions
    1. Question 1. Can Platform Builder 3.0 And Platform Builder 4.0 Coexist?

      Answer :

      There should be no problem with this as long as they are installed to separate directories.

    2. Question 2. Explain What Are The Levels In Wince Architecture?

      Answer :

      There are four levels in Win CE architecture:

      1. Hardware layer
      2. OEM layer
      3. OS layer
      4. Application layer

    3. Question 3. What Are The Sdks Developed By Wince?

      Answer :

      MSFT standard SDK's are,

      1. Windows Mobile for Smartphone = Windows Mobile Standard.
      2. Windows Mobile for Pocket PC = Windows Mobile Classic.
      3. Windows Mobile for Pocket PC Phone Edition = Windows Mobile Professional.

    4. Question 4. What Is Ce Stands In Wincce?

      Answer :

      Windows CE (also known officially as Windows Embedded Compact post version 6.0, and sometimes abbreviated WinCE) is Microsoft's operating system for minimalistic computers and embedded systems. Windows CE is a distinctly different operating system and kernel, rather than a trimmed-down version of desktop Windows. It is not to be confused with Windows XP Embedded which is NT-based

    5. Question 5. Can You Explain What Is The Specialty Of Wince?

      Answer :

      • WinCE supports both Hard real time as well as soft real time environment depends on what processor we are using and with what configuration. 
      • Using Platform builder tool one can make this WinCE OS as customise O S to his hardware. Which is one of good  advantage over other OS.
      • We can make as compact as possible O S image just by adding required component (along with sample code) only in customize OS Designing.

    6. Question 6. Do You Know What Is Device Driver?

      Answer :

      A driver is fundamentally a piece of software written for a specific device. Its main tasks are to perform I/O's on a device. To do this there are typically well defined models for a driver.

      Generic description of a driver structure will be:

      1. Device I/O Address (Physical Hardware -> Logical OS based address)
      2. Interrupt that the device generates and its handler (the driver)
      3. A software Handler to manage the read write operations to and fro from the device.

    7. Question 7. What Is The Main Difference Between Wince4.0 And Wince5.0 Is There Any Speciality?

      Answer :

      speciality in the sense:

      1.  number of processes supported by wince 5.0 is more than wince 4.0
      2.  memory mapping might be varying.

    8. Question 8. Explain What Are The Advantages And Disadvantages Of Wince Compared To Gpos?

      Answer :


      1. Supports various types of processor platforms
      2. Possible to Customize the Kernel and can reduce its size (upto ~300KB kernel size)
      3. Especially for the embedded device platforms


      1. Process limits, max. 32 process at a time in WinCE 5.0
      2. Limited space allocation for each processes, 32MB/each process

    9. Question 9. What Version Of Wince Supports Dual Core Processor?

      Answer :

      Only windows embedded compact 7 will support dual core.

    10. Question 10. What Is Windows Ce?

      Answer :

      Microsoft Windows CE is an open, scalable Windows platform for a broad range of communications, entertainment, and mobile-computing devices. The standards-based Windows CE platform is an entirely new operating system, built from the ground up to make possible new categories of business and consumer non-personal computer devices that can communicate with each other, share information with Windows-based personal computers, and connect to the Internet.

    11. Question 11. Why Did Microsoft Develop Windows Ce?

      Answer :

      For the past few years, Microsoft has outlined its vision of "Information at Your Fingertips", in which the idea of a personal computer on every desk and in every home evolved into one of computer-based devices in a variety of business and consumer environments. The Windows CE operating system is the result of a multi-year development effort to fulfill that vision.

      With Windows CE, Microsoft is providing an open, standards-based platform that will significantly lower the hurdles for original equipment manufacturers (OEMs), hardware manufacturers, software developers, and ultimately, customers to adopt new non-PC technologies and solutions.

    12. Question 12. What's The Difference Between Windows Ce 3.0 And The Pocket Pc?

      Answer :

      Windows CE is an operating system shipped as a set of building blocks. Pocket PC is a specific device built from these Windows CE building blocks. The Windows CE 3.0 operating system running on Pocket PC and Pocket PC 2002 devices is not, therefore, equivalent to the Windows CE 3.0 operating system running on other devices.

    13. Question 13. What Is Microsoft Windows Ce .net?

      Answer :

      Microsoft Windows CE .NET is the successor to Windows CE 3.0. It is the robust, real-time operating system for rapidly building the next generation of smart mobile and small footprint devices. Windows CE .NET works on four major CPU architecture families and on over 200 CPU types, and is used in a broad range of device types including: PDA (mobile handheld), Windows Thin Client, Smartphone, Web Pad, Internet/Media Appliance, Set-Top Box, Residential Gateway, Retail Point-of-Sale (POS), and Industrial Automation Device. Because Windows CE .NET is highly modular, footprint size can be customized to meet the specific product requirements of a range of devices.

    14. Question 14. Why Should I Build An Embedded System On Windows Ce .net And Not Linux?

      Answer :

      Windows CE .NET delivers a feature-rich, comprehensive, integrated embedded operating system platform, supported by an experienced and growing worldwide infrastructure of partners and developers that enable an OEM to get to market faster, utilize limited resources for product differentiation—not operating system development and maintenance—and protect their value-added intellectual property with a known, trusted vendor and business model.

      Windows CE. NET includes over 400 professionally-tested lightweight configurable components, a hard real-time and preemptive multitasking kernel, rich wireless, multimedia, browsing and power management functionality, and built-in support for over 200 different 32-bit CPUs spanning the ARM, MIPS, SuperH (SH), and x86 architectures.

    15. Question 15. What Kinds Of Devices Are Possible With Windows Ce .net?

      Answer :

      It is possible to build customized platforms for a wide variety of devices using Windows CE .NET.

      The new Platform Wizard, included in Windows CE .NET, includes a set of preconfigured platforms for the following targeted devices to help jump-start your development process:

      • Cell Phone/Smartphone Device
      • Custom Device
      • Digital Imaging Device
      • Industrial Automation Device
      • Internet Appliance
      • Media Appliance
      • PDA/Mobile Handheld Device
      • Residential Gateway
      • Retail Point-of-Sale (POS) Device
      • Set-Top Box
      • Tiny Kernel
      • Web Pad
      • Windows Thin Client

    16. Question 16. What Does The Windows Ce .net Emulation Technology Allow You To Do?

      Answer :

      Windows CE .NET emulation technology enables developers to build and test their design on their Windows 2000 or Windows XP-based workstations without having to purchase any additional hardware.

    17. Question 17. What Is Ipv6?

      Answer :

      Internet Protocol version 6 is a new industry networking protocol that supports a much larger address space. You now have a choice between IPv4 and IPv6, including IPv6 versions of network components such as Internet Explorer 5.5 and Windows Media, to name just a few. Windows CE .NET also includes a number of technologies that enable interoperability and testing of dual stack networks to support the transition period from IPv4 to IPv6.

    18. Question 18. How Do The File Viewers For Windows Ce Compare To The Applications Included With The Pocket Pc Platform And Handheld Pc?

      Answer :

      Windows CE .NET includes a set of File Viewers that allow a user to view and print native Microsoft Office and Adobe Acrobat documents. This contrasts with the Pocket applications available on the Pocket PC and Handheld PC platforms, which allow you to edit documents after converting them using Microsoft ActiveSync® technology. The File Viewers in Windows CE .NET, while not providing editing capabilities, can be used on a Windows CE .NET device without requiring ActiveSync or file conversion.

    19. Question 19. How Do I Remotely Manage Devices Built With Windows Ce .net 4.1?

      Answer :

      Windows CE .NET 4.1 adds a new device management client to complement the existing SNMP v 4.2 client. When the corresponding system management software (SMS) 2003 server is released, this new SMS 2003 client will enable enterprise management features such as hardware/software inventory and software deployment, thereby strengthening customers' software distribution and asset management. We have included the SMS 2003 client in advance of the SMS 2003 release, given that many customers require additional time for testing and deployment. For customers who wish to build their own server to use with the SMS client, Windows CE .NET 4.1 ships with documentation about the client and the protocol.

    20. Question 20. What If I Am Partway Through A Project And I Do Not Want To Upgrade To The Latest Release Of Windows Ce .net?

      Answer :

      Developers have a choice of either installing the latest version alongside the previous version of Windows CE .NET, or upgrading to the latest version. If you choose side-by-side development, any new projects should then be started with the latest version of Windows CE .NET. The upgrade can read projects and workspaces from the previous version of Windows CE .NET and convert them to the version 4.1 format on first save. However, changes made in the latest version cannot be saved to the previous version.

    21. Question 21. What Is The Minimum Footprint For Windows Ce .net?

      Answer :

      Continuing the effort to minimize the OS footprint for embedded devices, Windows CE .NET core kernel functions are selected on a feature-by-feature basis, so minimal implementation of Component Object Model (COM)/XML is possible. The minimum configuration can be as small as 200 KB, and is supported through granular networking, multimedia, and browser technologies, in addition to high compression font storage.

    22. Question 22. What Is The ".net" In Windows Ce .net?

      Answer :

      Microsoft .NET is a set of Microsoft software technologies for connecting your world of information, people, systems, and devices. It enables an unprecedented level of software integration through the use of Extensible Markup Language (XML) Web services: small, discrete, building-block applications that connect to each other

      In addition to other, larger applications—via the Internet. .NET connected software delivers what developers need to create XML Web services and stitch them together.

      The benefit to individuals is a seamless, compelling experience of sharing information. .NET technologies implemented in Windows CE .NET include XML, Simple Object Access Protocol (SOAP), Microsoft Passport, Microsoft Windows Messenger, and the Microsoft .NET Compact Framework, which increase developer productivity.

    23. Question 23. What Is The Licensing Model For Windows Ce .net?

      Answer :

      The licensing process for Windows CE .NET involves two steps: acquiring the Windows CE .NET toolkit to begin building your device image, and purchasing a runtime license for each device that you will distribute which contains the image. With the latest release of Window CE .NET, Microsoft has introduced a new runtime license.

    24. Question 24. When Should I Use Windows Ce .net Rather Than The Microsoft Windows Xp Embedded Operating System?

      Answer :

      The Microsoft strategy is to offer a broad range of Windows-based, embedded-operating-system solutions to meet the diverse needs of customers. Ultimately, the design requirements of your device will determine the best platform to choose. Understanding the development focus of each operating system also may assist you in making this decision.

      • Choose Windows CE .NET for solutions requiring real-time, small-footprint, and multiple-processor support.
      • Choose Windows XP Embedded for solutions requiring the latest Windows technologies built on the x86 processor.

    25. Question 25. Why Should I Use Windows Ce .net Rather Than Just Staying With Previous Versions Of Windows Ce?

      Answer :

      The advancements of Windows CE .NET over previous versions are significant. Windows CE .NET offers a wide range of technologies that developers would previously have had to implement themselves, such as 802.11 or Kerberos support, to name a few. Windows CE .NET, therefore, makes it easier to build more advanced devices and get those devices to market faster, with improved developer productivity.

    26. Question 26. How Do I Write Applications For Windows Ce .net?

      Answer :

      To write applications for Windows CE .NET, Microsoft offers a rich set of languages for creating managed (.NET) or native (unmanaged) applications. Use Microsoft Visual Studio .NET to write managed code or use eMbedded Visual C++ to write native code.

    27. Question 27. Can I Use Embedded Visual C++ 3.0 To Write Applications For Windows Ce .net?

      Answer :

      No. You will need eMbedded Visual C++ 4.0 to write applications. This product is included with Windows CE .NET.

    28. Question 28. Will Applications Created Using Embedded Visual Basic 3.0 Run On Windows Ce .net?

      Answer :

      No. Applications created using Microsoft eMbedded Visual Basic® 3.0 will not run on Windows CE .NET. Developers who want to write new applications using Visual Basic will be able to use Visual Studio .NET with Visual Basic .NET.

    29. Question 29. Why Would I Use Visual Studio .net Instead Of Embedded Visual C++ To Write Applications?

      Answer :

      The type of application being created will dictate the choice between native and managed code (.NET). When performance and control are the number one priorities, developers should turn to eMbedded Visual C++, or native code. When a consistent programming model and time to market are the primary considerations, the advantages offered by Visual Studio .NET are unequalled.

    30. Question 30. What Is C# (c Sharp)?

      Answer :

      C# is a new application programming language designed specifically to take advantage of the .NET Compact Framework.

    31. Question 31. What Is The Microsoft .net Compact Framework?

      Answer :

      The .NET Compact Framework is a subset of the Microsoft .NET Framework designed for footprint-constrained devices. The .NET Compact Framework is a hardware independent program execution environment for downloadable applications targeting and optimized for resource-constrained computing devices. It also offers a choice of languages (initially Visual Basic and Microsoft Visual C#™), and eliminates the common problems faced with language interoperability.

    32. Question 32. Why Should I Include The .net Compact Framework In The Operating System Configurations That I Build Using Windows Ce .net?

      Answer :

      There are numerous benefits to including the .NET Compact Framework on your device. From an end-user perspective, having the .NET Compact Framework on a device expands the number of rich applications and Web services to take advantage of. From a developer perspective, the inclusion of the .NET Compact Framework simplifies and reduces the development process, thereby increasing developer productivity.

      The .NET Compact Framework offers a choice of languages (initially Visual Basic and Visual C#) and eliminates the common problems faced with language interoperability.

      For example, Visual C# and Visual Basic components can easily co-mingle within a solution, thereby enabling a broader set of applications that can run on your device. In addition, every language supported by the .NET Compact Framework has equal access to the underlying features of the framework and the OS. The .NET Compact Framework also makes a rich framework available to programmers, including user interface classes, data access, XML support, automatic memory management, and garbage collection.

    33. Question 33. How Big Is The .net Run Time When In Windows Ce .net?

      Answer :

      While work on the .NET Compact Framework is not complete, currently the run time is approximately 2 megabytes (MB), compared with the 1.3 MB runtime that enabled eMbedded Visual Basic applications to operate.

    34. Question 34. Will .net Compact Framework Applications Perform As Well As Embedded Visual C++ Applications?

      Answer :

      In most cases, applications written with eMbedded Visual C++ will run faster than those written using Visual Basic .NET or Visual C#. However, for computationally-intensive portions of their application, developers will see a substantial improvement of their Visual Basic .NET applications over their eMbedded Visual Basic equivalents.

    35. Question 35. Why Isn't Embedded Visual C++ Integrated Into Visual Studio .net?

      Answer :

      Based on customer feedback, our initial efforts have been focused on enabling Visual Basic users to more easily program devices. However, the ability to create device applications using native code (C++) will ultimately be integrated into Visual Studio .NET.

    36. Question 36. Do I Have To Enable .net On My Platform?

      Answer :

      No. Enabling .NET on your platform is optional. However, including the .NET Compact Framework in your platform has a number of benefits. The .NET Compact Framework is a subset of the popular .NET Framework and is fully supported by Visual Studio .NET 2003. It enables millions of Visual Studio .NET developers to quickly and easily target your custom platform using skills that they already know. Second, the .NET Compact Framework provides a powerful, XML Web Services enabled execution environment for your platform, including support for Windows Forms, Microsoft ADO .NET data access, networking, and more.

    37. Question 37. What Is The New Source Code That Is Being Delivered In Windows Ce .net?

      Answer :

      Shared source now includes the Windows CE .NET Test Kit (CETK). This is the component developers use to automate their testing and troubleshooting of Windows CE .NET devices, and is a key piece of code that developers have been asking for.

    38. Question 38. Is The Shared Source The Same Across The Downloadable Evaluation And Emulation Editions And "in The Box"?

      Answer :


    39. Question 39. How Can I Check The Priority For A Running Thread?

      Answer :

      You can check thread priorities in the debug shell with the command "gi thrd" or by using Platform Builder's threads window.

Popular Interview Questions

All Interview Questions

All Practice Tests

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd Protection Status

C#. NET Tutorial