问题如题。
以前没有接触过sharepoint，领导给了我一个已经做好并运行在服务器上的网站源代码，让我将它移到sharepoint平台上。
因为之前做网站的公司每月要收网站维修费用，公司自己买了sharepoint的东西，运行到sharepoint平台上可以省下这笔钱。
请各位大侠不吝赐教，感激不尽！！！
------解决方案--------------------
php看來只能用iframe把它包住了
------解决方案--------------------
用SharePoint 2013 的Cloud App可以实现，但是未必省钱。
http://www.simple-talk.com/dotnet/.net-tools/an-overview-of-sharepoint-2013-app-development-model/
Building Useful Apps without Server Side Code on SharePoint
The Client-Side Object Model (CSOM) was one of the areas into which Microsoft poured a ton of work. SharePoint 2010 had a very limited set of functionality, but the CSOM in SharePoint 2013 really allows you to execute just about any operation you can think of. As you can imagine, you must have a fully-functional client-side API when you are trying to encourage people to move away from using server side code.
There are three ways that you can access CSOM functionality, so the deployment model that you are using for your SharePoint 2013 app will determine he option that you choose.
?.NET / Silverlight API
?JavaScript API
?REST API
SharePoint-Hosted App
If you plan to use a SharePoint-Hosted deployment model, then you are limited to static files. However, static files can include JavaScript and Silverlight XAP files that run dynamic code on the client side. As such, you are likely to employ the JavaScript API if you’re coding on an HTML / ASPX page or the Silverlight runtime if you decide to deploy a Silverlight XAP file. You can technically use the REST API from JavaScript and Silverlight if you so wish, but the other APIs are a better fit.
GimmalSoft opted for the SharePoint-Hosted App model because our Gimmal Drop Zone App for SharePoint 2013 in the Office Store actually started out as a Silverlight component for SharePoint 2010 and was a natural fit for converting into a SharePoint 2013 app.
[color=#FFFF00]Self-Hosted App[/color]
A self-hosted App can take on a number of forms because it can run on any number of different operating systems with any number of different application servers. If you opt for this deployment model, then I assume you want to run server-side code. If you are hosting on a server that runs ASP.NET, then it is a natural fit to use the .NET API. If you are running a LINUX / UNIX system then the REST API is going to be a better fit because most non-Windows servers really don’t run .NET code. JavaScript and Silverlight are available in any deployment model, but these are both client-side and not server-side technologies.