Comments for The Tranxition Developer Blog http://tranxcoder.wordpress.com Random musings from the developers at Tranxition Fri, 30 Oct 2009 13:52:19 +0000 http://wordpress.com/ hourly 1 Comment on A Generic Factory in C# by Bryan Ray http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-156 Bryan Ray Fri, 30 Oct 2009 13:52:19 +0000 http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-156 Definitely a good use of Reflection and an excellent walk through for understanding how to refactor your code and look for "code smells." I would, however, agree with hempelcx and cgassib that you're very much going towards a Dependency Injection solution. There's a lot of "support" code there that has to be maintained and rather than focusing on your application you're having to focus on something that a DI container could do for you. Take a look at Ninject, Unity, Autofac, Spring.NET, etc. There's a handful of good DI libraries out there. I only say this for future readers who are looking. Other than that it's a great article, man. Thanks. Definitely a good use of Reflection and an excellent walk through for understanding how to refactor your code and look for “code smells.”

I would, however, agree with hempelcx and cgassib that you’re very much going towards a Dependency Injection solution. There’s a lot of “support” code there that has to be maintained and rather than focusing on your application you’re having to focus on something that a DI container could do for you.

Take a look at Ninject, Unity, Autofac, Spring.NET, etc. There’s a handful of good DI libraries out there.

I only say this for future readers who are looking. Other than that it’s a great article, man.

Thanks.

]]> Comment on A Generic Factory in C# by cgassib http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-155 cgassib Thu, 08 Oct 2009 20:15:55 +0000 http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-155 I agree. It sounds like the route you're heading is leaning more towards a Dependency Injection approach. I agree. It sounds like the route you’re heading is leaning more towards a Dependency Injection approach.

]]> Comment on A Generic Factory in C# by hempelcx http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-154 hempelcx Thu, 08 Oct 2009 06:37:02 +0000 http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-154 arno, To me that's starting to sound a lot like a plugin or extension framework. Personally, I would consider either a <a href="http://www.hanselman.com/blog/ListOfNETDependencyInjectionContainersIOC.aspx" rel="nofollow">Dependency Injection Container</a> or Microsoft's <a href="http://www.codeplex.com/MEF" rel="nofollow">Managed Extensibility Framework</a> depending on how far you want to take it. arno,

