If you do everything by default, the 2.0 JIT compiler will handle the JIT
compilation of the assembly being called. You can dink with this, a bit, but
it gets rather complex. Currently, 2.0 is backwards compatible in most
respects, so this is not an issue. Attempting the other direction is a
problem, however, as there are backwards breaking changes.
--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
************************************************
Think Outside the Box!
************************************************
"Arran Pearce" <arranpearce@NO_SPAMcellhire.com> wrote in message
news:u9****************@TK2MSFTNGP12.phx.gbl...
Thanks for the info.
an extension to this question a bit: If i am running a app (web site or
windows app) in .NET v2. However i referance a assembly which is v1.1.
When i can objects from the v1.1 assembly are they processed by the 1.1
runtime? or v2 runtime?
My assemblys are not strongnamed or in the GAC.
Cowboy (Gregory A. Beamer) [MVP] wrote: You end up having to use the aspnet_regiis tool with the -s flag for
every root that does not fit the 2.0 Framework (at least by default). You can,
of course, set 1.1 to be default and head the other direction.
Currently, 2.0 is beta, so do not install on a production server.