|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Publishing the methods with parametersI am having an application which is pluggable to other applications. In this application there are some state transitions defining based on the business rules. As business rules are specific to the main application. This pluggable application provides an interface where the main application and this application understands. The business rules are defined in the .Net DLL in the main application with Some classes and some methods. Ex: Approval.Dll In this DLL i am having ApprovalRules class with methods CheckUnitStock(int unitValue,float stock) CheckUnitValue(float stock,bool isStockCalculated,int unitValue) etc....... i have approval mechanism in the pluggable application. I will specify in an XML which DLL have to use and what is the class in the DLL to configure the business rules (like CheckUnitStock,CheckUnitValue etc...). These methods should be published to the pluggable application in this format CheckUnitStock($UnitValue$,$Stock$)... This is just a publisher which the user will understands. So really it nothing but giving some publisher text for the Methods to make user understand what they are doing.... So what is your question?
Bryan Phillips MCSD, MCDBA, MCSE Blog: http://bphillips76.spaces.live.com Show quote "ramnadh" <ramnadh.nall***@gmail.com> wrote in message news:1161708818.330706.191260@k70g2000cwa.googlegroups.com: > I am using .net framework 1.1. > > I am having an application which is pluggable to other applications. In > this application there are some state transitions defining based on the > business rules. As business rules are specific to the main application. > This pluggable application provides an interface where the main > application and this application understands. The business rules are > defined in the .Net DLL in the main application with Some classes and > some methods. > > Ex: Approval.Dll > > In this DLL i am having ApprovalRules class with methods > > CheckUnitStock(int unitValue,float stock) > > CheckUnitValue(float stock,bool isStockCalculated,int unitValue) > > etc....... > > i have approval mechanism in the pluggable application. I will specify > in an XML which DLL have to use and what is the class in the DLL to > configure the business rules (like CheckUnitStock,CheckUnitValue > etc...). These methods should be published to the pluggable application > in this format > > CheckUnitStock($UnitValue$,$Stock$)... > > This is just a publisher which the user will understands. So really it > nothing but giving some publisher text for the Methods to make user > understand what they are doing.... |
|||||||||||||||||||||||