I've been working with SharePoint now for just over a month and I have to admit building a web application is quick and fairly easily. My first impressions of the platform were not good and I may have been a bit harsh on some points, but I do still feel if this application was to grow it would need a relational database. I know it is possible to import a relational database into SharePoint but the way SharePoint is set up for this project it's not possible.
SharePoint has helped so much with the speed of the development, I could not have gotten this far with the prototype if I was building it from scratch using ASP or JSP or PHP etc. It is also a testament to Microsoft for the support they have for their products. There are so many official resources on top of the large number of developer communities, which has helped immensely in troubleshooting and I've gotten some fantastic tips.
Everything is not exactly clear sailing as I am finding some restrictions developing for the platform. In some cases I can see where lower level coding would provide an easy solution but on SharePoint you need to use a work around. I suppose on the other hand lower level coding would be time consuming and in the end, there are work arounds. Solutions for SharePoint has forced me to think in a different way than I am used to when creating products for the web, and that has to be a good thing.
At the moment I'm working on two problems I'm having with SharePoint. One of which I've just about solved and I will post up a tutorial when I'm finished.
SharePoint has helped so much with the speed of the development, I could not have gotten this far with the prototype if I was building it from scratch using ASP or JSP or PHP etc. It is also a testament to Microsoft for the support they have for their products. There are so many official resources on top of the large number of developer communities, which has helped immensely in troubleshooting and I've gotten some fantastic tips.
Everything is not exactly clear sailing as I am finding some restrictions developing for the platform. In some cases I can see where lower level coding would provide an easy solution but on SharePoint you need to use a work around. I suppose on the other hand lower level coding would be time consuming and in the end, there are work arounds. Solutions for SharePoint has forced me to think in a different way than I am used to when creating products for the web, and that has to be a good thing.
At the moment I'm working on two problems I'm having with SharePoint. One of which I've just about solved and I will post up a tutorial when I'm finished.
No comments:
Post a Comment