SharePoint来一个C＃ASP.NET开发 [英] SharePoint for a C# ASP.NET Developer

问题描述

我一直在问到接下来的几个星期内创建 的SharePoint网站或如此，我M全新到SharePoint。

I've been asked to create a website in SharePoint within the next couple of weeks or so and I'm entirely new to SharePoint.

有没有人对如何做一些基本操作的很好的例子/教程，如创建自定义表单，使用基本的 CRUD操作，使用自定义的SQL Server数据库？

Does anyone have any good examples/tutorials on how to do some basic operations such as creating custom forms, using basic CRUD operations, with a custom SQL Server database?

也就是有什么办法可以在ASP.NET code（带 code-的背后页），但使用SharePoint外观和身份验证的东西？

Also is there any way to code in ASP.NET (with code-behind pages), but use the SharePoint look and feel and authentication stuff?

推荐答案

的SharePoint不是的非常的像你习惯的方式。我的两个主要的抱怨是：

SharePoint is not quite like what you're used to. My two main gripes are:

部署：

如果您的要求是单一的生产现场（无分期/测试/开发网站）你最好的选择可能是一起去的 SharePoint设计一起直接在生产现场破解的东西（是的，我知道这是肮脏的）。

If your requirements are for a single production site (no staging/test/development sites) your best bet is probably to go with the SharePoint Designer and hack stuff together directly on the production site (yes I know it's dirty).

如果你需要，你应出示部署包其他环境中的一切（无Xcopy部署）。部署包是 PITA 恕我直言，并的非常的容易出错。

If you need those other environments you should produce deployment packages for everything (no xcopy deployment). Deployment packages are a PITA IMHO and are very easy to get wrong.

IIS

基本的SharePoint接管你的 IIS安装并介绍了那里的东西都位于一套新的规则等有一个问题是幻像的文件。即当文件使用SharePoint Designer中的文件备份到数据库，并从现在开始，IIS将只使用在数据库中的文件发生变化，所以没有使用改变一个在文件系统中。

SharePoint basically takes over your IIS installation and introduces a new set of rules for where things are located etc. One gotcha is "ghosted" files. i.e. whenever a file is changed using the SharePoint Designer the file is backed up to a database and from now on IIS will only use the file in the database, so there is no use changing the one in the file system.

综上所述：

在我的愚见，如果你正在一个站点，运行时间不是重要的，你能负担得起，使生产的失误时，SharePoint可不够好与设计师。如果你正在你需要的code要经过之前多环境中 CMS 网站达到生产，（与持续集成），我能想到的任何其他基于.NET的CMS，做一个更坏的工作。你会花很多时间所著的Grokking如何让部署例程来为你工作，你会花很多时间与有关幻像的文件问题

In my humble opinion if you are making a site where uptime isn't that important and you can afford to make mistakes in production, SharePoint can be good enough with the designer. If you are making a CMS site where you need the code to go through multiple environments before it reaches production, (with continuous integration), I can think of no other .NET based CMS that does a worse job. You will spend a LOT of time grokking how to get the deployment routines to work for you, and you will spend a LOT of time with issues relating to "ghosted" files

祝你好运。

这篇关于SharePoint来一个C＃ASP.NET开发的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！