How to set up a development environment for sharepoint 2013

Question

I installed the foundation of sharepoint 2013, sql server 2012 on a Windows Server 2012 operating system in a virtual machine.

I need to set up a development environment for sharepoint 2013. Can someone help me on what I need to install separately from this.

I have questions like

Where should Visual Studio 2012 be installed (either on the client or on the server virtual machine)? What components do I need to install? Do I need to install Sharepoint Designer?

Please help me with this.

Hooray!

Answer 1

Here's how to set up your development environment for SharePoint 2013 from Microsoft

on other issues:

• Yes, you must install Visual Studio 2012 on the VM virtual machine in order to be able to develop sharepoint components and debug them.
• you can install the sharepoint designer if you want to edit pages and master pages to add CSS styles and client-side script code. no need to install the sharepoint designer on the server, it can be installed on any machine

Answer 2

Mahmoud Farahat is right, you must install Visual Studio on the same computer on which SharePoint is installed, and make sure that all DLL-specific DLL files are registered in the GAC.

With SP2013, Microsoft no longer allows the installation of SP for anything other than Windows 2012 and 2008R2. 2010 allowed you to install it on Windows 7, which, as I imagine it, is that development locators work, or at least some versions of Windows OS. You had to change the configuration setting in order to be able to do this, you can watch it, but are no longer relevant, since it is impossible. I installed SP2010 on my local laptop and it uses a powerful machine and makes it run horribly for everything. In my opinion, using a local machine for development is simply not practical because SharePoint is just so hungry. I had the launch of 2010 as a locally hosted virtual machine in Virtual Box, and this work is pretty good, so for every developer there is the opportunity to have a virtual machine locally. Our IT users did not like the idea of ​​placing servers in the corporate domain anywhere except for centralized access, so there was no choice for us, but if it is allowed in your policies, then it will work fine.

So, our 2013 development environment that I am setting up is located on a powerful farm with one server, that is, on the application, on the Internet, and on all virtual servers (acceptable for dev). We run multiple developer connections to a single SharePoint development server through Remote Desktop. Make sure that multiple RDP sessions are enabled in Group Policy, http://technet.microsoft.com/en-us/library/cc784146(v=ws.10).aspx . SP2013, VS2012 and SPD oh and IIS8 (Windows 2012) are installed on this server.

Perhaps both are developed in the same web application (SharePoint talks about ISS application pools), but you can only debug one session at a time because devenv.exe (Visual Studio) joins w3ps.exe (IIS application pool) to be able to deploy, install, and activate each of your designed features (more SP talk). Therefore, as soon as one developer connected to the web application for debugging, someone else will receive an error message that there is already a debugger in the process.

There are two solutions, in turn during debugging, this works, but even in a small team of two (there can be no less) this is a big drawback, and especially when launching the debugger can take a couple of minutes even to a powerful server. So what is the other option? Well, you need to create a process for each developer for an individual connection. This applies to web applications in SharePoint. You can achieve all this through central administration, but if you have several developers who do this in the GUI, it can be a little boring for the administrator. Therefore, to achieve the same result using a script, run the following code in PowerShell:

Add-PsSnapin Microsoft.SharePoint.PowerShell New-SPWebApplication -ApplicationPool "SharePoint – DEV1" -Name "SharePoint – DEV1" -ApplicationPoolAccount (Get-SPManagedAccount "yourdomain\service.account") -Port 81 New-SPWebApplication -ApplicationPool "SharePoint – DEV2" -Name "SharePoint – DEV2" -ApplicationPoolAccount (Get-SPManagedAccount "yourdomain\service.account") -Port 82 New-SPSite -Url http://yourspservername:81/sites/YourSiteName -Name YourProjectNameDev -Description "Developer1's Development team site for Your Project" -OwnerAlias yourdomain\developer1.username -Template "STS#0" New-SPSite -Url http:// yourspservername:82/sites/ YourSiteName -Name YourProjectNameDev -Description "Developer2's Development team site for Your Project" -OwnerAlias yourdomain\developer2.username -Template "STS#0" Remove-PsSnapin Microsoft.SharePoint.PowerShell 

