I have a complex workflow, written in VS2010 (not sharepoint designer) for Sharepoint 2010.
Is there a document somewhere (MS?), with the recommended steps, to deploy an updated workflow, without cancelling the existing running instances of the workflow?
I can easily deploy the new workflow, however, the problem is that, I do not want to kill the existing instances of the running workflow (which is what happens by default when you deploy the workflow).
Through trial and error, I have a long list of what I think I need to do, but I really would like some confirmation.
I also need to use the new Package capability to deploy the workflow, since VS.NET will NOT be installed upon the sharepoint production server.
Thanks!
Dave
I had struggled myself with this in the past (2007 times) but couldn't find an elegant way out except completing the workflows.
Could this give you pointers - SharePoint Workflow Versioning with VS 2010
Related
i have made a sequential workflow in visual studio 2010.
the workflow is working fine on me local machine. i have packaged it to a solution and uploaded it to our intranet. using site settings solution and then add solution and activate it. when i go to site features i don't see me solution and it's not working on the list i have made it for. anyone knows how to fix this ? i'm using sharepoint2010 foundation.
the language i have made it in is english and the site where im trying to install it is Dutch.
thanks in advance.
Check that the workflow is published.
This link may also be of help. There is a slight chance your problem might have to do with localization issues.
Hi guys I need to know if there is a tool that I can use to have my outlook addin(assume that it has been successfully installed to many users) get auto updates from a web server? I'm thinking of ClickOnce but I'm not sure of using it since there are drawbacks on its implementation.
Do you have any suggestions? or should I deploy it with ClickOnce?
any of you have an opinion/experience with ClickOnce deployment?
This is an article that describe how to add an automatic update service for an application, give it a look: Adding automatic updates to your program
Updated:
Another interesting approach is the ".NET Application Updater Component" which is the answer of a similar question "Auto-update library for .NET?" where you can find other interesting answers too.
I understand that you can't develop in Visual Studio 2010 for a remote Sharepoint 2010 server because you need a local copy running on your box. (I know there is a hack)
In my situation I have Sharepoint Foundation installed locally for development purposes but I'm not sure how to get the custom lists, etc from the remote server to my local box so I can develop against the same objects.
I've tried exporting the site on the remote box and then creating a new Visual Studio 2010 project from it. This resulted in exceptions when deploying to my local box - more problems which I'm sure given time I could work out...but more problems. (It was types not being installed properly on my local box that the custom object was using)
So I've been thinking there must be an easier way to pull down data structures.
I've spent a while looking for this and while there is quite a lot of information out there I'm finding it hard to find basic information like this.
Any help is greatly appreciated.
What objects do you need from the remote server?
If it is lists, you can export the lists from the remote server as templates then use the resulting stp files to create the lists locally. If it is dlls you can get them form GAC and add the required entries in SharePoint site web.config.
You can also try to export the entire site and create a site locally based on the site template.
every time i do build to setup project on vs2010 its starts sql manager 2008 process for a while and build. the process takes couple of minutes.
in 2008 it did not do that
any thoughts why ?
G
I don't have an "answer." But I have some information. This (or a very similar) question was asked in how do I stop sql server 2008.... In my case, I had installed VS 2010 (Ultimate) from a Passport drive; SQL 2008 was installed from an ISO image. If I simply plug in the passport drive (VS2010 source) when building the Setup project, the issue "goes away" in the sense that it does not show the dialog. My hunch is that it is still doing the same work, but is finding what it wants (quickly) on the passport drive. If I disconnect the external drive, the problem returns. So if the message is correct and VS 2010 is trying to configure something, it never really gets configured; but it gets past it quickly if it can find its install source.
Someone who has spent more time working with all the configuration pieces might be able to do more with this information.
I'm looking for suggestions on keeping a program that is running on a network updated. Installation consists of 15 users, each have the program on their local pc, but they all access same date from sql server.
I am looking for a clean method that would allow me to update one folder on the network and for each computer to get updated when they run the program and the programs sees a later ver on that folder on the network. (Obviously I can do this inside the program itself since it won't allow being overwritten while opened.)
You should have a look at
ClickOnce is a deployment technology
that enables self-updating
Windows-based applications that can be
installed and run with minimal user
interaction.
Using ClickOnce Deployment in
VB.NET
ClickOnce - A new VB.NET 2005 Deployment Tool
ClickOnce Deployment for Windows Forms Applications
ClickOnce Deployment in .NET Framework 2.0
Another option is to create a second program that will check the network for an updated version of your application. Let's call this program "updater.exe".
You can run updater.exe on system startup like Adobe Reader or Sun Java do.
Or, when your application is started it can load updater.exe. If updater.exe finds an update, it can close/unload your application, download the newer version, restart your application and close itself.
astander's answer above is correct, you can use ClickOnce for this. Another option is creating this application as a web application.
Web applications basically work the way you described, the application's files reside in a web server, all the users connect to it using a browser, and to update the application you only need to update the files in the server.