Longhorn - Written in .NET?
-
I was browsing a few sites that I frequent, and ran into a link over to a screenshot article on the newest leaked Longhorn beta. Just glancing through, and I struck one screenshot that made me very interested: http://www.flexbeta.net/images/longhorn_4015/12.gif[^]. For those who don't need to see the image, here's the full text of an error box shown in the screenshot: <Error Message> Explorer.EXE - Common Language Runtime Debugging Services Application has generated an exception that could not be handled. Process ID=0xcbc (3260), Thread ID=0xcc8 (3272). Click OK to terminate the application. Click Cancel to debug the application. </Error Message> Admittedly, this doesn't say much for the beta's stability, but if you reread the title of the error message, you might notice something interesting. Explorer.exe seems to have thrown a .NET exception. Is the new Windows version Longhorn at least partially written in .NET? Does anyone know?
-
I was browsing a few sites that I frequent, and ran into a link over to a screenshot article on the newest leaked Longhorn beta. Just glancing through, and I struck one screenshot that made me very interested: http://www.flexbeta.net/images/longhorn_4015/12.gif[^]. For those who don't need to see the image, here's the full text of an error box shown in the screenshot: <Error Message> Explorer.EXE - Common Language Runtime Debugging Services Application has generated an exception that could not be handled. Process ID=0xcbc (3260), Thread ID=0xcc8 (3272). Click OK to terminate the application. Click Cancel to debug the application. </Error Message> Admittedly, this doesn't say much for the beta's stability, but if you reread the title of the error message, you might notice something interesting. Explorer.exe seems to have thrown a .NET exception. Is the new Windows version Longhorn at least partially written in .NET? Does anyone know?
-
I was browsing a few sites that I frequent, and ran into a link over to a screenshot article on the newest leaked Longhorn beta. Just glancing through, and I struck one screenshot that made me very interested: http://www.flexbeta.net/images/longhorn_4015/12.gif[^]. For those who don't need to see the image, here's the full text of an error box shown in the screenshot: <Error Message> Explorer.EXE - Common Language Runtime Debugging Services Application has generated an exception that could not be handled. Process ID=0xcbc (3260), Thread ID=0xcc8 (3272). Click OK to terminate the application. Click Cancel to debug the application. </Error Message> Admittedly, this doesn't say much for the beta's stability, but if you reread the title of the error message, you might notice something interesting. Explorer.exe seems to have thrown a .NET exception. Is the new Windows version Longhorn at least partially written in .NET? Does anyone know?
I wouldn't trust screenshots of a product that isn't due to be released for at least 2 years. Maybe the crash was simply due to a component of IE that is fully managed, whereas the core of IE could still be native. cheers, Chris Maunder
-
I wouldn't trust screenshots of a product that isn't due to be released for at least 2 years. Maybe the crash was simply due to a component of IE that is fully managed, whereas the core of IE could still be native. cheers, Chris Maunder
It's still 2 years away??? Thought it was sooner. Is there a timeline anywhere? Regards, Brian Dela :-)
-
I was browsing a few sites that I frequent, and ran into a link over to a screenshot article on the newest leaked Longhorn beta. Just glancing through, and I struck one screenshot that made me very interested: http://www.flexbeta.net/images/longhorn_4015/12.gif[^]. For those who don't need to see the image, here's the full text of an error box shown in the screenshot: <Error Message> Explorer.EXE - Common Language Runtime Debugging Services Application has generated an exception that could not be handled. Process ID=0xcbc (3260), Thread ID=0xcc8 (3272). Click OK to terminate the application. Click Cancel to debug the application. </Error Message> Admittedly, this doesn't say much for the beta's stability, but if you reread the title of the error message, you might notice something interesting. Explorer.exe seems to have thrown a .NET exception. Is the new Windows version Longhorn at least partially written in .NET? Does anyone know?
I smell a rat. :suss: Eric Astor wrote: Is the new Windows version Longhorn at least partially written in .NET? It still has to be made native in the end. And I doubt they will make a complete re-write in .NET, can you imagine the speed if everything has to be JITed? Even Pre-JIT managed code is fairly slow. Nah, they'll keep it mainly native, its the safest way to be for an OS. [edit] I just noticed, why is it trying to load the OLD windows update? Even windows 2000 loads V4. Very odd :suss::suss: [/edit]
"If you just say porn then you get all manner of chaff and low grade stuff."
- Paul Watson, Lounge 25 Mar 03
"If a man is standing in the middle of the forest speaking and there is no woman around to hear him, is he still wrong?"
- Anon
Jonathan 'nonny' Newman Homepage [www.nonny.com] [^]
-
It's still 2 years away??? Thought it was sooner. Is there a timeline anywhere? Regards, Brian Dela :-)
Brian Delahunty wrote: Is there a timeline anywhere? On the back of a cornflakes box in an office in Redmond probably.
"If you just say porn then you get all manner of chaff and low grade stuff."
- Paul Watson, Lounge 25 Mar 03
"If a man is standing in the middle of the forest speaking and there is no woman around to hear him, is he still wrong?"
- Anon
Jonathan 'nonny' Newman Homepage [www.nonny.com] [^]
-
Brian Delahunty wrote: Is there a timeline anywhere? On the back of a cornflakes box in an office in Redmond probably.
"If you just say porn then you get all manner of chaff and low grade stuff."
- Paul Watson, Lounge 25 Mar 03
"If a man is standing in the middle of the forest speaking and there is no woman around to hear him, is he still wrong?"
- Anon
Jonathan 'nonny' Newman Homepage [www.nonny.com] [^]
Jonny Newman wrote: On the back of a cornflakes box in an office in Redmond probably. Yep. More than likely. :rolleyes: Regards, Brian Dela :-)
-
It's still 2 years away??? Thought it was sooner. Is there a timeline anywhere? Regards, Brian Dela :-)
-
I was browsing a few sites that I frequent, and ran into a link over to a screenshot article on the newest leaked Longhorn beta. Just glancing through, and I struck one screenshot that made me very interested: http://www.flexbeta.net/images/longhorn_4015/12.gif[^]. For those who don't need to see the image, here's the full text of an error box shown in the screenshot: <Error Message> Explorer.EXE - Common Language Runtime Debugging Services Application has generated an exception that could not be handled. Process ID=0xcbc (3260), Thread ID=0xcc8 (3272). Click OK to terminate the application. Click Cancel to debug the application. </Error Message> Admittedly, this doesn't say much for the beta's stability, but if you reread the title of the error message, you might notice something interesting. Explorer.exe seems to have thrown a .NET exception. Is the new Windows version Longhorn at least partially written in .NET? Does anyone know?
I think .net will have much tighter integeration than any of todays existing OS, thats pretty much known thing. From the screen shots I've seen earlier, there is something called Avalon (.net framework for longhorn) which looks pretty cool. But Chris said, its more than two years away and is tough to speculate now based on the screen shots which are not official. Cheers, Kannan