It is assumed that you are using NTLM authentication and reading http://technet.microsoft.com/en-us/library/ff607931.aspx to make sure that the New-SPWebApplication command has the appropriate settings for your environment. The code, as is, will also create a content database with the guid suffix, which may not be as clear, so indicate if you want to.

This creates a SiteCollection for each developer and site based on the Site Site template for each developer. Copy each line of a separate line for other developers.

We saved the default web collection on port 80 for the collaborative site, where we deploy all our features for the final test of the combination.

Each developer must edit their Project properties in Visual Studio so that the properties of their site URLs match their individually assigned port.

Be careful when combining projects in your Source control, as this property will be specified in the csproj file, and each developer will place their own port number in the repository.

Answer 3

My original answer is valid and works and seems to be useful to some people. Nevertheless, we quickly ran into difficulties when working even with recently acquired corporate servers with a virtual VMWare server. I think the main problem is Disk IO, and deploying the solution will take 4 minutes +.

Initially, our laptops could not start the local SP2013 virtual machine. If a budget is available and has gone through the entire development cycle, I would strongly recommend using the Oracle VM virtual box and creating a separate instance on each development laptop. The trick for this is the shear specification of the required equipment. 16 GB of RAM is the minimum and realistically requires a 512 GB SSD, although you might be a bit smaller. We have updated our laptops to meet this minimum, and there are not many laptops that are currently capable of more.

So, as soon as you have the equipment, download the virtual virtual box VM and install it on the host. You will need to create a single server farm and allocate 12 GB of memory for the VM, leaving 4 GB for the host. Install Windows Server 2012 on a virtual server, possibly downloaded through an MSDN subscription. You have an ISO loaded on the host laptop, therefore, you need a large disk; it can be removed after installation.

Configuring the network settings for the virtual machine is complex and perhaps different in your environment, but I went to the bridge bridge from the wired network port on the laptop through the dock. This means that the moment you take your laptop from the dock, the virtual machine will lose access to the Internet. You can go to the Wi-Fi port, but all your host file settings will be wrong. Therefore, be careful if you take the laptop a step, waiting for it to work.

Depending on how your enterprise administrators respond to random virtual machines in the corporate domain, you may need to - as I did; to create your own domain. I had to use the SP server to do this, and this is not recommended by Microsoft, but it did not delay me. So I turned the SharePoint server into a domain controller and a DNS server. If you want to develop SharePoint applications, you will need a DNS server. This gave me complete flexibility and control over the environment without any interference or expected others to work for me. The only drawback is cross-domain authentication, so you just need to get used to entering fully qualified domain names of users and have two passwords, and this single input will not work for testing from a local laptop. It doesn't matter how flexible it gives you in return. So, now you have a domain controller, and also create service accounts for SharePoint, as well as a developer account. Now you can start the installation of SharePoint 2013 from the installed ISO, which may be downloaded again through the MSDN subscription. Install Visual Studio 2012 and SharePoint Designer along with any version control tools you want to use.

To communicate between the host and the virtual server in the host host file C: \ Windows \ System32 \ drivers \ etc \ host add an entry for the server. This will allow you to access the server by its name. This must be done because the host and server are in different domains, and the server record is not part of the corporate DNS. Since the virtual cell is configured as a bridged network, and since our environment uses DHCP, rebooting the virtual machine can change the IP address of the field. Be careful if this is the case, you may need to change this periodically while using the box.

You may need to add some proxy settings to the server to access the Internet through the corporate network through the bridge adapter. This will require credentials to authenticate the account of the corporate domain of developers, and not the one used on the server in the newly created domain. For example, I need to add proxy settings to Tortoise HG so that the original control can click on the .org bitpack.

We found that for a single user development, the laptop works much better than the development server that we created on our department servers. It comes down to SSD performance even for enterprise-level SANs. Scaling up to a few users for a live environment is likely to be the opposite, but this approach definitely gave us a significant performance improvement, bringing the code iterate to half the initial deployment time. You can even clone environments for multiple developer laptops by simply copying VM files.