We are 2 developers using remotely a server machine that hosts sharepoint 2010. Our problem is when we debug a webpart solution IIS restarts automatically so every time we have to wait for each other to finish debugging before we can test our own webpart.
any solution please?
The best practice for nearly any web development work is to setup every developer to have their own sandbox copy of the site. With SharePoint, this typically means a local virtual machine due to the nature of the beast.
Related
We work for a small firm and we just started getting few SharePoint Projects.
Setup what we have done:
Purchased a new server and installed SharePoint 2010, SQL 2008R2, Visual Studio 2010 in the same server.
Created the application in the SharePoint Central Administration.
Developers directly login to server built the project using Visual Studio. (In server, only 2 ppl can login and work)
Issue:
1. We started getting 2 more projects, and the count of developers became more.
We need to know how to set up an environment where all the developers can work.
Also need to know if there is any way that they can work from local and then we can push the application to the server.
We do not have budget to get one more server and install TFS, so need to know if there is any other repository where we can make the above task possible.
Any help from all you people will me greatful.
Expecting a reply at the earliest.
Regards,
Alex
Depending on what specification laptops/PC's you have you may be able to create a virtual machine to do the development within. All the licenses here would be covered by MSDN subscription(if your devs have this) I think. VM's can get very big so what all the developers did in my last company was to have an external HD with our VM's on there, i think we were using e-sata connected external hd's
If you have TFS you should be able to connect the VM's up to this which essentially would allow you to use the build functionality to create your WSP packages ready for production(once testing has passed on your VM obviously), this package can then be dropped by TFS automatically to your production server ready for installation.
The great thing about this model is that you can have multiple VM's so if you break one you can just use a fresh one! All developers will be on a different VM but with some configuration would be working from the same source code.
Essentially this method has it's drawbacks and it's positives but i found this way was really benificial to me as i was learning how to do things and regularly needed a new VM :P
Something to note about what you have said, It is not recommended that you have VS on your production server.
Hope this helps
Truez
Management wants us to start using Visual Studio through Xenapp when we are working remotely. I can't find any good documents about how teams are using this. The biggest issue seems to be managing workspaces. Most development can be done without a connection using TDD but getting the latest versions is a problem. The Xenapp version of VS doesn't recognize the workspace on the local machine. You can create a workspace to the virtual desktop but then you would need to develop in the virtual machine. If you do map the the virtual environment to the local it gets all files again. This is a problem as that alone can take up to an hour.
We have 4 Xenapp servers that are load balanced so you never know which one you will end up on. If anyone is doing this I would appreciate any help.
I've spent waaaay too much time trying to figure this out. I'm running Windows 7 and Visual Studio 2010 in a VMware Fusion virtual.
When I debug my website project, Cassini (aka ASP.NET Web Development Server) starts and the site shows in my default browser (IE). I stop the debugger, make some tweaks to my C# code, and start the debugger again. The website starts up in IE and the site displays, but its using the code base from when I initially debugged NOT including any tweaks in code between the initial debug/build and subsequent debugs/builds.
The only way I can get code changes to build and run in the browser properly is if I manually stop the ASP.Net Web Development Server from the tray and then run debug.
Has anyone encountered this? Not sure if its caused by VS2010 or the environment being a virtual on a Mac.
Manually stopping Cassini after every debug is really starting to suck.
Thanks.
Check if Visual Studio is set to recompile the projects when there are changes.
Check that Tools > Options > Projects and solutions > Build and run > On run, when projects are out of date is set to Always build.
Perhaps you will have a more pleasant experience with IIS 7.5 Express as a replacement for Cassini.
From that page:
IIS Express is a lightweight,
self-contained version of IIS
optimized for developers. IIS Express
makes it easy to use the most current
version of IIS to develop and test
websites. It has all the core
capabilities of IIS 7 as well as
additional features designed to ease
-- website development including:
-- It doesn't run as a service or
require administrator user rights to
perform most tasks.
-- IIS Express works well with ASP.NET and PHP applications.
-- Multiple users of IIS Express can work independently on the same
computer.
Here's an article to help you get started.
Figured this out. I had mapped my Visual Studio 2010 folders to a VMware Fusion share in order to make my .NET projects accessible from Mac world (for copying graphics files into the projects, etc.). Evidently there was some type of permission issue or something that did not result in any sort of alert that was causing the problem.
I remapped all VS folders (Project, Website, etc.) into the standard Documents folder of my user instance and everything began working as expected.
Thanks for the help.
We are a group of four students who have to develop SharePoint web parts for a certain project. After two weeks of trying out various options, the only possible way we could do it was to set up a Windows Server 2008 R2 64-bit virtual machine (using VMware Player) on a Windows 7 Professional 64-bit desktop with an i3 540 (because it supports VT, unlike the laptops we four have), make four user accounts on the VM OS, and remote desktop into it from our laptops to develop. The VM has Visual Studio 2010 Ultimate, SharePoint Foundation 2010 and SharePoint SDKs installed.
My question is; if we create four different projects in Visual Studio, can we concurrently use that single installation of Visual Studio from remote desktop to work on our individual projects?
If yes, what kind of problems should we expect and how can we ensure we don't run into them?
Alternatively, is there another more trouble-free way of working this out (like changing some setting in Visual Studio to allow multiple instances, etc.)?
Thanks!
While this should work without issues, I would take care with an issue like this.
I would first verify that this is allowed under your current licensing for Visual Studio. I suspect that this is likely a violation of the license agreement, and as such, I would take care with trying to find a better solution. It may be allowed under your license (as there are many different forms of licensing), but I would check this very carefully prior to operating in this manner.
That being said, I suspect this will work fine. Visual Studio does take care to work and store settings per user account, so there is likely no issue. Microsoft Support would be the proper channel for support if you do run into any problems while operating, however.
If your laptops are 64-bit, I would install Visual Studio 2010 and SharePoint 2010 on each of your laptops. If your laptops are 32-bit, I would create 4 separate virtual servers.
Beyond the licensing that Reed points out, I would be concerned about resource sharing. During a SharePoint 2007 project, we had 3 developers sharing a single SharePoint virtual server with Visual Studio 2008 installed on each of our laptops. Everything went fine for awhile until development got really heavy. As soon as one developer would finish running a deployment job, another would start one. The application pool was down so often that the web sites were unusable. Everything was fine once we each got our own virtual server.
If you really must use one server (not recommended), then i would suggest you create 4 seperate web applications. This means they will each get a seperate application pool. Then each users should still be able to debug their webparts without effecting the other users. The debugger should only "break" the application pool that the user is on.
I have a VM on my Win 7 machine running Server 2008. My website can't run properly unless it's running on the server due to COM+, other website integration and environment variables. Currently, I have VS2008 installed on the Windows Server 2008 and I develop there (which is dumb, I know) instead on in my Win 7 workstation. I hate this setup.
My question is, how can I developer on my workstation and then EASILY push and test th websites on the VM Server?
Access files across the network so the actual changes are made on the VM Server?
Make changes locally and publish to VM Server?
Can I set up VS2008 so that if I when I Run the application in VS2008 it pushes everything over and opens a web browser that points to the VMServer's IIS Website?
Of course, the VM is a server on your network. Exactly like any other server on your network, virtual or otherwise.
For debugging you can setup VS2008 to remote debug but I think you'd have to publish the site, start it and then hook up the debugging but I'm happy to learn that there's an easier way... anyone?