Re: Speed of C# and GDI+

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: PPC JK (gnlincoln_at_msn.com)
Date: 05/07/04 

Date: Fri, 7 May 2004 09:27:02 -0400

Since a eVC++ DLL is involved here, CPU dependence is back in? If this
trade-off for speed is necessary, while not compile the C# or eVB code to
native binary exe to avoid the JIT MSIL compiler phase? Is there a
way/option of doing this?

"Kartal" <keturkarslan@hotmail.com> wrote in message
news:a5d88922.0405070243.5490c21c@posting.google.com...
> Hi Mateusz,
>
> .NET CF compiler generates MSIL code which is a CPU independent
> intermediate code. .NET CF converts MSIL code to appropriate machine
> code when managed method executed for the first time. However this
> conversion does not cause a very big performance issue for most of the
> applications. At the end you are actually running the machine code,
> .NET CF is not an interpreter. However .NET CF is a framework between
> the operating system and your application. I can neglect the overhead
> of that the framework layer but it may not be acceptable for your
> applcation.
>
> I would suggest you to develop two small test applications and measure
> the performance between.
>
> I prefer .NET CF as it abstracts the hardware differences and
> eliminates problems such as byte alignment etc. So you do not need to
> test on different platforms and single code runs PPC 2003 and PPC
> 2002. Designing the UI and implementing the application is also very
> simple.
>
>
> If it is acceptable to draw the screen after completing all the
> processing and drawing, there is also third option.
> You can do all you geometry processing in an eVC++ dll.
> Within that DLL you can paint everything to a memory DC.

Relevant Pages

  • Re: Speed of C# and GDI+
    ... Since a eVC++ DLL is involved here, CPU dependence is back in? ... native binary exe to avoid the JIT MSIL compiler phase? ... .NET CF converts MSIL code to appropriate machine ...
    (microsoft.public.pocketpc.developer)
  • Re: Exposing bool to non-MS, non-C++ callers
    ... the functions in this DLL accept a structure as an argument. ... The compiler doesn't help catch places where I neglect ... the C++ bool type is defined as one byte. ... depends on whether the Exe caller will push a value larger than 1 byte. ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Memory allocation methods
    ... all modules are compiled against the same CRT' DLL with the same compiler. ... that case you restrict yourself to a simple C-based API for the DLL. ... I prefer to use either exceptions (but writing exception-safe code is quite ...
    (microsoft.public.win32.programmer.kernel)
  • COBOL Compiler options
    ... calls to CICS. ... we do not document this DLL problem nor have compiler options ... use of DLL's with the integrated translator (for cases where it is valid ...
    (bit.listserv.ibm-main)
  • Re: Export class from dll
    ... Remember that C++ classes describe not only the general characteristics of ... Only when the DLL ... about the compiler not knowing the details of a CBox, ... How does the compiler know what CBox is? ...
    (microsoft.public.windowsce.embedded.vc)