+ Post New Thread
Results 1 to 9 of 9
  1. #1
    Full Member level 5
    Points: 3,137, Level: 13
    elec-eng's Avatar
    Join Date
    Nov 2006
    Posts
    243
    Helped
    20 / 20
    Points
    3,137
    Level
    13

    Is C# good for embedded applications

    i heard that C# was developed not only for PCs but also for embedded

    but

    Is C# good for embedded applications

    can it be compared to C for size and speed

  2. #2
    Full Member level 5
    Points: 4,114, Level: 15
    Achievements:
    7 years registered
    RBB's Avatar
    Join Date
    Jul 2007
    Location
    USA
    Posts
    304
    Helped
    70 / 70
    Points
    4,114
    Level
    15

    Is C# good for embedded applications

    I've never heard of C# being used for embedded applications. I don't think it is even possible, as it is a managed language.
    For embedded applications you have C or assembly.



    •   AltAdvertisement

        
       

  3. #3
    Full Member level 5
    Points: 3,137, Level: 13
    elec-eng's Avatar
    Join Date
    Nov 2006
    Posts
    243
    Helped
    20 / 20
    Points
    3,137
    Level
    13

    Re: Is C# good for embedded applications

    THIS IS NOT TRUE

    Look at Wikipedia

    http://en.wikipedia.org/wiki/C_Sharp#Design_goals

    They Wrote

    C# is intended to be suitable for writing applications for both hosted and embedded systems,
    but you can say that it is not very popular

    it must take its time to be more deployed



    •   AltAdvertisement

        
       

  4. #4
    Advanced Member level 3
    Points: 8,212, Level: 21

    Join Date
    Jan 2004
    Location
    USA
    Posts
    864
    Helped
    94 / 94
    Points
    8,212
    Level
    21

    Re: Is C# good for embedded applications

    C# can be used only for embedded devices using WinCE with mobile .NET platform like a cellphone or PDA.

    It cannot be used to generate native microcontroller executable.



    •   AltAdvertisement

        
       

  5. #5
    Full Member level 5
    Points: 4,114, Level: 15
    Achievements:
    7 years registered
    RBB's Avatar
    Join Date
    Jul 2007
    Location
    USA
    Posts
    304
    Helped
    70 / 70
    Points
    4,114
    Level
    15

    Is C# good for embedded applications

    I stand corrected. I assumed embedded applications meant native microcontroller code. I forgot about WinCE. I'm a dummy.



  6. #6
    Junior Member level 3
    Points: 1,319, Level: 8

    Join Date
    Feb 2006
    Posts
    26
    Helped
    1 / 1
    Points
    1,319
    Level
    8

    Re: Is C# good for embedded applications

    It is not good for embedded. In embedded we normally use C or Assembly to write embedded application.



  7. #7
    Full Member level 5
    Points: 3,137, Level: 13
    elec-eng's Avatar
    Join Date
    Nov 2006
    Posts
    243
    Helped
    20 / 20
    Points
    3,137
    Level
    13

    Is C# good for embedded applications

    What about C++



  8. #8
    Full Member level 1
    Points: 2,760, Level: 12

    Join Date
    Jan 2002
    Posts
    98
    Helped
    1 / 1
    Points
    2,760
    Level
    12

    Re: Is C# good for embedded applications

    Full featured .NET is an another java + a lot of APIs.

    WinCE only support small subset of .NET, they call it .NET Compact Framework.

    As like the java compiled code, .NET environment is an interpreter.

    But They gave very nice name to it, Managed Code.



    Is an interpreted language adequite for Embedded appications?



    •   AltAdvertisement

        
       

  9. #9
    Newbie level 4
    Points: 1,653, Level: 9

    Join Date
    Dec 2003
    Posts
    5
    Helped
    0 / 0
    Points
    1,653
    Level
    9

    Re: Is C# good for embedded applications

    Quote Originally Posted by visioneer
    Is an interpreted language adequite for Embedded appications?
    It depends on requirements, script languages have been used in embedded applications for a long time (washing machines, pinballs etc.), I'd say interpreted/script languages are suitable for event driven applications with no hard realtime requirements.

    What comes to using C#/Java/OO in embedded systems (other than UI applications) I see a problems: garbage collection (execution is not deterministic), class creation (generates overhead), and fill all your favourite OO-language improvements/features here :D (generates overhead)

    Finally remember this: Project requirements define what tools are needed (it might be OO-language in some cases)



--[[ ]]--