Searching for the right solution

Tech-Archive recommends: Fix windows errors by optimizing your registry


We have a Winforms app built for Vista (vb.net). We will soon be migrating
it to be a full WPF app.

The application currently runs on dedicated\proprietary laptops each
controlling 6 peripherals. So far, we have taken steps to prevent the user
from doing anything on the laptop except running the main app. Obviously,
this application would be better suited and managed in a tightly controlled
embedded environment.

Do to various reasons, we would like to keep the overall structure of our
system the same (laptop + peripherals), but switch to an embedded environment
where nothing but our App is running (no win shell or Windows Applications
available).

This decision was made in the 11th hour. So, we are looking for the
cleanest and simplest transition for the time being. My initial research
focus was on Windows Embedded CE for embedded laptops (thin client units). I
looked into XPe, but again we do not want to rework our Vista app any more
than we have to.

Then I found Windows Embedded Enterprise consisting of Vista Business for
Embedded. Although we would have to use a more netbook\thin-client hybrid
approach, it would alleviate our concern with app reworks and additional
driver development. At the moment, we are not concerned with footprint size.
Therefore, this solution seemed to fit our needs.

In reading more about the WEE platform, I was thrilled to see that it was
geared towards "fixed function" devices such as "kiosks, ATM systems, POS
devices, complex industrial automation controllers, and complex medical
devices.". This statement told me that we could control the User UI by
disabling or changing the Windows GUI or shell. Or at least it seemed.

I queried this group about it and was told that this is not the case. That,
in fact, it was equivalent to the standard pc OS and did not provide controls
by which we could provide our app as the sole functionality and UI of the
system.

What would the experts here recommend in researching this scenario and which
Embedded solution do you think would best address our immediate concerns?

Solution requirements:

1) Must be able to run our current Vista .NET winform app without major rework

2) Use on a small embedded netbook or thin-client laptop

3) The ability to Hide, disable or make inaccessible the windows
desktop\shell\GUI

Hope this makes sense as I am new to the Windows embedded world.

Thanks,
Ken

.

Relevant Pages

  • Re: Searching for the right solution
    ... We have a Winforms app built for Vista. ... controlling 6 peripherals. ... from doing anything on the laptop except running the main app. ...
    (microsoft.public.windowsce.embedded)
  • Re: Deployment under Vista
    ... combination of a special path designated by Windows and the current ... Consequently, under Vista CSIDLs were changed into KNOWNFOLDERIDs, ... Let's call my app Fred.exe and it uses say two random access files, ... The Install suggests that the app is placed in C:\Programs. ...
    (microsoft.public.vb.general.discussion)
  • Re: Deployment under Vista
    ... Outlook apparently does not easily allow me step ... this app works perfectly under XP Home. ... The Install suggests putting the app where you set it to. ... you're breaking the Vista rules by putting data in a Program ...
    (microsoft.public.vb.general.discussion)
  • Re: Deployment under Vista
    ... combination of a special path designated by Windows and the current ... Consequently, under Vista CSIDLs were changed into KNOWNFOLDERIDs, ... Let's call my app Fred.exe and it uses say two random access files, ... The Install suggests that the app is placed in C:\Programs. ...
    (microsoft.public.vb.general.discussion)
  • Re: Searching for the right solution
    ... We have a Winforms app built for Vista. ... controlling 6 peripherals. ... from doing anything on the laptop except running the main app. ...
    (microsoft.public.windowsce.embedded)