Is anyone using .NET 3.0?

[jm]

It is production, so I wondered why more people aren't using it. Is
there any advantage to 2.0 developers to use 3.0?

 

[bruce barker]

..net 3.0 is just the work flow components added to 2.0. while you can
host a wf component in an asp.net application, deciding how manage its
event model with disconnected browsers will be a fun. if you need a
workflow rules engine look at 3.0.

note: 3.0 is not the new version of the clr with the new compilers, linq
and llamda functions.

-- bruce (sqlwork.com)

 

[Mark Rae]

It is production, so I wondered why more people aren't using it. Is
there any advantage to 2.0 developers to use 3.0?

None of any appreciable benefit to ASP.NET...

 

[Juan T. Llibre]

Maybe I don't get what .Net 3.0 make available for web developers.
Can you explain a bit what .Net 3.0 offers for web developers ?

 

[sloan]

..Net 3.0 probably would have been better called.

..Net 2.1 or 2.x or something. Because its not teh same jump as 1.0 to 1.1
or 1.1 to 2.0.

The WFC are one of the biggest "add ins".

 

[dgk]

Maybe I don't get what .Net 3.0 make available for web developers.
Can you explain a bit what .Net 3.0 offers for web developers ?

I believe:

There are four components. Windows Presentation Foundation is neat,
but is for desktop apps. Windows Communication Foundation seems like
Biztalk. Windows Workflow Foundation - looks like a good idea but I
don't even know if it's for asp or desktop, maybe both?

Cardspace is the fourth part and is sort of a single place to register
your identity so websites can authenticate you with a token instead of
all the logon stuff. I don't know how that works either but doesn't
appear to be proprietary to MS.

It isn't like it extended the languages or anything. More in the way
of new project types.

 

[Juan T. Llibre]

Not even that, given that it introduces zilch for web applications.

It should have been named something else, not .Net-something.
Maybe Windows FX, or something similar.

re:

The WFC are one of the biggest "add ins".

Which does zilch for web applications.

 

[Mark Rae]

.Net 3.0 probably would have been better called.

.Net 2.1 or 2.x or something. Because its not teh same jump as 1.0 to 1.1
or 1.1 to 2.0.

The WFC are one of the biggest "add ins".

But of no use to ASP.NET...

 

[jm]

But of no use to ASP.NET...

what about xaml and all that "stuff." Doesn't that affect designing at
least the presentation layer of asp.net applications? I'm asking
because I have a projects that I thought might be ideal to start
learning 3.0 with. They're small, but useful, but if 3.0 isn't linq
and all the other items I keep reading about, then perhaps I should
wait. I'd like to use xaml and the "flash killer," but I'm not sure
it's all ready for prime time.

 

[Mark Rae]

3.0 isn't linq and all the other items I keep reading about

It isn't...

If you want to investigate the next "true" version of the .NET Framework and
Visual Studio.NET, then you need to download Orcas from Microsoft:
http://www.microsoft.com/downloads/...27-458B-4129-9047-FCC4FACAE96C&displaylang=en

 

[jm]

It isn't...

If you want to investigate the next "true" version of the .NET Framework and
Visual Studio.NET, then you need to download Orcas from Microsoft:
http://www.microsoft.com/downloads/...27-458B-4129-9047-FCC4FACAE96C&displaylang=en

It's besides the point, but they shouldn't have renamed it then, IMHO.
It's confusing. They should have just released new components for 2.0.

 

[Juan T. Llibre]

re:

what about xaml and all that "stuff."

Anything that is created or implemented in XAML can be expressed
using a more traditional .net language, such as C# or Visual Basic .NET.

Maybe this site can clear up some of the doubts about xaml:

http://www.xaml.net/

 

[Laurent Bugnion [MVP]]

Hi,

I believe:

There are four components. Windows Presentation Foundation is neat,
but is for desktop apps.

<snip>

Don't forget XBAPs. They are interesting because they are somewhere in
between web applications and desktop applications. It's not really a RIA
either, since it's hosted in IE and deployed dynamically. I find XBAPs a
very interesting concept, actually, and they may be of interest for web
developers too.

HTH,
Laurent

 

[Mark Rae]

It's besides the point, but they shouldn't have renamed it then, IMHO.
It's confusing. They should have just released new components for 2.0.

I don't think you'll find any argument about that round here...

 

[Juan T. Llibre]

re:

I don't think you'll find any argument about that round here...

<chuckle>

 

[Joerg Jooss]

Thus wrote Bruce,

.net 3.0 is just the work flow components added to 2.0. while you can
host a wf component in an asp.net application, deciding how manage its
event model with disconnected browsers will be a fun. if you need a
workflow rules engine look at 3.0.

..NET 3.0 includes not only WF, but WCF, WPF, and CardSpace.

Cheers,

 

[Joerg Jooss]

Thus wrote Juan,

Maybe I don't get what .Net 3.0 make available for web developers. Can
you explain a bit what .Net 3.0 offers for web developers ?

While none of these technologies apply to each and every web app, in general
all of the .NET 3.0 frameworks are relevant for web development: WF can be
used to orchestrate your page flow (see the Web Client Software Factory for
an implementation) or business logic. WCF can be used to access or provide
remote or local services for distributed applications or integration scenarios.
CardSpace is the Windows solution to manage digital identities for web applications.
And WPF(/E) adds new capabilities to your user experience toolbox.

Also note that WCF is way more powerful than ASP.NET Web Services.

Cheers,

 

[Juan T. Llibre]

I agree on CardSpace, but reserve my judgment regarding
the usability on the web of the other .Net 3.0 technologies.

 

[Juan T. Llibre]

In case anybody is interested, there's 3 free .Net 3.0 eLearning courses:

Collection 5134 : Developing Rich Experiences with Microsoft .NET Framework 3.0 and Visual Studio
2005
https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=109340

This collection of 3 2-hour premium clinics teaches about the new capabilities provided by the
..NET Framework 3.0. These clinics are for experienced Developers and Software Architects
who are looking to adopt Microsoft's next generation technology within their solutions.

Topics covered within the collection include:

* Windows Presentation Foundation
* Windows Workflow Foundation
* Windows Communication Foundation

Requirements:

a. Experience (2 years) as a full time developer using Visual Studio 2005 / Visual Studio 2003
b. Experience developing one or more of the following:
a. Web Applications
b. Windows Forms Applications
c. Server Components
d. XML Web Services

This offer includes the following:

E-Learning

Clinic 5135: Introduction to Developing with Windows Presentation Foundation and Visual Studio 2005
Clinic 5136: Introduction to Developing with Windows Workflow Foundation and Visual Studio 2005
Clinic 5137: Introduction to Developing with Windows Communication Foundation and Visual Studio 2005

Enjoy!

 

[Joerg Jooss]

Thus wrote Juan,

I agree on CardSpace, but reserve my judgment regarding the usability
on the web of the other .Net 3.0 technologies.

Sure, neither WF nor WCF affect ASP.NET UI development, but once we talk
about implementing or reusing existing business logic (that probably already
runs on some other server), it starts to get interesting.

Cheers,