I often come up with solutions or possibilities while exercising. It typically happens on my treadmill when I'm about half way into the routine. Then I'm debating 'Do I get off the treadmill and mark it down now or wait?' If I wait, I'm impatient to get through the rest of my exercise routine and it's supposed to be relaxing! :o)



>Whilst on my exercise machine, I suddenly thought about my example partial class code. I just want to make it absolutely clear that the name of the partial class code files have no bearing on the type, number or names of the contained members.
>
>It could be construed from my sample code that a partial class code file called CharlesHankey.Compression.cs contains a single member called Compression. This is not the case; CharlesHankey.Compression.cs merely serves to differentiate the code file from CharlesHankey.Backup.cs - as long as you maintain the "partial class CharlesHankey" construct within the codefiles, the compiler couldn't care less what members you put in each code file/partial class definition. The only requirement is that the members are unique, overloaded methods notwithstanding.
>
>I hope this clarifies any potential confusion caused. If not, feel free to come back to me on this.
>
>-=Gary
>
>
>>>>I'll go for two rounds and throw in some crisps.
>>>
>>>The last of the big spenders :)
>>>
>>
>>Alright, I admit Wiltshire ( Malmesbury ) only represents half the ancestral homeland. The rest is up somewhere between Aberdeen and Inverness < g >