SMD solutions becoming too large and unmanageable
Hello,
We are currently using several Start-my-day(SMD) solutions for multiple departments within our organisation. When we first started using the SMD's they weren't that big yet, but at this point we are having some very large solutions and they are slowing down developers and users at this point.
We started off by having just SMD's, but more functionality was needed and was implemented into the SMD solutions. Otherwise we had to stop the SMD solution and start an other robot to do some work. This was managable, but this choice made us build more and more into the same solutions.
We are currently looking into how we should proceed. Should we seperate some stuff or are there any other options here on the table that we don't know of.
Do you have any experience in these problems?
Regards,
Niels Lewerissa
Is the problem that you are having is that some of your shared projects for each adapter you wish to use with SMD now contain other logic that you do not wish to include in all of your solutions? If so, then you could consider implementing a business layer project on top of your adapter project. Your adapter projects would only contain whatever minimum functionality you need, while your business layer will contain more complex logic. In your SMD solutions, you would just reference the adapter project, but in your projects that need more functionality, you would reference the business layer project (which would reference the adapter project). This wouldn't make the size of your adapter itself smaller (you'd still have many control interrogated), but the number of automations and things would be less since you'd confine those to another project.