What is the easiest way to deploy to multiple servers with as few clicks as possible from within Visual Studio? We are using web deploy, not FTP or file system if that is helpful.
Not sure that's possible from within Visual Studio.
Take a look at this article. It describes doing it via the commandline, which might be useful.
http://msdn.microsoft.com/en-us/library/ff731049.aspx
Related
I am currently in the process of developing a program in Visual Basic. For now, I want to give the program to a few friends to test, make changes and then release it. But I don't exactly know how. I used the Publish feature in Visual Basic, but I don't exactly know what I'm supposed to do with it. It mentions things like installing from a disk and whatnot. I just plan to upload it to a file sharing website and release it that way.
EDIT: Using Visual Studio 2012
Use dropbox or any file sharing site :D
Is there any tool or plugin that can synchronise visual studio so that when I use it at home the same windows are open in the same configuration as when I left work?
Have you tried Pepper?
Will sync (most of) your settings to the/ a cloud somewhere.
Visual Studio Live Share may be able to be used to get this behaviour.
I am new to Visual Studio 2008 Shell (integrated mode), I just want to know what is its function? (I did not find much clearly from the web.)
From http://msdn.microsoft.com/en-us/vstudio/bb510103.aspx
looks like it is some interface/framework to allow tools to integrate with VSTS IDE. My question is whether any Microsoft VSTS tools (like databse designer and other tools in VSTS) dependent on VSTS Shell? I am asking this question because it is conflicting with SQL Server 2008, and I want to make sure that if I uninstaill VSTS Shell, it does not impact anything.
thanks in advance,
George
SQL Server 2008 Management Studio using the VS 2008 Shell. (That's why it looks and feels just like Visual Studio).
Visual Studio Shell is an extensibility mechanism provided to use Visual Studio core platform to provide your own tools. It has two modes. In "Isolated Mode," it'll always set up a separate instance of Visual Studio that hosts your tool. In "Integrated Mode," it'll only install a new VS instance if there's no one already available. If one is already there, it'll integrate with it. I don't think removing it causes any problems for a VS installation. It seems to be smart enough to handle it (it might break a third party tool, however).
The shell version means that applications can merge into the shell and be used independently. Isolated mode means that this version only performs one task and is a complete separate application..
See: VS2k8 Shell
A clearly defined difference is here
Is is possible to deploy VS add-ins using ClickOnce? How can I do it?
Take a look at Securing and Deploying Add-Ins. And the subtopic Securing Add-ins by Using ClickOnce.
I haven't personally used them, but I found them while searching with a similar question as yours.
#Rob: The links you have provided is Add-in's for Applications (aka MS Office), not for Add-in's for Visual Studio (as I understand the question). The Add-in object model in Visual Studio does not support ClickOnce - unfortunately.
To deploy Add-in's for Visual Studio, visit http://msdn.microsoft.com/en-us/library/dd393694.aspx.
I'm pretty sure that you cannot do this. ClickOnce is designed for side-effect free deployments, and don't impact registry (except perhaps for file associations) or "Program Files" (having their own repository).
I'm pretty sure you'll need msi for this.
I'm trying to develop some SharePoint workflows for the company I work for, and I'm not too familiar with the ins and outs of the technology. Normally when I want to familiarize myself with something, I just play with it, look at the properties, find all the methods, etc.
When I fire up Visual Studio and try to create a SharePoint workflow, it gives me an error indicating I don't have a reference to "Microsoft.SharePoint.dll". Someone told me that it was normal to see that because you have to do all your development on the SharePoint Server itself if you want to do workflows. Is this true?
If so, is there anyone out there that has successfully developed SharePoint workflows in a multi-developer environment without resorting to any "hacks"?? Thank you for reading and your responses...
If you want to create a Sharepoint workflow using the Sharepoint Templates, you need to have a Windows 2003 or 2008 Server running Sharepoint. Essentially, that is true for all Sharepoint development: For it to be really efficient, you need to run Visual Studio on a Sharepoint Server. This in turn means that every developer needs his own Sharepoint server and then you have one additional "Staging"-Server where you deploy and test your combined solutions. Suddenly, that MSDN Subscription looks very attractive :-)
As for your Workflow learning question: I can highly recommend "Workflow in the 2007 Microsoft Office System" by Apress.
Yes, you have to do all your development on a the SharePoint server itself. Consider using a virtual machine and package up features that you can deploy to your staging and production environments.
http://weblogs.asp.net/erobillard/archive/2007/02/23/build-a-sharepoint-development-machine.aspx
http://www.wssdemo.com/Pages/EntDev.aspx
Yes, you can develop SharePoint Workflows, WebParts, etc. in a multi-developer environment without any hacks. I suggest you use
a MOSS 2007 VPC Image
Ankhsvn to use svn inside Visual Studio
and also the WSPBuilder Extensions
and maybe you should read What are your biggest complaints about Sharepoint? to see what you're up to ;-)
To learn SharePoint Workflow development,you can start at Step by Step Tutorial. Creating Workflows for Windows Sharepoint Services and MOSS2007
While it's true you need SharePoint installed on your development computer for most SharePoint development, you can get away without it for workflow development. Follow these steps:
Copy the SharePoint DLLs to your development computer (for workflow you'll need microsoft.sharepoint.WorkflowActions.dll).
Open Visual Studio and open the Toolbox tab
Add a new tab (call it SharePoint Workflow Items)
In the new tab, click "Add Items"
Click the "Activities" tab
Locate and add microsoft.sharepoint.WorkflowActions.dll
You'll see a few new tasks show up and already selected.
Once you do this, you'll be able to develop WF workflows that can use SharePoint-specific tasks. Deployment and testing the workflow is another task altogether.
Also, it was casually mentioned in this thread, but you cannot develop SharePoint workflows on a 64-bit SharePoint Server at this time. You will have to have a 32-bit Windows Server and SharePoint Server installation.
Here is a link to some SharePoint workflow how to videos.
http://chrisbarba.wordpress.com/2009/12/21/sharepoint-workflow-how-to-videos/