OLD VERSION WINFX VIDEO CONVERTER CODE

If you want to create a completely new parser, inherit from GenericUriParser. You can write these parsers in their entirety, or the parsers can be derived from well-known schemes (HTTP, FTP, and other schemes based on network protocols). The UriParser class enables you to create parsers for new URI schemes. Go to the documentation on MSDN2 for UriParser, you’ll read this:

īefore I start with the nitty-gritty details of building your own UriParser, I’d like to point out something amusing (well, amusing to total nerds who’d rather write about parsing URIs than play video games or watch Arrested Development). They also provided a mechanism to parse URI schemes that the framework doesn’t know about: extend UriParser. It just so happens that they kinda worked around my two earlier complaints: they deprecated those heinous protected methods currently you only get a compiler warning, but it’s a start.

OLD VERSION WINFX VIDEO CONVERTER CODE

Therefore, if you’re using FxCop to check your code against the guidelines, I’d recommend fixing violations of the “Use System.Uri instead of string” rule. Your classes should version well across framework versions if you use their guidelines. Why? Well, with each version of the framework, Microsoft will work to make it better (at least that’s what they promise us). Yet, I’d still recommend you use System.Uri for your URI needs, even if it won’t parse your URI. It won’t parse mailto-style URIs and extending it is just evil. I posted before about my displeasure using System.Uri for advanced scenarios.

Old version winfx video converter