J
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?
there any advantage to 2.0 developers to use 3.0?
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?
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 ?
The WFC are one of the biggest "add ins".
.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".
Mark said:But of no use to ASP.NET...
3.0 isn't linq and all the other items I keep reading about
Mark said: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
what about xaml and all that "stuff."
I believe:
There are four components. Windows Presentation Foundation is neat,
but is for desktop apps.
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...![]()
.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.
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 agree on CardSpace, but reserve my judgment regarding the usability
on the web of the other .Net 3.0 technologies.