.Domino Framework

I have just finished expanding the Domino.Reflection namespace to allow the new Inspector tool to browse the contents of LotusScript libraries. 

Inspector will be able to display information about data documents, profile documents, design documents, and deletion stubs found in ANY database. Inspector will be able to provide a list of all (or selected) design documents found in a database (Domino Designer is not required).

As part of the display information for Design documents I have decided to provide information about any classes found in a selected LotusScript library.  Using the extended DominoScriptLibrary class (part of the Domino.Reflection namespace), I can now return a list of properties and methods for a nominated class.  I can also get the code used  for any one of the properties/methods.  Combining these features together Inspector becomes (amongst other things) a basic class browser for LotusScript libraries.

Both the extended Domino.Reflection namespace and the new Inspector tool will be released as part of the 0.5 beta of the .Domino Framework planned for the end of this week.

An application I am working on has the need to change view selection formuale from time to time and we wanted to avoid the need to deploy a new version of the application each and every time such a change was needed due to the high cost of the change control/release process (man I love SDLCs....)

Given the NotesView class has a read/write SelectionFormula property I have been able to develop an extension Domino.Reflection namespace to coordinate the activities associated with modifying the view selection formulae at run time.  A special Admin form is provided in the application which allows an administrator/developer to select a view and then change the view selection formulae directly.  I have developed a demo of this functionality that will be included in the .Domino Framework database when it is posted on the OpenNTF Web site.