What is difference in developing applications using .Net Framework, Asp.net and developing application in Sharepoint (MOSS or WSS)?
使用.Net Framework,Asp.net开发应用程序和在Sharepoint(MOSS或WSS)中开发应用程序有何不同?
5 个解决方案
#1
I highly recommend checking out this thread for various pain points:
我强烈建议您查看此主题以了解各种难点:
https://*.com/questions/256407
Since SharePoint is built on ASP.NET, the argument can be made that anything you can do with ASP.NET you can do with SharePoint but the reality is developing applications for SharePoint is not for the faint-hearted and you should expect a much longer development cycle, particularly if you are new to the platform. I suggest becoming very familiar with Google, *, and .NET Reflector because a lot of what you need to know is not in the documentation or hard to find.
由于SharePoint是基于ASP.NET构建的,因此可以说你可以使用ASP.NET做任何可以用SharePoint做的事情,但现实是为SharePoint开发应用程序并不适合胆小的人,你应该期待更长的时间开发周期,特别是如果您是平台的新手。我建议您熟悉Google,*和.NET Reflector,因为很多您需要了解的内容不在文档中或很难找到。
It's not all bad though. You get a lot of infrastructure out of the box like authentication, versioning of data (if you are storing your data in lists), and incoming/outgoing email connectivity to name a few.
虽然这并不全是坏事。您可以获得大量开箱即用的基础设施,例如身份验证,数据版本控制(如果您将数据存储在列表中),以及传入/传出电子邮件连接等等。
#2
Sharepoint is a collaboration tool built on top of .NET and ASP.NET. To develop applications for Sharepoint means you still need familiarity with ASP.NET and the .NET Framework, but also familiarity with the Sharepoint infrastructure/API's.
Sharepoint是一个基于.NET和ASP.NET构建的协作工具。为Sharepoint开发应用程序意味着您仍然需要熟悉ASP.NET和.NET Framework,但也熟悉Sharepoint infrastructure / API。
#3
Depends on what sort of stuff you want to do really. There are many points in SharePoint that are exposed for you to build on. For simple requirements one of these points of development will suffice but for typical business applications on SharePoint you use a combination of features such as workflow, event receivers, timer jobs, web parts, sites and lists. C# code can run in a workflow, an event reciever, the code-behind library attached to an infopath form.
取决于你想要做什么样的东西。 SharePoint中有许多要点可供构建的点。对于简单的要求,其中一个开发点就足够了,但对于SharePoint上的典型业务应用程序,您可以使用工作流,事件接收器,计时器作业,Web部件,站点和列表等功能的组合。 C#代码可以在工作流,事件接收器,附加到infopath表单的代码隐藏库中运行。
Essencially SharePoint gives you a collaboration platform to develop on to enable all sorts of things. Be warned thou, it certainly isn't as painless as straight C# development and requires lots of technologies and thus lots of new learning. However it's a been a very rewarding experience for me.
Essencially SharePoint为您提供了一个协作平台,可以开发各种各样的东西。请注意,它肯定不像直接的C#开发那么轻松,需要大量的技术,因此需要大量的新学习。然而,这对我来说是一次非常有益的经历。
#4
SharePoint is working with canned but modifiable website templates (WSPs) inside a of an system with a really long feature list-- including an abstraction over the data store (lists), the templating engine, work flow features, etc, etc.
SharePoint正在使用具有非常长的功能列表的系统内的固定但可修改的网站模板(WSP) - 包括对数据存储(列表)的抽象,模板引擎,工作流功能等。
The other is custom development of websites from scratch.
另一种是从头开始定制网站开发。
You can have it both ways. SharePoint itself was build with ASP.NET 2.0, so you can host aspx and with some effort ascx pages inside of SharePoint. Once inside SharePoint, any custom written .NET code can take advantage of the SharePoint object model. This works best if a custom application from the start is planned to be hosted in SharePoint.
你可以两种方式。 SharePoint本身是使用ASP.NET 2.0构建的,因此您可以在SharePoint内部托管aspx并使用一些ascx页面。进入SharePoint后,任何自定义编写的.NET代码都可以利用SharePoint对象模型。如果计划从一开始就在SharePoint中托管自定义应用程序,则此方法效果最佳。
#5
Deploying your solution. SharePoint uses WSP files while ASP.Net supports copy/paste.
部署您的解决方案。 SharePoint使用WSP文件,而ASP.Net支持复制/粘贴。
Think of SharePoint as a framework that sits on top of ASP.Net. There are rules to use this framework, try your best to abide by the rules.
将SharePoint视为一个位于ASP.Net之上的框架。有使用此框架的规则,请尽量遵守规则。
#1
I highly recommend checking out this thread for various pain points:
我强烈建议您查看此主题以了解各种难点:
https://*.com/questions/256407
Since SharePoint is built on ASP.NET, the argument can be made that anything you can do with ASP.NET you can do with SharePoint but the reality is developing applications for SharePoint is not for the faint-hearted and you should expect a much longer development cycle, particularly if you are new to the platform. I suggest becoming very familiar with Google, *, and .NET Reflector because a lot of what you need to know is not in the documentation or hard to find.
由于SharePoint是基于ASP.NET构建的,因此可以说你可以使用ASP.NET做任何可以用SharePoint做的事情,但现实是为SharePoint开发应用程序并不适合胆小的人,你应该期待更长的时间开发周期,特别是如果您是平台的新手。我建议您熟悉Google,*和.NET Reflector,因为很多您需要了解的内容不在文档中或很难找到。
It's not all bad though. You get a lot of infrastructure out of the box like authentication, versioning of data (if you are storing your data in lists), and incoming/outgoing email connectivity to name a few.
虽然这并不全是坏事。您可以获得大量开箱即用的基础设施,例如身份验证,数据版本控制(如果您将数据存储在列表中),以及传入/传出电子邮件连接等等。
#2
Sharepoint is a collaboration tool built on top of .NET and ASP.NET. To develop applications for Sharepoint means you still need familiarity with ASP.NET and the .NET Framework, but also familiarity with the Sharepoint infrastructure/API's.
Sharepoint是一个基于.NET和ASP.NET构建的协作工具。为Sharepoint开发应用程序意味着您仍然需要熟悉ASP.NET和.NET Framework,但也熟悉Sharepoint infrastructure / API。
#3
Depends on what sort of stuff you want to do really. There are many points in SharePoint that are exposed for you to build on. For simple requirements one of these points of development will suffice but for typical business applications on SharePoint you use a combination of features such as workflow, event receivers, timer jobs, web parts, sites and lists. C# code can run in a workflow, an event reciever, the code-behind library attached to an infopath form.
取决于你想要做什么样的东西。 SharePoint中有许多要点可供构建的点。对于简单的要求,其中一个开发点就足够了,但对于SharePoint上的典型业务应用程序,您可以使用工作流,事件接收器,计时器作业,Web部件,站点和列表等功能的组合。 C#代码可以在工作流,事件接收器,附加到infopath表单的代码隐藏库中运行。
Essencially SharePoint gives you a collaboration platform to develop on to enable all sorts of things. Be warned thou, it certainly isn't as painless as straight C# development and requires lots of technologies and thus lots of new learning. However it's a been a very rewarding experience for me.
Essencially SharePoint为您提供了一个协作平台,可以开发各种各样的东西。请注意,它肯定不像直接的C#开发那么轻松,需要大量的技术,因此需要大量的新学习。然而,这对我来说是一次非常有益的经历。
#4
SharePoint is working with canned but modifiable website templates (WSPs) inside a of an system with a really long feature list-- including an abstraction over the data store (lists), the templating engine, work flow features, etc, etc.
SharePoint正在使用具有非常长的功能列表的系统内的固定但可修改的网站模板(WSP) - 包括对数据存储(列表)的抽象,模板引擎,工作流功能等。
The other is custom development of websites from scratch.
另一种是从头开始定制网站开发。
You can have it both ways. SharePoint itself was build with ASP.NET 2.0, so you can host aspx and with some effort ascx pages inside of SharePoint. Once inside SharePoint, any custom written .NET code can take advantage of the SharePoint object model. This works best if a custom application from the start is planned to be hosted in SharePoint.
你可以两种方式。 SharePoint本身是使用ASP.NET 2.0构建的,因此您可以在SharePoint内部托管aspx并使用一些ascx页面。进入SharePoint后,任何自定义编写的.NET代码都可以利用SharePoint对象模型。如果计划从一开始就在SharePoint中托管自定义应用程序,则此方法效果最佳。
#5
Deploying your solution. SharePoint uses WSP files while ASP.Net supports copy/paste.
部署您的解决方案。 SharePoint使用WSP文件,而ASP.Net支持复制/粘贴。
Think of SharePoint as a framework that sits on top of ASP.Net. There are rules to use this framework, try your best to abide by the rules.
将SharePoint视为一个位于ASP.Net之上的框架。有使用此框架的规则,请尽量遵守规则。