I created s set up project using this link.
The addin was not getting installed. When I tried to add it through add ins in excel it said "xxx is not a valid office addin".
This error is because the dll is not strong named and not in GAC. So I enabled adding the dll in GAC in the set up project using this link
I am still not able to see the add in when I run the set up. and when I forcibly tried to add it, got the same error.
Any idea whats going wrong?
Thanks in advance!
Update: Added the registry entry in the deployment project
FInally used clickonce to create the build!!
Related
I created an addin with VSTO and a setup project with visual studio installer.
Im totally new on creating setups... and im getting something weird here (most likely a rookie problem).
I have what follows...
When i install, files get deployed into the folder, like below... and i suppose its the way it should be.
But when i try the addin, i get the following error, like if the manifest is pointing to a different path:
Then for the sake of testing i copied the manifest into the folder he seeks, like so:
And them, the add-in loads correctly...
Though I need some guidance with 2 scenarios:
where or how can i fix this pointing to that folder?
Is there a way to perform a delete on a specific registry key when program is uninstalled?
Please i have this important job to finish at my work and im burning nails...
Many thanks in advance for your time taken to read and help.
Before installing the add-in make sure it is unregistered (if you debugged the project previously there). Also make sure that your installer added Registry entries for VSTO Add-ins on the target machine that correspond to the actual location.
In general, make sure that you did all the steps describe in the following articles (depends on what installer you chose for deploying the add-in):
Deploy an Office solution by using Windows Installer
Deploying a VSTO Solution Using Windows Installer
Started a new project and copied all the code from the previous one... started working.
I cannot understand what witchery Visual Studio does some times.
I am trying to create an installer for an outlook add-in built in VS 2019 Community. I am using the setup extension. It works on my local computer but only because it is the device the VSTO was created on. My problem is create it work universally. When I check the add-in location that works locally, it is pointing to the VSTO in my visual studio project.
I have added the primary project output to the Application Folder in the File System setting, and I have changed the Register property to vsdrpCOM.
It works locally like I mentioned, but I need it to work universally. It does produce a setup.exe and setup.msi as well. I know it is something little I am missing but I thought I would turn to the community for some help.
First of all, make sure that you included all the required prerequisites to the add-in installer. This is the first point to check among others.
Make sure that you did steps described in the Deploy an Office solution by using Windows Installer article.
I know this is an old post but I forgot to update the answer.
My issue pertained to creating the registry keys. I thought the keys would populate in the setup project, I was not aware I had to create every key myself. This was my first time doing a project like this.
So the short answer is make sure you create all the keys as posted in the link above by Eugene.
I'm building an orchard CMS site. Initially, I downloaded the zipped version, but VS complained of the error: "Object reference not set to an instance of an object" in project Markdown.csproj, line 1. This made no sense to me, so I tried installing it from Web Platform installer. That worked great for a while. Then I restarted visual studio after some theme changes and got the original error again. I've attempted to revert the theme changes and tried relaunching VS in admin mode. Still no dice.
I can find absolutely nothing on the subject of Markdown.csproj via google. If anyone has suggestions I'm all ears. Thanks.
In case anyone else runs into this, the solution for me was to migrate to orchard 1.4 via the source instead of web platform installer.
Create a new project.
Move your orchard files to the new project replacing all existing files and folders, except; .cproj file(s), Properties folder.
Clean
Build
Clean you solution and recompile. I have had this happen to me, not with that module specifically, and cleaning up the binaries has solved it for me.
I am using VS2010 to create an Office addin (for Outlook) and im getting the folowing error:
The "GenerateOfficeAddInManifest" task was not given a value for the required parameter "TargetFramework"
I don't even added code to my addin. Just created the template and build!
Any help on this?
I dont have access to this project anymore but what I did back then was editing the project file and adding a "TargetFramework" to the "GenerateOfficeAddInManifest" manually.
I had the same problem too. My solution was to install Visual Studio Sp1, and it worked like a charm.
If you guys are facing this problem, try to do the same before posting anything.
I'm using Visual Studio 2005. I have a program written in C#. When I create the installer and then add the primary output, it's not picking up any dependencies. Not even .Net. Anybody have any ideas?
I fixed my own problem, but figured I would post the "fix" in case any else should run into the problem.
I went back under my main project>references and removed the references to other projects. Then I right clicked on each of the other projects and removed them. I added them all back and rebuilt the project. Then I right clicked on the "Detected dependencies" folder in the installer and hit refresh dependencies and it detected them all
If you want to install the .NET Framework with your setup, you should add it under "Pre-requisites" on the property pages of your setup and deployment project.
Then the created bootstrapper (i.e. the setup.exe file) will check whether the specified version of the .NET Framework is present on the target system and install it as needed.
Please note that this check is only done by the setup.exe file and not when the user double-clicks the msi file. The reason for that is that Windows installer does not allow one msi file (your installer) to start another msi installation (e.g. the .NET Framework installation).
Try to do a build of your installer, it may add the dependencies at that time.
Your dependency dll must be in binary search path of windows.
That is PATH=/path/to/dll must be in environment.
Just in case it helps somebody... None of the other answers worked for me... It seems the cause of the issue for me was that I was adding the 'Primary output' and 'Content Files' in one step (at the same time)... once I deleted them both and added them individually it worked.
i.e. once I removed them both ('Primary output' and 'Content Files') and added 'Primary output' the Detected Dependencies folder was populated correctly, I then continued to add the 'Content Files'.