In my feature request I mentioned that RS could invoke a special AssertException exception. On trapping the exception object one would then be able to examine properties on that object to determine the info and present any alert or log it as one sees fit. I was not expecting the Assert command to automatically present any window or do any logging itself, merely trigger an exception.
For example the AssertException class would have the following examinable properties: AssertException.MethodName As String AssertException.ClassName As String AssertException.LineNumber As String AssertException.TestCondition As String AssertException.Message As String //optional string passed to Assert() AssertException.ID As String // optional ID passed to Assert() On 22/11/06 15:12, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > It's also not clear to me how RS could write this Assert method for > you. I'm quite sure they don't know what I want it to do, since in > different projects I may have it do different things. One client wants > it to display a message box; another wants it to use System.DebugLog; a > third wants the error written to their own log file. If they were to > implement it, what makes you think they would choose whatever > functionality you happen to prefer? _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
