>Yes, he did...but it would be better to give him suggestions for things that have a possibility of happening. For example, added functionality in NET4COM to read/write the Windows event log.

I think what will happen is that NET4COM will continue to have additional functions added to it. For example, I helped work out a new classes for XML to be called NET4COM.Xml to surface some cool useful fuctions that VFP (or any COM client) can use for XML validation via XSD, XSLT transformation, XPath queries, XML inferencing (create XSD from an XML doc), etc. using the System.Xml namespace in .NET that go well beyond functionality in the MSXML COM object. What I think can and will happen is another class like NET4COM, maybe NET4COMX, that SednaX project adds which surfaces additional .NET based fuctionality for use within VFP that is not included in NET4COM (a side by side project, rather than exending the NET4COM project itself).

As for the Windows event log stuff, anything that relates to Windows like event log, network drive mapping, file search, sidebar functions, events, etc. will end up being in the Vista Toolkit for VFP (another part of Sedna later) rather than in NET4COM.