To me that’s starting to sound a lot like a plugin or extension framework. Personally, I would consider either a Dependency Injection Container or Microsoft’s Managed Extensibility Framework depending on how far you want to take it.

]]> Comment on Customizing “lookful” WPF controls – Take 2 by jan http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-153 jan Wed, 07 Oct 2009 20:06:59 +0000 http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-153 oh never mind, i figured it out. sorry for the spam =) oh never mind, i figured it out.
sorry for the spam =)

]]> Comment on Customizing “lookful” WPF controls – Take 2 by jan http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-151 jan Wed, 07 Oct 2009 19:18:11 +0000 http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-151 Hi! Thanks for this post. I downloaded the project file and it works on the multi-line but not if there's just one word in it and Trimming = ”CharacterEllipsis” as Kevin noted above. Do you have an updated project file? Thanks Hi! Thanks for this post. I downloaded the project file and it works on the multi-line but not if there’s just one word in it and Trimming = ”CharacterEllipsis” as Kevin noted above. Do you have an updated project file?
Thanks

]]> Comment on Customizing “lookful” WPF controls – Take 2 by Richard Jones http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-150 Richard Jones Wed, 07 Oct 2009 08:12:57 +0000 http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-150 To solve the problem with calculating IsTextTrimmed when the field contains a single word, a simpler solution is to add the line: formattedText.Trimming = TextTrimming.None after formattedText.MaxTextWidth = textBlock.ActualWidth (rather than Kevin's extra code from August 8th). This means that formattedText's height always increases if its content needs to wrap around. I have another problem: The IsTextTrimmed property is recalculated if the textblock size is changed (e.g. if the UI is resized). However, it doesn't get recalculated if the textblock's content is changed. I'm using binding to set the textblock's value, and IsTextTrimmed is calculated correctly when the field is displayed initially. However if the underlying Text value is then changed to something else, IsTextTrimmed doesn't get recalculated (unless you jiggle the edge of the UI!) It seems that where we register the handler for the SizeChangedEvent, we also need to do something similar for when the Text property's value is changed. I've tried various things but haven't found an elegant solution. Any ideas? To solve the problem with calculating IsTextTrimmed when the field contains a single word, a simpler solution is to add the line:
formattedText.Trimming = TextTrimming.None
after
formattedText.MaxTextWidth = textBlock.ActualWidth
(rather than Kevin’s extra code from August 8th). This means that formattedText’s height always increases if its content needs to wrap around.

I have another problem: The IsTextTrimmed property is recalculated if the textblock size is changed (e.g. if the UI is resized). However, it doesn’t get recalculated if the textblock’s content is changed. I’m using binding to set the textblock’s value, and IsTextTrimmed is calculated correctly when the field is displayed initially. However if the underlying Text value is then changed to something else, IsTextTrimmed doesn’t get recalculated (unless you jiggle the edge of the UI!)

It seems that where we register the handler for the SizeChangedEvent, we also need to do something similar for when the Text property’s value is changed.
I’ve tried various things but haven’t found an elegant solution. Any ideas?

]]> Comment on A Generic Factory in C# by -arno- http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-149 -arno- Mon, 28 Sep 2009 12:50:51 +0000 http://tranxcoder.wordpress.com/2008/07/11/a-generic-factory-in-c/#comment-149 Hello, i developped quite the same thing (~not generic :( ), some time ago, and i'm now facing a new problem with this approach : i want my factory to build an inherited objet declared in a different assembly...the only way i found until now is to make my factory parse every assmebly available in a specific folder in order to find every "type" that would match my object interface... not very clean. Would you have an idea to solve this ? Hello,
i developped quite the same thing (~not generic :( ), some time ago, and i’m now facing a new problem with this approach : i want my factory to build an inherited objet declared in a different assembly…the only way i found until now is to make my factory parse every assmebly available in a specific folder in order to find every “type” that would match my object interface… not very clean. Would you have an idea to solve this ?

]]> Comment on Customizing “lookful” WPF controls – Take 2 by STEVE F http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-148 STEVE F Wed, 16 Sep 2009 19:11:15 +0000 http://tranxcoder.wordpress.com/2008/10/12/customizing-lookful-wpf-controls-take-2/#comment-148 Anyone have code for this working in a textbox. If so could you email it to me at steve_44@inbox.com Anyone have code for this working in a textbox.
If so could you email it to me at steve_44@inbox.com

]]> Comment on Using the VixCOM library by James Bower http://tranxcoder.wordpress.com/2008/05/14/using-the-vixcom-library/#comment-147 James Bower Mon, 07 Sep 2009 21:29:41 +0000 http://tranxcoder.wordpress.com/2008/05/14/using-the-vixcom-library/#comment-147 Great blog, reading it through RSS feed as well Great blog, reading it through RSS feed as well

]]> Comment on A custom task for building WiX under MSBuild (TFS) by hempelcx http://tranxcoder.wordpress.com/2008/07/03/a-custom-task-for-building-wix-under-msbuild-tfs/#comment-145 hempelcx Wed, 26 Aug 2009 19:10:45 +0000 http://tranxcoder.wordpress.com/2008/07/03/a-custom-task-for-building-wix-under-msbuild-tfs/#comment-145 Hi, Sam. Sorry you had trouble. Note that I did specify later in the post that you will need to wrap a root element around the variable definitions. MSBuild will always strip off the outer element that contains the XML document when it passes it to your custom task. <code> <_VariableDefinitions>   <Root>     <VariableDefinition Name=“Var1“ NewValue=“Val1“ />     <VariableDefinition Name=“Var2“ NewValue=“Val2“ />     <VariableDefinition Name=“Var3“ NewValue=“Val3“ />   </Root> </_VariableDefinitions> </code> That outer <code><Root></code> element is required for it to be a valid XML document once the <code><_VariableDefinitions></code> element is stripped. I don't recall what MSBuild will do if it's missing - but sending an invalid document containing just VariableDefinition elements could be the result. Also note that the name of the root element is irrelevant - the XML parsing code doesn't care. Hi, Sam.

Sorry you had trouble. Note that I did specify later in the post that you will need to wrap a root element around the variable definitions. MSBuild will always strip off the outer element that contains the XML document when it passes it to your custom task.

<_VariableDefinitions>
  <Root>
    <VariableDefinition Name=“Var1“ NewValue=“Val1“ />
    <VariableDefinition Name=“Var2“ NewValue=“Val2“ />
    <VariableDefinition Name=“Var3“ NewValue=“Val3“ />
  </Root>
</_VariableDefinitions>

That outer <Root> element is required for it to be a valid XML document once the <_VariableDefinitions> element is stripped. I don’t recall what MSBuild will do if it’s missing – but sending an invalid document containing just VariableDefinition elements could be the result. Also note that the name of the root element is irrelevant – the XML parsing code doesn’t care.

]]>