CLR is not just something that blindly interprets IL instructions. IL
instructions by themselves are useless. Just like any language is useless on
it's own. It's all about runtime and libraries that provide various services
such as forms, graphics, printing, encryption, the whole CAS (code access
security model), garbage collection, web services, remoting, versioning,
cross language interaction, etc etc etc. That, as you might guess, is what
the "Fat" .net framework is about. I'm not going to list many many other
things that .NET provides. Running .Net apps inside a browser VM would suck
performance wise.
It's very far from simple HTML/Browser concept.
"feng" <gi******@ms1.u rl.com.tw> wrote in message
news:O2******** ********@TK2MSF TNGP09.phx.gbl. ..
The SmartClient is a good idea, but there are some drawback.
1. It requires that the "Fat" .NET Framework be installed
2. It's hard to build full-featured applications without configing the
security policy of the client.
If IE contain CRL that can interpret the small set of IL
instructions... . 1. Gain the .net power to develop rich-web client
2. It is possible to across platform(Browse r) just as HTML.
"Carl Daniel [VC++ MVP]" <cp************ *************** **@mvps.org.nos pam>
¦b¶l¥ó news:uu******** ******@TK2MSFTN GP09.phx.gbl ¤¤¼¶¼g... Why don't IE become a thin .Net VM?
1. Who says it won't?
2. Strictly speaking, .NET isn't based on a VM, but on a runtime
environment.
-cd
