"Longhorn" SDK available

High-Tag

Newcomer
Joined
Nov 8, 2003
Messages
2
Please refer to this site for more information

http://longhorn.msdn.microsoft.com/



===========================================================

Seriously saying will longhorn be very different from windows XP?
Well i have read some articles that say that some new compiler to compile codes...

And wht is WinFX?? totally no idea wht's that....

Do we need to learn this and upgrade ourselves?
 
ok, you can find at this moment plenty of information for longhorn and Whidbey, but for sure we'll have to wait 'til the final relases of this software to have a good and complete documentation of them available.... in the meantime, we have to do it ourselves

:)
 
You might want to check out www.winsupersite.com

Longhorn will feature hundreds of new APIs that will let provide access to the new system's features. The Win32 API from previous Windows versions is being replaced by a new .NET-based API called WinFX, for example. It will also feature a new communications and collaboration subsystem, dubbed Indigo.
 
I was reading some of the comments on the message board on that site and one mentioned that Longhorn is going to be Vector Graphics driven... why lord why would anyone waste processor time with that? And I saw another post that said it will require a 6G processor to run? That maybe someone blowing smoke... don't think we'll get that far in 3 years. But about the vector graphics... XP and it's bubbly feel good graphics was shut-off 2 seconds after the first time I logged on... if I wanted my computer to be bogged down I'd just keep my old 133Mhz rather than have a lot of useless process' running in the background!
 
.NET 2004 basically from what I read... going to add more bells and whistels to the IDE for VB'ers (like on errors it looks like they have a spell check type of thing (did you mean boolean rather than bolian) for example)... didn't see that it would be there for C#... one cool thing I saw was that instead of:

C#:
Label myLabel = new Label();
myLabel.Name = "Label1";
myLabel.Click += new ClickEventHandler(Label1_Click);

//then later in your code:
public void Label1_Click(object sender, EventArgs e) //or whatever it is
{
  //code
}

it will be simpler:
C#:
Label myLabel = new Label();
myLabel.Name = "Label1";
myLabel.Click += new ClickEventHandler(object sender, EventArgs e)
{
    //code
}

Be nice to skip a step there... there were a lot of other things too but I don't remember now what it all was... follow this link for more info:
http://msdn.microsoft.com/vstudio/productinfo/roadmap.aspx
 
That's known as an anonymous method.

C#, along with VB.NET, will gain anonymous methods, generics (similar to templating in C++), and partial types. VB.NET will also gain XML code comments, a feature that C# already has. ASP.NET will be augmented with master pages, personalization, and a few dozen additional server controls.

All in all, this will be a major release.
 
I don't like the look of this FX - first we learn one thing (me only just!) and then they bring something else in! When will it end?

Will the win32 APIs still be supported?
 
Partial types allow developers to declare a class (and its members) in two or more files. This is an excellent improvement for ASP.NET, and will allow larger classes to be broken down into more manageable pieces.

As for WinFX-- your .NET applications of today will still run on the Windows "Longhorn" framework. Win32 applications will as well, for the most part.
 
Is there a good reason to change from XP to LongHorn, I know there was a big change since win 98 to XP but now?

I don't think it worth it, they keep doing new operating systems instead of improving the ones thy have because of the business and not the quality. What do you think?

Bye,
Ronq.
 
Microsoft is releasing Windows XP SP2 in quarter one of this year. How are they not improving their exisiting operating systems? Do you expect them to sit still and never innovate?
 
The reason to move from XP to Longhorn is to move into new (.NET) territory, since Longhorn will be heavily integrated with .NET. I believe Microsoft has said the change will be comparable to the move from DOS -> Windows, and from Win3.1 -> Win95.
 
ok I'll show me ignorance:(

Longhorn? is there somewhere I can see screen shots?
My employer is still on W2K not sure of Longhorn plans, but I woul like a look:)

VS 2004? Will there be an easy cheap upgrade for VS 2003 users?
 
VS 2004? Will there be an easy cheap upgrade for VS 2003 users?

MS always provides an upgrade option. However, it'll most likely be far more than the measly $50 you paid to upgrade from 2002 to 2003.
 
Back
Top