For those who haven't managed to use .NET 2.0 yet

Forum Moderators: open

Message Too Old, No Replies

For those who haven't managed to use .NET 2.0 yet

Jimmy Turnip

2:46 pm on Jul 3, 2006 (gmt 0)

.NET 3.0 (ish)

[msdn.microsoft.com...]

wardbekker

7:33 am on Jul 4, 2006 (gmt 0)

Just for completeness:

- It's still in Beta
- Visual Studio 2005 can handle it with some updates, but still very buggy.
- Net 3.0 is actually a extended Net 2.0 version, previously called WinFx. For me the biggest addition is the Windows Presentation Framework. WPF is the next step in the evolution of Windows Forms. The old win32 is (finally) thrown overboard and you are now able to take advantage of the graphic capabilities of modern GPU's. For the developer that means much more freedom in creation of the UI: Vector based UI, 2D animation acceleration etc..

txbakers

3:01 pm on Jul 4, 2006 (gmt 0)

well I'm sure glad I didn't rush out and buy 2.0 books and spend a year learning it.

I guess I'll wait for 3.0....

wardbekker

3:15 pm on Jul 4, 2006 (gmt 0)

txbakers,

You really want to wait then for version 4.0. It fixes all the irritating bugs of 3.0 , plus adds more complexity and even some extra new bugs! ;-)

aspdaddy

9:30 pm on Jul 4, 2006 (gmt 0)

For the developer that means much more freedom in creation of the UI: Vector based UI, 2D animation acceleration etc..

Yeah, one of the biggest problems with business systems is that the forms just arent pretty enough. Now we can all benefit from prettier forms designed by geeky programmers with no design skills. This really is exciting news.

wardbekker

9:59 pm on Jul 4, 2006 (gmt 0)

Now we can all benefit from prettier forms designed by geeky programmers with no design skills

I hope they also support the blink tag ;-)

mrMister

9:02 am on Jul 5, 2006 (gmt 0)

Why is it that Microsoft seem great at creating useful naming schemes (codenames) for their pre-release products, but then fall flat on their face with the final product naming.

It's getting harder and harder to see where .Net Framework ends and the Windows API begins.

WinFX is a Windows API. It's the successor to the Win32 API, so why the hell have the decided to call it .Net 3.0?

It would be a lot easier if the Framework were to be kept seperate from the Windows APIs.

Easy_Coder

9:02 pm on Jul 5, 2006 (gmt 0)

Why is it that Microsoft seem great at creating useful naming schemes (codenames) for their pre-release products, but then fall flat on their face with the final product naming

Naming by commitee gets those silly marketing goofs every single time...