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.
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.
We wish to add a dialog to our WiX installer that prompts the user for a SQL server connection: server address, authentication type, and SQL login/password. A Test Connection button would be nice as well.
My searches turned up the msiext project, but I cannot reference its dlls (e.g., WixCommonUiExtension.dll) in my WiX project because they were built for WiX 3.0. Did a bit of googling and I'm not the only user who's experienced this issue. Folks have even tried building the msiext project against WiX 3.5 themselves, but based on the posts in that link I'd prefer not to go down that road.
Can anyone provide or point me to a dialog I can use? I would prefer not to reinvent the wheel here. Thanks!
I know it's a bit late but you could try http://msiext.codeplex.com/ project. The site claims that they have such dialog
I am finding all sorts of general descriptions of no-touch deployment and lots of questions and problems, but I can't figure how to just get started with it. What is the method that makes it happen? I'm working in VB.Net 2005. I think assembly.loadform will suit me best since I know all of my users and will deploy via my intranet.
Appreciate any links or suggestions for starting places (other than googling "no-touch deployment", I already did that).
If it's a web application project that you're deploying, one-click publish with Web Deploy may be what you're looking for. Here's a related link:
How to: Deploy a Web Application Project Using One-Click Publish and Web Deploy
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
There was a challenging situation happened when i was working with install to provide product key validation. I had to use C++ unmanaged code to validate the key. Actually we had the main validation logic written in C# and I had to create a mixed project. Problem was not stopped only with these, it continued. Since I used VC++ code, it expected atleast the VC++ runtime redistributable to be installed in the client machine. I thought of dropping the plan to migrate our install to Wix because of these kind of problems.
But I came to know that there is a nice and very cool feature that DTF is available in Wix to integrate any kind of actions in C#. I used it and could integrate the key validation in couple of hours and till now it is working fine in all client machine I implemented before 6 month.
Do you have any interesting moment or nice experience with DTF?
Search my blog at http://blog.deploymentengineering.com for DTF and you'll find a lot of useful content. I love DTF but I still believe that the best solution is to avoid a CA whenever possible in the first place. C#, like VBScript before it, is so luring that it tends to suck imperative thinking developers into writing CAs when not needed. I believe this is the reason DTF wasn't released for so long.
At my day job my approval is required for anyone who believes they need a CA. I instruct the developers on basic MSI philosphy, how to use DTF, how to attach a debugger and I make it clear that they are on the hook if it ever has any issues. The result is very few but well written CAs in our product line.
I have written several .NET CAs to support our WiX based installs:
Managed Wrapper around HTTPAPI.DLL - supports creating IP/Port SSL bindings and HTTP Url ACLs for use in deploying WCF services. I plan to turn this one into a Wix Extension. It was very interesting learning how to properly handle rollbacks, etc.
SSL Picker dialog that displays all the SSL certificates on the system and allows you to pick one.
SQL Server browser dialog - lets you browse your network for SQL Servers and then browse SQL Servers for Databases. Optionally uses impersonation. This is for crafting a connection string.
I am in the process of writing a set of CAs that will use the Microsoft.Web.Administration assembly to do native installs of web applications on IIS 7 (without requiring the IIS 6 Metabase Compatibilty feature be installed).
First off, the C#/DTF custom actions are still custom actions (no magic here :-)), so you should follow all the various CA guidelines working with this kind as well. It simplifies most of MSI tasks by abstracting low-level API behind the high level well-designed classes. Also, keep in mind that you can use managed code CA only in case the target machine has .NET installed (or install it as a prerequisite). Finally, the dtf.chm documentation which is distributed along with WiX toolset has some simple, but self-explanatory examples.
Hope this helps.