Will you use .NET 3.0?

How do you forsee yourself using .NET 3.0 over the next 6 months or so?

WCF -> Maybe.  Currently using ICP Remoting.
WPF -> Our company has a complex Flash GUI which could do well in WPF.  However, porting it would not be trivial, and we don't have dev hours to burn.
WF -> Nope
CardSpace -> Not sure.

WCF -> Already using it for intranet communication in our software.
WPF -> We plan on utilizing WPF in the near future.
WF -> Nope. No need.
CardSpace -> Probably, in the future.

So, I guess the answer here is Yes.

WCF -> Planning to play with it. Never done any work with web services and from some Microsoft WCF demos I watched, the technology seems really promising.
WPF -> Definitely. WPF is the part of .NET 3.0 that intrigues me the most.
WF -> Assuming this means Workflow Foundation, probably not at first. Might play with it in the future.
CardSpace -> Very unsure about this one. I'm interested in seeing if it'll catch on, but got no plans to develop for it myself.

WCF -> Don't see it being used atleast in the next version of our product. I'd be interested in getting started early though
WPF -> Definitely. Not the 3D stuff, but things like text, speech, packaging, etc APIs. Infact we've started to use the packaging stuff already.
WF -> Probably not.
CardSpace -> Most likely, in any case I'll be planning to start on getting upto speed with it.

WCF - just working on implementing some of it now, because we wanted self-hosting HTTP web services, working well so far, quite straitforward too.

WPF- I am sure in the future yes, at the moment no.

WWF- perhaps, I saw some articles that showed some promise in it.

I will use it when they launch the Expression Suite, especially Sparkle, aka Expression Interactive Designer. I hope to be switching from Flash to Sparkle.

I am really looking forward to using Visual Studio 2008 in the first quarter of 2008 using .Net Framework 3.5 or 4.0 with LINQ.

Currently I am using .Net Framework 2.0 and like the data binding tools in Visual Studio 2005. Saves me from writing thousands of lines of code.

I suspect the Windows 2008 (server version) and Visual Studio 2008 will be released Q1 of 2008.  The sooner the better.

WCF -> Nope.
WPF -> Nope.
WF -> Nope
CardSpace -> Nope.

Not, at least, until I *need* to use them.

Seriously?

Let's see - will I use all these really cool new toys.... Hmm... Let me think.

Just as soon as I have time to do any pet projects you can bet your life I'll be using WCF, WPF and Cardspace. I don't have much use for WF, but that's ok, I'm not the target audience.

I imagine WCF will be the most useful for now - but most people will want to play with WPF.

WCF -> Have just come off a 6-month project where we used WCF exclusively for all client/server and server/service communication. It's great. Hope I'll get more chances to use it.
WPF -> Will probably start playing with it, but I hate UI programming anyway.
WF -> Will probably get to use it as part of Sharepoint dev projects.
CardSpace -> To me, it seems CardSpace relies on there being a pretty big ecosystem in place. If you're the only one using CardSpace you get little benefit over traditional methods, whereas the moment lots of different providers start using it, we'll see the benefits. It didn't work with Hailstorm, maybe it will now. Or maybe I'm just not grokking CardSpace.   

Does anyone know a good "introduction to WCF" type article? Preferably one that isn't written against beta 1.

Sven Groot wrote:

Does anyone know a good "introduction to WCF" type article? Preferably one that isn't written against beta 1.

I think a good place to start would be http://wcf.netfx3.com/, the WCF-section of the official .NET 3.0 site. Especially the Resources page.

Sven Groot wrote:

Does anyone know a good "introduction to WCF" type article? Preferably one that isn't written against beta 1.

https://www.microsoftelearning.com/eLearning/offerDetail.aspx?offerPriceId=109340

WCF - I am not sure if it does TCP.  Currently, we use TCP to send data btw server/client[ Its a real-time system]. i dont how this will help. any ideas? - Sending data from server->client should be atleast 10-20 records per seconds. We currently use this
which is great but looking for something to replace that...

WPF - Maybe
WF- Not sure
Cardspace - Nope.

Although, I like the PeerChannel which is really cool. I wish there were some goood samples to play with.

arunpv wrote:

WCF - I am not sure if it does TCP.  Currently, we use TCP to send data btw server/client[ Its a real-time system]. i dont how this will help. any ideas?

WCF will do what you want - but why place extra layers of abstraction (and code) over the top of The One True Way(tm)

Yes I am kidding, sorta, maybe. A bit.

Rossj wrote:



WCF -> Nope.
WPF -> Nope.
WF -> Nope
CardSpace -> Nope.

Not, at least, until I *need* to use them.

Pretty much the same except for me more when the Customer has or wants to use them.

Is CardSpace passport 2.0?

Rossj wrote:



arunpv wrote:WCF - I am not sure if it does TCP.  Currently, we use TCP to send data btw server/client[ Its a real-time system]. i dont how this will help. any ideas?

WCF will do what you want - but why place extra layers of abstraction (and code) over the top of The One True Way(tm)

Yes I am kidding, sorta, maybe. A bit.

Hmmm.... Interesting... How about PeerChannel? Can I use that for sending Data packets Client to Client. That way i can reduce the overhead on the Server right?