面向 C# ASP.NET 开发人员的 SharePoint

问题描述

我被要求在接下来的几周内在 SharePoint 中创建一个网站，或者所以我对 SharePoint 完全陌生.

有没有人有关于如何使用基本的CRUD 操作，使用自定义SQL Server 数据库?>

还有什么方法可以在 ASP.NET 中编码(使用 code-behind 页面)，但使用 SharePoint 外观和身份验证内容?

解决方案

SharePoint 与您习惯的完全不同.我的两个主要抱怨是:

部署:

如果您的要求是针对单个生产站点(无暂存/测试/开发站点)，您最好的选择可能是使用 SharePoint Designer 并直接在生产站点上将内容组合在一起(是的，我知道这很脏).

如果您需要那些其他环境，您应该为所有内容生成部署包(无 xcopy 部署).部署包是 PITA 恕我直言，非常容易出错.

IIS

SharePoint 基本上接管了您的 IIS 安装并引入了一套新的规则来说明事物的位置定位等.一个问题是幻影"文件.即，每当使用 SharePoint Designer 更改文件时，该文件都会备份到数据库中，从现在开始 IIS 将只使用数据库中的文件，因此更改文件系统中的文件没有用.

总结:

以我的拙见，如果您正在制作一个正常运行时间不是那么重要的网站，并且您可以承受在生产中犯的错误，SharePoint 对设计师来说就足够了.如果您正在制作 CMS 站点，您需要在该站点中代码在进入生产环境之前通过多个环境，(使用 持续集成)，我想不出其他基于 .NET 的 CMS 做得更糟工作.您将花费大量时间研究如何让部署例程为您工作，并且您将花费大量时间处理与幻影"文件相关的问题

祝你好运.

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.

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?

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 is not quite like what you're used to. My two main gripes are:

Deployment:

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).

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 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.

To sum up:

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

Good luck.

这篇关于面向 C# ASP.NET 开发人员的 SharePoint的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！