Is your question a sample to illustrate a problem understanding interfaces? Or are you using interfaces in the way you have shown?
If it's the latter, I would design a single class that takes a FileInfo object as parameter and decide within the class (using the extension, for example) how to process it. I wouldn't rely on the client to pass in the correct subclass as shown in your example. But that's just me. On Apr 2, 4:31 pm, "tom.schultz" <[email protected]> wrote: > I have a question > > If I wanted to implements an class that can take files of different > types as input i guess interfaces > Like: > myTextFile = MyFileHost.RequestDocument( ITextFile("test.txt")); > myIniFile = MyFileHost.RequestDocument( IIniFile("test.ini")); > > myTextFile.ReadLine(...); > > myInifile.ReadValue(sSection, sVar); > > Is this even the correct way of doing things in c#, and how would you > implement this? > > regards Tom -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
