4 team member is developing on a server. Now all 4 of them are debugging code for separate modules simultaneously. If one starts debugging others get trouble. How to solve this issue so that both can work simultaneously?

First of all your development environment is not correct, when one dev will debug then IIS reset happens automatically and all other will be impacted. Below is my recommendation

Development Environment:-

It could be a virtual machine with SharePoint standalone installation along with Visual studio, this virtual machine will be assigned to one particular developer

The development environment should have the entire setup of the project (ideally) if you have proper deployment scripts and packaging of your entire SharePoint solution, it can be easily configured on each developers virtual machine

Test Environment:

This environment will have again the entire solution deployed, but this environment would not have any development tools, it is purely for testing by your SIT team.

Hi Nizamuddin,

I have a question here. In your development set up we will create all web applications, site collections etc. through PowerShell scripts. We will maintain all scripts in a document and same scripts can be run in production server. Now If we add any OOB content to various sites (e.g. XSLT list view web part & customize that) through the SP Designer, how can we take those content to the production server? I mean how can we resemble same XSLT web part to the production server in the same site?

For custom development I understand that all will be taken as WSP file, but my question is how SP designer added content will be taken to the server?

Can you please guide what is the actual steps/ process of taking all content to the production server from Development server?

Regards

Hi there,

What you may be looking for is Content Deployment, it does have some obvious boundaries of what it can import and what it can't please read the below as it may be of help.

http://technet.microsoft.com/en-us/library/ee721058(v=office.14).aspx

any reply from Nizamuddin?

Rgds

What you may be looking for is Content Deployment, it does have some obvious boundaries of what it can import and what it can't please read the below as it may be of help.

Question here is, we don't want to take any test data, that is why content DB is not taken, but we want to take all OOB web parts etc created for site collection in the production server? I know how workflow, SSRS, info path etc is taken. They have separate ways. But how to take development with SharePoint designer?

What you may be looking for is Content Deployment, it does have some obvious boundaries of what it can import and what it can't please read the below as it may be of help.

This is totally wrong answer, I wanted some thing else..................

Can any experts reply with real answer for my specific question on deployment of SharePoint Designer content to production server?

"Question here is, we don't want to take any test data, that is why content DB is not taken, but we want to take all OOB web parts etc created for site collection in the production server? I know how workflow, SSRS, info path etc is taken. They have separate ways. But how to take development with SharePoint designer?"

Hi Shml,

Ask your team members to create four different web applications with different application pools so you'll get different w3wp processes for each of them.

Now assign one web application to each of your team members and ask them to debug only their w3wp not all the w3wp.