I am looking for tips and figure some people here could short cut this for me. We will be building interfaces to a variety of back end systems that will be called from K2 processes via smart objects. Right now I am using the dynamic assembly service in my prototyping. I organize my c# project into folders and classes like the text below. Unfortunately, this ends up with lots of "folders" named Class1 where you can drill down to methods named "static method 1". In short what is missing is the folder name that gives meaning to the otherwise identically named classes. Is there any way around this?
If I wasn't using the dynamic assembly service, would I have another level of categorization available to me?
Service Object Assembly Project
-- business system 1 (project folder)
-- class 1 (class file in folder)
-- static method 1
-- static method 2
-- business system 2 (project folder)
-- class 1 (class file in folder)
-- static method 1
-- static method 2
Thanks!