如何把做好的网站（用php写的）移到sharepoint平台上
问题如题。
以前没有接触过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.
Azure Provisioned App
Azure is a .NET technology, so it makes the most sense to use the .NET API when implementing an Azure-provisioned application. Once again, note that you have the option of using any CSOM API mode that you want in an Azure application, but the .NET CSOM assemblies are the best fit, considering that Azure is running on the .NET platform.
[解决办法]
Self-Hosted App
A Self-Hosted App is an application where the files for the application exist on an external server (e.g. you are hosting those files yourself somewhere outside of SharePoint). When a user accesses your application, they are redirected to a page on this external server where the application resides. In this model, you can run server-side code, but it has to be run on the external server. There is still no way to run custom code on the SharePoint server. One of the benefits of this model is that the external server does not need to be a Windows server: SharePoint is really just redirecting users to a web page, so you can use any operating system and application server you want as long as it can fulfill web requests. You could be a PHP developer with a Linux machine and still make SharePoint apps.
Another interesting reason to use this model is that it puts you in complete control of upgrades. Since you own the server, you can deploy updates and have them applied immediately for all of your clients. In the other models, the user has to take some action to upgrade because you do not have access to the server on which the App is hosted.
[解决办法]
个人建议：
最好不要这样迁移根本没有用，sharepiont的体系、机制、基本架构你看一下。
用ifram 就没有意义了。
[解决办法]
如果你真的想做迁移，考虑下面几个步骤:
1.静态页面的迁移
2.动态页面的迁移
3.中间应用程序的迁移
4.底层数据库的迁移
[解决办法]
工作量会比较大， 我迁移过一个出差管理模块进sharepoint
[解决办法]
如果你原来的网站是用CMS或者smarty这种东西做的，相对容易，sp开发是.net的语言，asp.net本来就是代码分类的，直接把潜入PHP中的字段改成.net或者sp控件就可以了。数据用sp中的列表去完成。
另外，sp开发的本质其实是webservice程序，所以你可以直接建立一个普通的ASP.NET程序。然后调用sp。
