Are you saying the CLR is interpreted? You might want to read up on its architecture if you think so. Then you would know that the IL is jitted into machine language as needed.
I do believe that when SQL server uses the CLR that T-SQL will become another CLR language, and it should be interesting to see how they handle data manipulation in other languages like c#, but using something like ado.net makes sense. Remeber that in SQL server 7 and above the engine itself uses OLEDB, so it wouldnt be that hard to imagine any CLR using that directly and effeciently, perhaps it might even be converted to use the SQL manage provider.
Its also not hard to imagine that the stored query plans will function like asp.net and acutally be compiled CLR code that was created by the optimizer using the codedom, or perhaps just emitted IL code. In any case I think we will see some very interesting stuff when MS starts using the CLR in SQL server.
Its seems like most people here you do not understand what.Net is, and it is Microsoft's fault to some degree..Net does completely fix dll hell, the.net framework and clr where designed around "xcopy" deployment, meaning no more registry, xml config files in the app directory (novel idea;)). In fact it makes me wonder about how the registry will be used as time goes on. But anyway my main piont is.Net is being marketed centralized applications that are rented, but in reality that is just one way to use the underlying framework, and at the same time it is Microsoft "eating there own dog food", by using the framework for that purpose. But it you still prefer to make a classic windows app the.Net framework gives a excellent library (Winforms) to do so, and if you so desire you can get into the raw GDI+, or even directx, its not all about web apps.
The GDI was moved into kernel space as a consicious decision in NT 4, it used to be in user space in 3.51, but Microsoft realized they could not get the performance needed (see X windows) unless it was moved. Perhaps it would have been nice to be able to choose that on the server, although it probably would have complicated driver development quite a bit, besides they do have embedded versions if you really want a headless server.
Um, please point me to some docs on where iis runs in kernel mode, didnt know inetinfo.exe was actually a kernel mode driver? Because I have killed it many times without having to reboot, oh maybey you didnt know that Task manager cant kill a service process because its running under a different security context(see kill.exe from the NT resource kit, or handelex form www.sysinternals.com)
Slashdot Mirror
Are you saying the CLR is interpreted? You might want to read up on its architecture if you think so. Then you would know that the IL is jitted into machine language as needed.
I do believe that when SQL server uses the CLR that T-SQL will become another CLR language, and it should be interesting to see how they handle data manipulation in other languages like c#, but using something like ado.net makes sense. Remeber that in SQL server 7 and above the engine itself uses OLEDB, so it wouldnt be that hard to imagine any CLR using that directly and effeciently, perhaps it might even be converted to use the SQL manage provider.
Its also not hard to imagine that the stored query plans will function like asp.net and acutally be compiled CLR code that was created by the optimizer using the codedom, or perhaps just emitted IL code. In any case I think we will see some very interesting stuff when MS starts using the CLR in SQL server.
Its seems like most people here you do not understand what .Net is, and it is Microsoft's fault to some degree. .Net does completely fix dll hell, the .net framework and clr where designed around "xcopy" deployment, meaning no more registry, xml config files in the app directory (novel idea ;)). In fact it makes me wonder about how the registry will be used as time goes on. But anyway my main piont is .Net is being marketed centralized applications that are rented, but in reality that is just one way to use the underlying framework, and at the same time it is Microsoft "eating there own dog food", by using the framework for that purpose. But it you still prefer to make a classic windows app the .Net framework gives a excellent library (Winforms) to do so, and if you so desire you can get into the raw GDI+, or even directx, its not all about web apps.
The GDI was moved into kernel space as a consicious decision in NT 4, it used to be in user space in 3.51, but Microsoft realized they could not get the performance needed (see X windows) unless it was moved. Perhaps it would have been nice to be able to choose that on the server, although it probably would have complicated driver development quite a bit, besides they do have embedded versions if you really want a headless server.
Um, please point me to some docs on where iis runs in kernel mode, didnt know inetinfo.exe was actually a kernel mode driver? Because I have killed it many times without having to reboot, oh maybey you didnt know that Task manager cant kill a service process because its running under a different security context(see kill.exe from the NT resource kit, or handelex form www.sysinternals.com)