First, Version 2.0 of the.net Framework is still in beta.
Second, one of the whole points of the.Net framework is side-by-side deployment. That applies to the framework itself, not just apps developed with.Net.
For example, I have versions 1.0, 1.1, and 2.0 beta installed on my machine. I can write an app using VS Net 2005 that targets 1.0, even though VS Net 2005 comes with version 2.0. So it really doesn't matter what version of.Net ships with Longhorn (expect 2.0, maybe 2.x), as no one will have to develop for it.
Hint: This is why MS touted.Net as the end of DLL Hell.**
Another hint: This is why Microsoft can never 'break' Mono. Even if Mono, by some disaster, is not able to keep up with.Net version x.x, it will always be able to run 1.1 apps.
Third, Microsoft is releasing IE7 this year (betas available this summer). Note that this is a full year ahaed of Longhorn, and that XAML is not supported on XP.
And last but certainly most important is that XAML is not a web forms language. In Longhorn, it is the counterpart to <asp:/> tags, for creating Avalon applications.
Let me say that again. XAML is intended to be used to develop Windows applications. Not web apps. While XAML (Windows) apps can be run within the browser, the default behavior is to run as a Windows app, in its very own top level window. Or <canvas>, if you prefer the XAML notation...
You are likely correct in speculating that XAML will become the preferred intranet platform of choice for Windows only shops, but developers have been able to produce Windows only intranet apps for years now, without even touching IE.
It's called a smart client: A Windows forms app connected to a web service.
** Having contracted for MS, I am amazed that they were able to develop anything before.Net. DLL Hell may be bad for users, but it's a lot worse for developers.
I remember being tasked to modify a team member's app once. I check out the source, made the adjustments, compiled, and checked the source in. When the app was run, it had a logic error. After several hours of debugging, I was baffled. A code review found no problems with my work. The original developer, on a whim, checked out the code and complied it. It ran perfectly. I was like WTF?!
I had version 4.2.x of one of the DLLs used in the app on my box. He had 4.1.x.x. Go figure.
I'll simply correct your statements, as there is no -1 Wrong available.
Microsoft is going to release IE7 *this year*, for Windows XP. You may confirm this by checking out blogs.msdn.com/ie.
Betas of IE7 will be available this summer. No feature set / improvements have been announced, but it will almost certainly contain all of the features you described (Except XAML support).
Also, a good bit of 'IE7' might be done. MSDN posted an exercise for users of Visual C# Express Edition Beta that used the '.Net2 browser object' to create a custom web browser, complete with tabs, tear offs, etc. I have the beta of VS 2005 and did the exercise (it took about 20 minutes), and had a WTF! moment due to the project rendering sites differently than IE6.
(New html rendering engine, perhaps? I honestly don't know. I took almost 4 hours to install VS Net 2005, so who knows what's in there...)
Only a half-hearted attempt to understand this nation's founding and history could lead you to the conclusions you've vomited all over this page. ...
Oh, really?
I gather you missed that day in your US History course when FDR's threat of packing the Supreme Court was covered?
And you seem to be ignorant of the fact that FDR made the threat due to the fact that the Court was poised to rule that the entirety of the so-called 'New Deal', including Social Security, was unconstitutional.
Go back to Jr. High. The ignorant need not discuss the issues of the day.
Slashdot Mirror
First, Version 2.0 of the .net Framework is still in beta.
.Net framework is side-by-side deployment. That applies to the framework itself, not just apps developed with .Net.
.Net ships with Longhorn (expect 2.0, maybe 2.x), as no one will have to develop for it.
.Net as the end of DLL Hell.**
.Net version x.x, it will always be able to run 1.1 apps.
/> tags, for creating Avalon applications.
.Net. DLL Hell may be bad for users, but it's a lot worse for developers.
Second, one of the whole points of the
For example, I have versions 1.0, 1.1, and 2.0 beta installed on my machine. I can write an app using VS Net 2005 that targets 1.0, even though VS Net 2005 comes with version 2.0. So it really doesn't matter what version of
Hint: This is why MS touted
Another hint: This is why Microsoft can never 'break' Mono. Even if Mono, by some disaster, is not able to keep up with
Third, Microsoft is releasing IE7 this year (betas available this summer). Note that this is a full year ahaed of Longhorn, and that XAML is not supported on XP.
And last but certainly most important is that XAML is not a web forms language. In Longhorn, it is the counterpart to <asp:
Let me say that again. XAML is intended to be used to develop Windows applications. Not web apps. While XAML (Windows) apps can be run within the browser, the default behavior is to run as a Windows app, in its very own top level window. Or <canvas>, if you prefer the XAML notation...
You are likely correct in speculating that XAML will become the preferred intranet platform of choice for Windows only shops, but developers have been able to produce Windows only intranet apps for years now, without even touching IE.
It's called a smart client: A Windows forms app connected to a web service.
** Having contracted for MS, I am amazed that they were able to develop anything before
I remember being tasked to modify a team member's app once. I check out the source, made the adjustments, compiled, and checked the source in. When the app was run, it had a logic error. After several hours of debugging, I was baffled. A code review found no problems with my work. The original developer, on a whim, checked out the code and complied it. It ran perfectly. I was like WTF?!
I had version 4.2.x of one of the DLLs used in the app on my box. He had 4.1.x.x. Go figure.
I'll simply correct your statements, as there is no -1 Wrong available.
.Net2 browser object' to create a custom web browser, complete with tabs, tear offs, etc. I have the beta of VS 2005 and did the exercise (it took about 20 minutes), and had a WTF! moment due to the project rendering sites differently than IE6.
Microsoft is going to release IE7 *this year*, for Windows XP. You may confirm this by checking out blogs.msdn.com/ie.
Betas of IE7 will be available this summer. No feature set / improvements have been announced, but it will almost certainly contain all of the features you described (Except XAML support).
Also, a good bit of 'IE7' might be done. MSDN posted an exercise for users of Visual C# Express Edition Beta that used the '
(New html rendering engine, perhaps? I honestly don't know. I took almost 4 hours to install VS Net 2005, so who knows what's in there...)
Only a half-hearted attempt to understand this nation's founding and history could lead you to the conclusions you've vomited all over this page.
...
Oh, really?
I gather you missed that day in your US History course when FDR's threat of packing the Supreme Court was covered?
And you seem to be ignorant of the fact that FDR made the threat due to the fact that the Court was poised to rule that the entirety of the so-called 'New Deal', including Social Security, was unconstitutional.
Go back to Jr. High. The ignorant need not discuss the issues of the day.