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.
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 am currently trying to integrate typescript into vs 2010 by following these instructions for windows 7 described here.
Please do not mark this as duplicate because I am having a problem with the provided solution to my question and cannot comment on the solution.
I followed your instructions closely but sadly it's not working for me. During installation of typescript I get an warning from VisualStudio concerning devenv.exe: Invalid Command Line. Unknown Switch : updateConfiguration.
After clicking okay the installer reports that the installation was successful. when I start VS without creating or opening a project, after a while I am greeted with another error:
Confirming, that I do not want to get bugged about this again i create a new typescript(!) project, which gets denied with a more severe notification:
I checked all the folder paths I added as parameters to the .msi file and it looks like everything is in place. Any ideas how to resolve this?
Thanks!
I suppose there is a missing folder redirection in the answer you referenced, the VSTools msbuild folder is not being redirected.
If you open up the %programfiles%\msbuild\Microsoft\VisualStudio\v11.0\Typescript folder, is the target file present there? Try copying the whole folder to %programfiles%\msbuild\Microsoft\VisualStudio\v10.0\Typescript.
On a more serious note, Typescript is usually used for Web Development, Web development project types are almost 100% backwards compatible between VS2012, VS2013 and VS2010, so why not upgrade to make use of these features.
It can hardly be a support issue, since backhacking Typescript into VS2010 is surely putting you in the unsupported bucket.
I recently installed Dotfuscator 4.10 on my computer and I already has VS 2012 working on it. Everything worked fine up to the point when I tried Dotfuscator embedded in VS (I mean the standalone GUI app works perfectly).
Just for the try, I created a small solution (no TFS/VSS) with a C++ /clr app, a C++/clr dll and a C# app.
I then added a Dotfuscator project. To this project I added the output from the three dll/exe other projects.
When I tried to rebuild the solution, I was asked to save the .dotfuproj file. Strange and abnormal behaviour, the file should be saved automatically and without prompting me. OK, I chose to overwrite the existing file (what should have been done automatically after all.) I got the error Object reference not set to an instance of an object. I had to cancel the operation and could not build the solution.
Note that I observed the same behaviour if I tried to save the dotfuproj file under an other name. Also, the file is not R/O.
My question: has someone experienced this problem? Any solution? Thanks for your help!
You can try deleting your Dotfuscator project and then creating a new project. If that does not work, try using direct input to the Dotfuscator project, rather than using the output of another project within your solution.
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!!