Question

Je construis un programme VM pour le développement SP 2013.Développera des solutions, des webparts, des formulaires personnalisés, des datavis, une connectivité des données de l'entreprise, des champs personnalisés, des rapports en ligne JQuery, des rapports SSRS pour le déploiement dans SharePoint, etc.

My VM a Windows 2008 EE R2, SQL 2012 Enterprise, Visual Studio 2012, SharePoint Designer 2013.

Dois-je installer SharePoint 2013 autonome ou une ferme?

Je préfère le garder aussi simple que possible et aller autonome, mais vais-je courir dans toutes les limitations. Je serai-je en mesure de déployer des rapports SSRS SQL 2012?Datasources externes pour BDC?Testez l'authentification basée sur les revendications?oauth et odata?Ma préoccupation consiste à installer manuellement tous ces services sur ce devillage de devis si je vais ferme.

Mise à jour: une autre information importante est que le serveur ne sera pas joint à un domaine et n'aura pas accès aux comptes de domaine.Tous les comptes de service doivent être des utilisateurs locaux.

Était-ce utile?

La solution

Going stand alone will only (negatively) impact the security accounts used and the use of SQL Server Express 2008 R2 instead of your own SQL Server 2012 (and of course will prevent any growth later on) Both installations will run the Farm Configuration wizard which will configure most of the service (and you should do it manually to have better control once you'll know what you're doing) if you do not stop it / decline it.

A good guidance is the critical path training. It will help you creating a development frienly environment in minimal time : http://www.andrewconnell.com/blog/archive/2012/08/27/now-available-critical-path-trainingrsquos-sharepoint-2013-setup-guide-for.aspx

Moreover, the kind of development that you'll be doing will heavily benefit from a development environment that is way closer to the target production environment than a quick & dirty "stand alone" deployment which will never be the case in any production environment (avoiding you the "hey it worked on my machine syndrome" when delivering to QA/STG/Prod).

Happy installation :)

Autres conseils

Stand alone will attempt to use SQL server express. I would choose farm.

It is always better to choose the farm installation, if possible. You may later decide to add a few more servers.

You might want to consider performance too. The full version recommends a 4 core processor. I installed it on a VM on my laptop (2 core, 16GB RAM) with 1 core for the VM and performance of the VM tanked compared with the standalone.

Is it not possible to promote the vm to a dc? That way you can use all the goodness having AD gives you. A great guide to setting up a sp 2013 can be found @ www.criticalpathtraining.com in the member section (membership is free). If you want to add mail, use hmailserver...very light

Licencié sous: CC-BY-SA avec attribution
Non affilié à sharepoint.stackexchange
scroll top