What would make development with SharePoint easier?
+3
A:
Remote Deployment: - 1 central Sharepoint, and transparent remote debugging.
AlexDuggleby
2009-05-17 12:21:56
+9
A:
A better product.
Right now it is to many things that doesn't behave as a development environment should.
- Dispose of objects
- Performance of traversing small lists with 3000/4000 items
- Lack of support of transactions
Hopefully next version will have the SQLServer based lists where you can have transactional support and better performance......
Bill G raised the question in feb 2008 that it is something strange with Sharepoint that you get problems when you have 3000 items in a list and SQL Server easily supports million of items....
salgo60
2009-05-17 16:18:10
Wasd today listen to Martin Fowler who spoke about when software doesn't have the optimal design and when you should add new functionality you have to pay a cost which you don't have to pay if the software was better designed.Th term for this is design debt and that is what we have in the Sharepoint product hopefully 2010 will change that http://www.ibm.com/developerworks/rational/library/edge/09/jun09/designdebteconomics/index.html
salgo60
2009-09-29 19:20:56
+8
A:
The build and deployment process needs to be simplified. There are numerous tools available to create WSP files, but they are all decent at one thing another, but you ultimately need to extend or rework the solution WSP deployment package for you environment.
John Ptacek
2009-05-18 02:36:42
+1
A:
Should check out @SPDevWiki's page on this also http://www.sharepointdevwiki.com/pages/viewpage.action?pageId=7340352
Jeremy Thake
2009-06-22 11:41:45
A:
Less people trying to abuse the product would make things a lot easier too ;)
ArjanP
2009-06-23 10:21:04
Oh negative feedback without a comment? booIMO it's a common source of problems.. people trying to fit the square SharePoint peg in the round hole of their problem..
ArjanP
2009-09-07 06:07:19
+3
A:
Making the dev process more like "traditional" asp.net development, in other words making the integration with VS better. You should develop against SharePoint from within VS not from within SharePoint (ie SPD). SPVisualDev on codeplex has made that process better but I hope (an I say hope) for better support within VS2010 together with SP2010.
Johan Leino
2009-06-23 10:31:27
+4
A:
Informative error messages.
While easier debugging and less XML are very tempting (as people suggested), I would settle for something much more modest.
SharePoint usually "swallows" exceptions or other error messages. Very often when a customized page or a web part fails, you get an obscure 'page cannot be displayed' message. With luck, the designer will direct you to the problem, or you might find some details on the logs or the system event viewer. But in many cases you have nothing.
Examples - Business data catalog xml monstrosity that worked on the editor but not on the site, xml web parts that fail randomly, xsl typos or mistakes, etc. All take much longer to find than they should, and some are impossible to debug.
Kobi
2009-06-23 11:22:43
I hate that "value does not fall within the expected range" exception that pops up whenever something goes wrong in the API.
Ries
2009-08-06 14:18:40