Comment A few points for you to consider... (Score 1) 339
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.
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.
