We are at the beginning of developing for Sharepoint 2007. It has however occured to me that with .NET 3.5 on the horizon (with Orcas release of Visual Studio) will we be locked into coding .NET 2.0 (and 3.0 with the right wrappers) until Sharepoint is updated
What is the roadmap for this as it has implications for our ability to keep pace with current technology if we are tied to the Sharepoint platform for development
Sharepoint development future? .NET 3.5 and beyond...
Hot Topic
- Simple Class question regarding hierarchies or Parent Child relationships.
- Artifacts can we/should we version for SharePoint development
- Data Access layer generation tool query
- Typed Dataset or Custom Classes
- how to quote content
- Delete Extended Web Apps?
- Clustered .NET Applications
- OHSBE Message formats
- Should a good business tier provide async methods?
- Visio reports
SharePoint Products
- layout templates
- Sharepoint error when adding Web Part
- How are you gnerating application definitions?
- Drop Down Menus on Navigation Bar
- ReadOnly Fields in a WebPart
- Source code control using MOSS 2007
- Displaying InfoPath browser form within master page content
- Performance issue become worse upon split out Web Applications into web server and DB server
- Scalable Windows services
- Trying to figure out the max. number of concurrent users/requests for a single server.
Sharepoint development future? .NET 3.5 and beyond...
Ray Dyce
I have not seen any roadmap for the future of SharePoint nor its development platform which makes sense since things are probably just in the planning stage.
Without trying to sound too flippant if you are worried about future directions you will never develop for right now
Shadi Mari
True,.. but if Sharepoint isn't going to be able to leaverage the gradually evolving .NET platform, then we are currently in a position to switch to building our own portal and making use of Sharepoint via Services.
With a 5 year life span on an intranet, it is a consideration, we don't want to be in a technology cul-de-sac for that time :)