I'm currently using ClickOnce to install myapp.exe. But now I've added Outlook 2007 addin support, myaddin.dll.
So, how can I install both exe and addin with ClickOnce.
I don't think you can package them together per se. That's not supported (yet). But what you CAN do is deploy them to the webserver separately, and then have the desktop application invoke the install link for the Outlook Add-In when it runs. Just do a Process.Start("iexplore.exe", "http://myapp.com/myaddin.vsto")
It might get complicated depending on which version of Office you're deploying for.
I think it can be done by adding the .exe project as a dependency of the addin project. I read a little that said that's the way it's done, but haven't tried it personally.
Related
Working with VS2017 Community I have written a service that works on my local machine. I followed the instruction here:
https://learn.microsoft.com/en-us/dotnet/framework/windows-services/walkthrough-creating-a-windows-service-application-in-the-component-designer
and installed it successfully using Installutil.exe (as per instructions in above link). All good.
I now want to deploy that across six servers in our organisation. In Microsoft's documentation about installing services (https://learn.microsoft.com/en-us/dotnet/framework/windows-services/how-to-install-and-uninstall-services) it says:
If you’re a developer who wants to release a Windows Service that users can install and uninstall you should use InstallShield
and links to a page that applies to VS2012 (can't post any more links as my reputation<10)
I have downloaded and installed the "Microsoft Visual Studio 2017 Installer Projects" package, which allows me to create a Setup Project. When I run it, it installs the project output correctly (i.e. copies the exe & dll files to the correct folder in Program Files) but does not create the service.
There's a detailed post about deploying services on this site (question 9021075) but when I follow those instructions I get a 1001 error on Install.
All the documentation I can find refers to earlier versions of VS or the previous Installer package, so I'm not even certain if I can do it with the software I am using.
So, with VS2017 Community using Microsoft Visual Studio 2017 Installer Projects, how to I create a stand-alone Installer to deploy a service that works correctly when installed locally using InstallUtil?
Or can I use InstallUtil on the target machines? I think I'd need to install Visual Studio on them for that, which I'd prefer not to. Is there a quicker way?
I only have 6 servers to install this on, so even some manual work-around might do.
Thank you for the responses. I now have a solution. I found InstallUtil on the Target Server (in my case it was in C:\Windows\Microsoft.NET\Framework64\v4.0.30319 but search will find it). I copied and added that to my project as content so when I now deploy it, I have InstallUtil in the same folder as my EXE.
To install, I run CMD as admin, cd to project folder and issue command:
installutil.exe myService.exe
This is a one-off task. Once the service is working, to update it I just need to stop it, upload the new myService.exe (& any DLLs) to overwrite the old ones and restart it again.
Further information about settings you're using for the serviceProcessInstaller1 and serviceInstaller1 files will be needed to debug this issue, as the 1001 error raised by the installer is a generic error.
An alternative way of doing this is to use Topshelf, which is a framework for hosting services written using the .NET framework. It simplifies the creation of services, allowing developers to create a simple console application that can be installed as a service using Topshelf. The reason for this is simple: It is far easier to debug a console application than a service. And once the application is tested and ready for production, Topshelf makes it easy to install the application as a service.
Alternatively, you could use InstallUtil.exe. It is part of the .NET Framework, so no need to install Visual Studio.
I have been struggling to figure this out.
We have made a Outlook Add-In in Visual Studio 2013.
I can install this using the .vsto that they provide without a problem on a windows machine.
Now I try the same thing, placing the .vsto on the citrix server, installing this works fine, although it does a call to the internet which isn't allowed, so I had to work around that (anybody know why it calls to the internet? and what?).
Than I got it installed at the server, go to the thin clients, its right there, the only thing I have to do is activate it.
The second I activate it, it runs an executable, which obviously is not allowed, and I cannot activate it on the client.
You need to create an MSI installer for the add-in. See Deploying an Office Solution by Using Windows Installer for more information.
The solution is very simple but impossible.
I have office 2010 and office 2012 installed, VB6 fails to create a Word application object giving me no more than just a message saying that the DLL is not registered.
All attempts to remove and restore the DLL using the installer or third party DLL fails.
After removing everything office related and only installing office 2010, the application object gets created successfully. But this is not a viable solutions for our customers: we can't have them removing their Office suites for this.
Is there any other way?
I had a similar issue on my dev machine with two versions of office. Cast your eye over this article from Microsoft support they mention the /regserver command line option. The article is Office automation when multiple versions of Office are installed. By the looks of it I don't think you can force it to pick one version or the other but the /regserver will help you in your dev environment.
We have a windows application. To deploy it we used windows installer. Now as our application require lots of automatic update we are thinking to move to winform clickonce deployment.
The only problem is we have some DLL in our project which require registration (vsdrfCOMRelativePath). How can I achieve the same in clickonce deployment
ClickOnce installs are for one user account, so will that be an issue? Services won't install either. ClickOnce isn't just another way of doing what an MSI install does, it is very different. You may be better off adding code to your app to call a web service and downloading the update rather than converting to ClickOnce. As far as I know, you can't run COM registration from ClickOnce. Make sure you understand all the ways in which MSI differs from ClickOnce!
I have a project that was given to me where, organically, they created it using Add-In Express and Visual studio. The issue they ran into is that some of the prerequisites needed to be installed before the actual add-in could be installed. So there is a 2 step process. I have some experience with InstallShield and believe my version is 2009. I am wondering if that will handle the install better than add-in express or if I should create a manual package in VS2010. Also, is there a way to silently install the prerequisites?
As a regular .net based application your Add-in Express based solution relies on the .net framework. So, .net framework should be installed on the end user PCs. Your solution may also include a lot of references or dependencies (if any) that should be installed before running the add-in installer.
You may be interested in the Video: Fully featured setup projects for Office solutions article on our technical blog.