http://www.stephenforte.net/owdasblog/PermaLink.aspx?guid=15ff6542-8059-4ebb-b768-3c511bf70268

Looks like Nov. 7 - of this year is when Yukon will be released...

Jeff...

November 7th? I haven't seen that date before... But vs.net 2005 also has to be finished by then... that will be a looooooooooooooooong struggle (edit). It is true, it was said during Paul Flessner's keynote at teched 2005. VS.NET 2005, SqlServer 2005 and biztalk 2006 will be released in the week of november 7th.

This also means that the current upgrade will not get expression columns in the LLBLGen Pro designer (in the current upgrade) to have more time to get 2.0 done by November (which will have this feature)

That makes me sad, I would like expressions in the designer. Is v2.0 going to have both dotnet 1.1 and 2.0 compatible templates?

Otis wrote:

It is true, it was said during Paul Flessner's keynote at teched 2005. VS.NET 2005, SqlServer 2005 and biztalk 2006 will be released in the week of november 7th.

I don't mean to be skeptical... BUT I'd be very surprised if that date doens't slip AGAIN.

arschr wrote:

That makes me sad, I would like expressions in the designer. Is v2.0 going to have both dotnet 1.1 and 2.0 compatible templates?

Yes, v2.0 will have .NET 1.x and 2.0 compatible code bases. Features solely for .NET 2.0 of course aren't available in .NET 1.x. The codebase for .NET 1.x is a continuation of the current code base, the codebase for .NET 2.0 is rewritten for the most part.

Expressions in the designer take a lot of time to develop, I'll see if I have time for them. The design is already done, and I'd planned to use a SyntaxEditor control to let the user enter them, the problem is to keep the underlying objects in sync when someone renames a field for example. But perhaps I solve that in an hour and they're slipped into the code as I too really want to have them. .

Marcus wrote:

Otis wrote:

It is true, it was said during Paul Flessner's keynote at teched 2005. VS.NET 2005, SqlServer 2005 and biztalk 2006 will be released in the week of november 7th.

I don't mean to be skeptical... BUT I'd be very surprised if that date doens't slip AGAIN.

I thought that too, but then I realized how Microsoft makes deadlines: they scrap features and simply don't fix bugs. I.o.w.: now this date is set, you can be sure the stuff is on a DVD in that week, which is IMHO a sad thing... Though they can't wait any longer with SqlServer 2005...