Discussions

http://www.bungie.net/News/content.aspx?type=news&cid=12835

Will be very interesting to see what games they do next....and for which platform!

hmm...not just BCL but also ASP.NET WinForms and WPF!

Seems the source code for the BCL in .NET will be released under Microsoft Reference License!

http://blogs.msdn.com/jgalasyn/archive/2007/10/03/net-framework-source-code-to-be-released.aspx

Dr Herbie wrote:

I've decided I can't keep up with this, so I'm now going to worry about it.
We only moved our code up from NET1.1 to NET2 in the last year and we don't expect our customers to go for Vista for a long while yet so there's no point in looking at WPF or WCF.

Just wondering why you are linking .NET 3 to Vista?  We started moving a very large project and a new project to .NET 3 over a year ago and have gained so much from WPF and Workflow Foundation.  We deploy our software onto Win2k3 for web and windows services.  Also XP Clients for the WPF Application front end.  Not a vista PC in sight!

Yep, very good news.  Have read his blog for quite a long time.

this tech really does look good!

Am very happy to hear that the apps are WPF as well.

Minh wrote:

Remoting is a pain in the a&& to work with.

Not only do you go through all the config headaches, you have to distribute your server-side DLL onto the client (to serve as a "proxy") so you don't even get instant update like a web app.

Use WCF -- I hear it's just much better.

Or just build a Web service.

Stay away from Remoting It's a dead-end technology.

You don't need to put your server .dlls on the client at all.  If you have a good solution which all objects in a shared assembly that will be sent by value over the remoting link then you are fine.  If you do ByRef method calls or object manipulation then keep your interfaces in the shared assembly as well.

I have used remoting as the core communication for a very large .net project and it works really well.  I am however looking at upgrading the whole lot to WCF for some of the more advanced features they have introduced.

I can sort of understand not having Expression Designer on there (however i do use that to get XAML).

However not having Web and Blend on there is a really bad move.  They are both very major tools for developers.  Blend mostly as it is the only good/productive way to develop WPF UIs.

VSS does indeed suck big time.  However Team Foundation Server rocks!

I believe it has not been RTM'ed yet.  (Due mid dec).  However they did launch it with Vista and Office on Nov 30th.