.NET Framework - MIX 2007 face-to-face session?

I wanted to check how much interest there was in doing an hour-long
face-to-face session as Mix 2007 with the Expression Blend team. If there is
significant interest, we can set aside an hour (or two if you want) to
listen to feedback, and that will help us deliver an even better release
next time around.

Also, there will be a variety of interesting annoucements coming at Mix - so
stay tuned! If you are not attending, no need to worry - we will have most
of the information shortly after they are delivered at
http://www.visitmix.com. Also, we plan to publish all the Expression Blend
Hand-On-Labs after the conference (and we think we have some pretty cool
ones!), so that would be a great way to get more familiar with some of the
newest features in the product if you are new to it!

Thanks,
-unni

  BrennonWilliam replied...

Howdy,

I won't be attending MIX unfortunately but if I was, I would have liked to
meet the entire team.

Good luck with everything there and I hope all the people that have been
helped at one time or another by you and the rest of the team go and thank
you all personally.

Have fun in Vegas and say g'day to Elvis for me!

Cheers
--
http://www.learnexpressionblend.com
http://www.expressionblend.com
http://www.resourcedictionary.com
http://www.x-coders.com

http: / / vadmyst.blogspot.com You wrote on Thu, 1 Nov 2007 12:45:00 -0700: MS> Hi, MS> I'm trying to build a robust application framework that will be used MS> by other developers in the future. Their applications should be MS> able to recover themselves if they are crashing MS> So, I thought, the best way to handle this is to lauch their stuff MS> in a separate AppDomain and when that AppDomain crashes, unload it MS> and restart it. MS> This seems to work fine, unless an unhandled exception occurs in a MS> background thread

1$1$1$1$1$S, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S S, S, S, S, S, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S S, S, S, S, S, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S S, S, S, S, S, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S$1, S, S, S, S, S, S, S, S, S, MS, S, S, S, S, S, S, S, S, S, S, S, S, S, S, S

expressed in LINQ, but that's okay.) As for backward compatibility: I wouldn't expect MS to release a version of .NET which breaks NHibernate or other libraries, and if it no other. You could look at the Repository Factory, a GAT package which comes from MS Patterns and Practices, and which is now up on codeplex.com. - - Peter Recursion: see Recursion database support than nHibernate (which chokes when doing simple stuff like using Guid fields with MS Access). XPO also has a much more logical Attribute design since the nHibernate attributes are affected if I change foo AFTER this query and BEFORE execution. Why is this comparison expression suddenly different from the expression of b? The first is executed at that moment, the latter is executed somewhere later It seems to do OK on Firebird but falls over on really simple stuff in MS Access (e.g. create a Guid column in your Access table and watch the schema tries to create the table). There are a number of documented issues with nHibernate and MS Access (due to limited support in MS Access for stuff like subqueries) - whereas XPO works flawlessly with MS Access. Like I say

Linq; expression parser? .NET Framework In Linq, you can apparently get a meaningful body from and expression's .ToString(); random question - does anybody know if linq also includes a parser? It just possible at all? Marc C# Discussions LINQ (1) VB.NET (1) IBindingListView (1) DynamicExpression (1) Expression (1) AppDomain (1) PropertyInfo (1) ParseLambda (1) Why would you use a parser on the Because that parser will produce a parse tree which will look very similar to the expression tree you called ToString() on :) So interpret the expression tree instead. FB - - - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - Lead developer of LLBLGen Pro, the productive O / R mapper for .NET weblogs.asp.net / fbouma Microsoft MVP (C#) - -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- - I think the point would be to parse expression trees which *hadn't* been created from ToString, but read in from a file etc interpreted my witterings. . . my point being, that unlike raw .Net 2.0 predicates (etc), LINQ expression trees are quite structured. Obviously the C# 3-series compiler can parse source to create an expression, but it is unclear to me (at least until Reflector supports CLR 3.5 ;-p

Text && c.Column_2 = = TextBox2.Text select c; Thank you! -Stefan C# Discussions System.Linq.Expressions.Expression.ValidateNewArgs (1) AppDomain.CurrentDomain.AssemblyResolve (1) DBLinq.util.RowEnumeratorCompiler (1) System.Linq.Enumerable.ToList (1 have been PropertyA] It's actually slightly easier than that if you ignore the query expression syntax: var query = dataContext.SomeEntities.AsQueryable(); if (!string.IsNullOrEmpty(inputA)) { query = query.Where(x = > x PropertyB = = inputB); } You could even write a method to abstract it out if necessary. Query expression syntax is nice in many cases, but just to add a Jon Hi Jon. I uses a proportional font) IQueryable<T> ConditionalWhere<T> (static this IQueryable<T> query, string value, Expression<Predicate<T> > predicate) { if (!string.IsNullOrEmpty(value)) { return query.Where(predicate); } } then call it with 10:01 am, Stefan Wilhelm I mean explicitly calling Where instead of letting the query expression translation do it for you. What do you mean by "what is with ORDER BY you'll need to use the OrderBy method or "order by" part of the query expression syntax - but that will be more strongly typed than your SQL example. Jon I want no query.OrderBy<Firma> ("columnAsString"); Thank you for your answers!!! You could presumably put an expression tree and lambda together through code (using Expression.Property(. . .) at some point), but it would not be pretty. The switch would be easier