Actions
Forum Thread Details
  • State Not Answered
  • Replies 13 replies
  • Subscribers 59 subscribers
  • Views 1414 views
  • Users 0 members are here
Related

Need help getting started

Former Member

I have built a small C# windows service application and need to build a small windows OS computer to run the application. The only requirements I need are Mic input, Audio output, Ethernet and I guess monitor, and usb ports for mouse and keyboard for setting up system. Once complete, no need for monitor, keyboard and mouse. The only other requirement I may need is to host a small web application to modify small configurations of the C# windows application.  This is not absolute. 

 

I am not sure what I really need to use or where to start. I can only assume the bare minimal, cost needs to be as low as possible.  Any help would be appreciated.

 

Thanks,
Shawn

  • 0 in reply to xever

    Thanks to everyone for their input, suggestions and help.  Well, I guess I am back to square one again.

    - Shawn

  • 0 in reply to Former Member

    I don't think you are back to square one.  You can continue building the product, and can use the rPi to validate your software and application, this is your prototyping stage anyway.  However, what is being implied with the reply is that you should be cautious on deciding the final platform.  There are strict standards and regulations for such critical systems, and the product should be robust in all its aspects.  The rPi was built as an educational platform, and since you are at this stage, I think using it is not a bad starting point.  Just don't fall into the trap of prototypes ending as final products.

     

    Christever

  • Former Member
    0 Former Member

    Your Windows service program is probably making proprietary calls (Windows service API).  You could wait for Windows 10 on the Pi 2 or you could consider porting your application to Raspbian Linux:

    • C# to C++
    • Windows service APIs to Linux equivalents

     

    It might be fun and a new adventure.  I have done this in the past for a periodic-executing NT service that was already in C++.  My experience:

    • Windows application event log --> Linux syslog
    • Start/stop/exit API and autostart on boot --> /etc/init.d service (start/stop/restart/status)
    • Little things, little adventures