N. T. wrote:
> Bob Ammerman wrote:
>> I incorrectly stated that the translation to native code could happen at
>> development time. I apparently am mistaken. It can only be done at (or
>> after) installation on a target computer. See the "NGEN" utility.
>
> I am not an expert in all that "NGEN" / "JIT" things, but from the
> basic logic if "translation to native code can't happen at development
> time", how could be possible to run apps under development, that is
> from Visual Studio?
>

Adding to my own post...
Talking about "development time", It looks like even very Visual
Studio is not necessarily =93NGEN=92d=94 when installed:

http://weblogs.asp.net/scottgu/archive/2010/04/12/visual-studio-2010-and-ne=
t-4-released.aspx
***
The VS 2010 and .NET 4 installs add a bunch of new managed assemblies
to your machine.  Some of these will be =93NGEN=92d=94 to native code durin=
g
the actual install process (making them run fast).  To avoid adding
too much time to VS setup, though, we don=92t NGEN all assemblies
immediately =96 and instead will NGEN the rest in the background when
your machine is idle.  Until it finishes NGENing the assemblies they
will be JIT=92d to native code the first time they are used in a process
=96 which for large assemblies can sometimes cause a slight performance
hit.

If you run into this you can manually force all assemblies to be
NGEN=92d to native code immediately (and not just wait till the machine
is idle) by launching the Visual Studio command line prompt from the
Windows Start Menu (Microsoft Visual Studio 2010->Visual Studio
Tools->Visual Studio Command Prompt).  Within the command prompt type
=93Ngen executequeueditems=94 =96 this will cause everything to be NGEN=92d
immediately.
***

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.