Hello all,I have been on this project for a while and wanted to get your thoughts.I have been working on a Sharepoint solution for a while to create a ASP .Net feature in Visual Studio. Now this is your standard CRUD application that queries data, displays data, updates data etc.As I am proceeding to code in this the original developer has used quite a few patterns MVP, observer, commands, repository and a couple of others. Being that this is Sharepoint developement and integration with Sharepoint is not good at all, I am finding that to much time is spent managing facets of the patterns rather than actually finishing the app. Another point is that debugging a Sharepont app with VS2008 is a pain because I have to redeploy the app everytime to make sure my changes worked.My chief concern is that its taking me going through about5 hours, 8 different objects having to redeploy the app to sharepoint over 10 times to test my code just to populate a couple of grids and comboboxes. It just seems more efficient use of my time program this app just seperating out my data access and business logic layers and calling the them from my code behind in my ASP .Net pages. It just seemed like he used the patterns just to use them without understanding why they are needed or a patterns proper place in an app..What do you guys think?
View Complete Post