Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Timothy's question, as applied generally to the question of Type conversion in .NET, is a very big issue. While conversion strategies are somewhat straightforward in specific scenarios with known types, unfortunately there is no generalized strategy in any implementation of .NET to accomplish Type conversion at run-time from one arbitrary Type to another, nor is such a strategy forthcoming from Redmond. However, Microsoft supplies some good guidelines for the general concept of Type conversion, including:</p> <ul> <li><a href="http://msdn.microsoft.com/en-us/library/98bbex99.aspx" rel="nofollow">Type Conversion in the .NET Framework</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/ms173105.aspx" rel="nofollow">Casting and Type Conversions (C# Programming Guide)</a></li> <li><a href="http://msdn.microsoft.com/en-us/library/cc645047%28v=VS.95%29.aspx" rel="nofollow">TypeConverters and XAML</a></li> </ul> <p>I have had to deal with the same general issue in my systems, and as a solution I have consolidated all the standard strategies into one method. The scope of this issue is broad and the related conversion strategies are varied, so this consolidated approach can only be covered in a complete technical article. However, I offer here a copy of my method documentation in hopes this will help you get a firm grasp on the overall requirements you will need to address if you want to develop a similar, generalized solution. Here's the link to my documentation:</p> <ul> <li><a href="http://mjappfactory.com/Links/ConvertType.pdf" rel="nofollow">ConvertType method</a></li> </ul> <p>I hope this helps you out,</p> <p>Mark</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload