It could be that what I'm trying to achieve isn't possible (as I can't find out how to do it!) but basically I've upgraded my VS Version from 2010 to 2013.
All of my companies test sites are running on IIS 6 on Windows 2003 Server.
And what I'm trying to do is remote debug my solutions on this machine (Which I was able to do in VS2010).
So my question is...is this possible or will I need to convince someone to upgrade the server?
Thanks,
Craig
I need to be able to setup my IIS server to accept Web Application publishing via the web deployment tool in Visual Studio 2010. I have attempted to install web deploy, but still haven't had any success. I am not positive if this is the right tool or not.
I am running Server 2008 R2 Enterprise
version 6.1.7601 Service Pack 1 Build 7601
X64
IIS Version 7.5.7600.16385
SQL Databases will be accessed and are housed on this server as well.
SSRS is also running on this server.
Thank you,
Stephen Hathaway
I have my desktop with VS 2010 professional installed, a virtual machine with TFS 2010 installed and a second virtual machine on which I want the builds to work onto.
Thats what I'm trying to say.
The two virtual machines are on the same domain, the VS 2010 is on a different domain.
Is it just configuring the build agent?
Hope this makes sence.
Thanks
To make your Visual Studio project build on a dedicated server you have to setup a Team Build definition, see this page on the MSDN for more information.
When remote debugging on a remote web server you need to have the remote debugging tools from Visual Studio installed on the web server.
Is it possible to run multiple versions of the msvsmon.exe at the same time?
How do people handle the case where some of the developers are running Visual Studio 2008 and others are useing 2010?
I am going to be learning how to do SharePoint 2010 development and as such I am setting up my environment? I have a couple of questions about that.
First, I am following a couple of helpful articles on how to do it as follows...
http://geekswithblogs.net/manesh/archive/2010/05/28/building-the-ultimate-sharepoint-2010-development-environment.aspx
and
http://msdn.microsoft.com/en-us/library/ee554869%28office.14%29.aspx
Both of these article recommend setting up Sharepoint on a server environment or VM and THEN setup Visual Studio on that same environment.
I was wondering if it will work to setup Sharepoint on a VM Guest and use my existing installation of Visual Studio (my VM host) to do the work. To do Sharepoint development do you HAVE to install Visual Studio on the VM Guest with Sharepoint? What do I lose if I just use my production install of Visual Studio (or will it just plain not work?).
It just seems counter-productive to have two development environments (and I refuse to install Sharepoint on my production machine...at least right now.)
Also, will SharePoint Foundation edition (rather than full server version) function just fine for learning and development or will I find that I am eventually going to hit barriers and limitations with it.
Thanks in advance for your help.
Seth
In order for many of the SharePoint features Visual Studio 2010 to work, both must be installed on the same machine (or VM). Visual Studio can't deploy to another machine, and the debugger (F5 Debugging) won't work remotely. If you choose to not install VS on the VM, then you will have to package and deploy the solutions yourself, as well as debug them yourself, either through the remote debugger, or trace logs on the machine. Its worth installing VS on your VM.
The SharePoint Foundation will work fine for learning, unless you are trying to learn about some of the features specific to SharePoint Server. Here is a good chart showing the differences.
You need to have SharePoint installed on your development machine so that you can write code utilizing the SharePoint assemblies.
As for just using SharePoint Foundation, I would recommend that you identify what sort of functionality you want to work with and let that determine if you can get away with just using SharePoint Foundation or not. Personally, I would use the full version so that you can learn about the the functionality it offers as well. Otherwise, you won't really be learning everything that SharePoint can provide for you.