SharePoint 开发人员的个人资料是什么 [英] What is the profile of a SharePoint developer
问题描述
我有一个专门从事 ASP.NET 的开发团队.因此，我们提供的解决方案是基于 Web 的，在 IIS 上运行并使用 MS SQL 服务器.公司内联网内的一切.该团队拥有这方面的专业知识，而且他们在 C# 和 .Net 方面都非常出色.
该公司正在部署 SharePoint MOSS 2007.此部署是我未参与的项目的一部分，我对此的了解很少.但是我知道他们已经建立了思考者"层(那些会说要做什么的人)、集成层(谁将配置、部署和管理生产)，并且他们需要建立所谓的开发层(那些会做其他两人做不到的事情的人).
我被要求评估通过添加 SharePoint 开发来增加团队专业知识的可能性.这是简单的部分，我只需要找到所需的培训并派遣我的人员即可.
然而，现在开发这个词可能意味着很多东西，有时我发现配置被用来代替开发.我不反对通过开发新的专业知识来发展团队，但我想确保让我的开发人员保持兴奋.其次我不想说我们有SharePoint开发专业知识，实际上我们所做的只是修改css或xml文件.此外，我不认为使用向导来生成解决方案是推动 C# 开发人员遵循的最佳途径.
我首先问自己的问题是:SharePoint 开发人员的背景是什么?如果 .Net 开发人员被要求成为 SharePoint 开发人员，他们会有什么感受?
任何想法将不胜感激.
一年多以前，当我在我的公司继承了 WSS 3.0 解决方案时，我开始了 Sharepoint 开发.
我个人认为这是让我稍微了解 Sharepoint 开发的重要一步，有很多问题(例如安全性、负载平衡、重影)很高兴看到 WSS 团队如何解决以及帮助我解决我正在处理的其他解决方案中的问题.但我并不是全职研究 WSS 解决方案，所以其他人每天都必须回答它是如何与 WSS 一起工作的.
WSS 和 Sharepoint 是 ASP.NET 平台上的扩展，因此对于开始创建 Sharepoint 解决方案的开发人员来说，任何 ASP.NET 和 .NET 的一般经验都应该是一个良好的基础.我阅读了Inside Microsoft Windows Sharepoint Services 3.0 一书以便在开始从事 WSS 项目之前了解基本概念和 wss 解决方案架构.
我很快发现您必须有一个用于 Sharepoint 开发的虚拟机环境，这是因为在客户端上工作并附加到服务器上的远程进程以进入调试模式很痛苦.因此，我建议创建一个安装了 Visual Studio 的 MOSS 虚拟机，该虚拟机可以访问您的源代码控制系统.在该机器上开发解决方案，完成后检查源代码管理.
我还建议查看开发工具，例如 stsdev 和 wspbuilder 帮助您构建解决方案，这些将大大简化您的开发过程.网络上也有很多可用的工具，例如codeplex 为您提供帮助.
有时开发这些解决方案可能会很痛苦，更改可能需要回收 IIS 池或暴力 IISReset，错误消息有时可能有点神秘等等.但是您很快就会了解并知道该看哪里.Sharepoint 也为您提供了很多帮助，我收到了来自客户的数百万个问题，可以使用标准的现成 Web 部件解决这些问题，因此我不必编写任何代码来让我的客户满意 :)
Sharepoint 还希望以某种方式对解决方案进行编码，例如12 hive 文件结构，因此它可以帮助您标准化您的解决方案.
严重缺乏文档，因此您必须大量依赖 Reflector 和此类工具，才能了解框架内发生的情况，希望 2010 年会变得更好.
初始学习曲线很高，需要学习很多新概念和技术，例如共享点、特征、重影和代码访问安全中的工作流Sharepoint 使用的 Xml 配置有很多开发人员必须学习，这包括站点定义、列表模板等.有时有时我会卡在 Xml 编辑模式中，无法弄清楚为什么事情不能正常工作
这些只是我的一些想法，我一直主要从事 WSS 开发，如果有人可以评论 Sharepoint 中的 Web 部件配置，例如配置搜索.这是我很少做的事情.
I have a development team specialized in ASP.NET. So the solutions we provide are web based, running on IIS and using MS SQL server. Everything within the intranet of the company. The team has this expertise, and they are excellent in C#, and .Net in general.
The company is deploying SharePoint MOSS 2007. This deployment is part of a project that I am not involved in, and for which I have very little information. However I know that they have established the "thinkers" layer (those who will say what to do), the integrations layer (the who will configure, deploy and manage the production), and that they need to establish the so called development layer (those who will do things the other two can't).
I am asked to evaluate the possibility to increase my team's expertise by adding SharePoint development. This is the easy part, I just have to find the required training and send my people.
However these days the word development could mean a lot of things and sometimes I discover that configuration is used in place of development. I don't have any objections to evolve the team by developing new expertise, but I want to be sure to keep things stimulating for my developers. Secondly I don't want to say that we have SharePoint development expertise, and actually what we do is just modifying css or xml files. Also, I don't think that using wizards to produce a solution is the best path to push a C# developer to follow.
The questions I am asking myself first is : what is the background of a SharePoint developer? how could .Net developers feel if asked to become SharePoint developers?
Any thoughts will be greatly appreciated.
I started in Sharepoint development over a year ago when I inherited a WSS 3.0 solution at my company.
Personally I think it was a great step for me getting to know Sharepoint development a little, there are a lot of problems (e.g. security, load – balance, ghosting) that was good to see how was solved by the WSS team and helps me solve problems in other solutions I‘m working on. But I don‘t work on WSS solutions full time, so others have to anwer how it is working with WSS every day.
WSS and Sharepoint are an extension on the ASP.NET platform, so any experience in ASP.NET and .NET in general should be a good foundation for a developer that is starting creating Sharepoint solutions. I read the Inside Microsoft Windows Sharepoint Services 3.0 book in order to get the basic concepts and wss solution architecuture before I started working on WSS projects.
I quickly found out that you have to have a Virtual Machine environment for Sharepoint development, this is because it‘s a pain working on a client and attaching to a remote process on the server to get in debug mode. Therefore I recommend creating a MOSS virtual machine that has Visual Studio installed that has access to your source control system. Develop solutions on that machine and when finished then check into source control.
I also recommend looking at development tools, such as stsdev and wspbuilder to help you building your solution, these will ease you development process quite a bit. There are also quite a lot of tools available on the web, e.g. codeplex to help you out.
Sometimes it can be a pain developing these solutions, changes can require recycling the IIS pool or a brute-force IISReset, error messages can sometimes by a little cryptic and so on. But you quickly catch on and know where to look. Sharepoint also helps you out a lot, I‘ve had millions of questions from clients that can be solved with standard out-of the box web parts, so that I don‘t have to code anhything to keep my clients happy :)
Sharepoint also expects solutions to be coded in certain way, e.g. 12 hive filestructure so it helps you standardizing your solutions.
There is a serious lack of documentation, so that you have to rely on Reflector and such tools a lot, just to know what is happening within the framework, hopefully this gets better with 2010.
The initial learning curve is high, and a lot of new concepts an technologies to learn ,e.g. Workflows within sharepoint, featuers, ghosting and code access security There is a lot of Xml configuration that sharepoint uses that developers have to learn, this includes the site definition, list templates and more. There are sometimes days when I‘m stuck in Xml edit mode and can‘t figure out why things don‘t work as they should do
These are just few of my thought, I‘ve been working mainly in WSS development and it would be great if someone could comment regarding web part configuration in Sharepoint, e.g. configuring the search. Which is something I haven‘t been doing a lot of.
这篇关于SharePoint 开发人员的个人资料是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
