I am developing a VSTO 2010 Office 2007 Outlook Add-In deployed from Click-Once. On the computer I developed it, running Visual Studio, everything works just fine, but when trying to install it on another computer, the addin is installed, and during the startup screen, It comes under Inactive Applications Add-in.
In Load Behavior, It shows Not Loaded.A Runtime error Occured during the loading of the COM-Add-in.I have changed the Load behavior from 2 to 3 in HKCU under Registry Editor.But it is again reverted back to 2.Not sure how to find the specific error so I can fix it.
Does anyone have any ideas on what might be causing this?
Any ideas anyone might have would be greatly appreciated.
Finally I have found a solution by myself.What I have done is Before I published a solution I was checked .Net Framework 3.5 SP1 Client Profile in prerequisites under Install settings and it works for me now.
Related
I have written a VSTO for Outlook with a formregion for meeting/appointmentitems in VS 2015.
I deploy this to our desktop computers using ClickOnce.
I would like to use the Windows Installer to install the VSTO for laptops because when I use ClickOnce and the laptop uses Outlook when not connected to the corporate network, the add-in is disabled.
I assume this is because it cannot reach the internal ClickOnce publish location, eventhough the deployment should not check for updates.
I have followed this article to create an installer for the addin.
I followed the all-users steps and the files are installed to the local computer and the registry keys are being created but the Add-in is not loaded in Outlook and it even is not showing up in the list of Addins in Outlook.
Anyone who has had similar issues and knows how to solve this problem? It's driving me crazy for the past 2 days.
There is no such central repository. Your addin most likely gets disabled on startup because of a run-time error.
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.
I recently, upgraded to Windows 10 and got Visual Studio 2015 Community hoping to build UWP apps and ASP.Net 5 apps. At first, I installed everything, but ended up skipping / canceling the Windows 8.1 / 10 mobile emulators (my PC can't even run them). After everything was installed, I went to create a new UWP app (C#), and got this error:
Next, I try the same thing, but with JavaScript. It works perfectly! on the same UAP 10.0.0.0 that is supposedly missing. The link it provides is completely useless (it sends me to http:/microsoft.com/en-us) -_-. Oddly, this only happens when I try to use C# or VB.Net, JavaScript UWP apps seem to work fine. What is going on here? Where can I find the real link to the SDK I need?
UPDATE
JavaScript UWP apps will be create just fine, but when I attempt to build, I get:
Error "10.0.0.0" is not a supported value forTargetPlatformVersion.
Please change it on the Project Property page. Test
C:\Program Files (x86) \MSBuild\Microsoft\VisualStudio\v14.\JavaScript\Microsoft.VisualStudio.JavaScript.UAP.targets
This is the download link for the standalone SDK, maybe reinstalling the sdk will fix the problem.
https://dev.windows.com/en-us/downloads/windows-10-sdk
Normally you don't always have to reinstall visual studio when something goes wrong because it takes a lot of time to reinstall again. From your question you skipped/cancel that feature, the first thing to do is go to the control panel and double click on visual studio under programs to Modify the software and enable those features.
In the case, visual studio was working properly before but due to some updates it stopped, go to control panel right click the visual studio version you have under programs to repair.
If the above doesn't work try to reinstall it again. I hope this helps.
We developed an Outlook Add-In for Win 7 with SP1 and .NET Framework 4.0 as a prerequisite. It gets install perfectly on some machine without any hiccup but in other machines (same configuration, Win 7 & SP1) the add-in goes into the 'inactive' state and doesnt load while outlook start-up.
While installing there are no issues or error message getting displayed. What could be the problem? How can I check or debug what could be causing this issue? Any solution or hints on this will be highly appreaciated.
Inactive add-ins are usually caused by a missing reference that wasn't deployed. Try some of these resources:
http://blogs.msdn.com/b/haahmadi/archive/2010/05/26/my-vsto-add-in-does-not-load.aspx
http://archive.msdn.microsoft.com/vstotroubleshooter
I'm trying to create a Shared Addin using VS 2008 for Office XP (Excel to be precise). However, after creating the project in Visual studio and changing the references to Office XP (apart from Extensibility which I don't seem to be able to find a copy for office xp) and adding excel.exe to the references as well. I now don't seem to be able to get the addin to install on any computers.
Does anyone have any guides on writing Office XP addins using VS 2008 (Com Addins I might add)?
Does anyone know the reference that I'm meant to have or things prior that I'm meant to have installed on the pc?
I have three test pcs, this one has office xp, 2003 and 2007 on it and I can write an addin using 2003 references that runs on this but no other box. One with just office xp on it but also office xp PIAs installed and .NET and another one just with office xp on.
Any help would be very much appriciated.
I found the problem with this in the end.
The problem came from a KB entry 908002. Unfortunatley, to run the fix you need Visual Studio 2005 and Office 2003 installed otherwise it won't deploy the fix and so I had glossed over this quite a few times. In the end I found an old copy of VS2005 and Office 2003 on a spare machine, installed the fix, created an installer and tried it on a machine with Office XP and everything worked fine.
There are two fixes that are needed for this to work on any machine with Office XP:
extensibilityMSM.msi - installs the extensibility.dll
lockbagRegKey.msi - adds a fix to a registry key
I couldn't find these to be downloaded seperately from the KB908002 fix but I have copies locally.
After applying these fixes it was easy to use COM Addins like using VSTO and it took me less than an hour to write the actual code. I'm not looking for a way to include these in my MSI installer as prerequesites.
Any questions chuck them in a comment and I'll try and update asap.
You need the PIAs installed as a prerequisite. Does the addin install at all, or fail at installation? An add-in misbehaving at startup may be banned by the host application (Excel). You can reneable it in the Add-in settings dialog in Excel.
#PintSizedCat - Here is a link to a msdn blog that shows how to extract the msi's without having VS2005 installed.
See the section "Building the Shared COM add-in setup project" - use the command line:
vs2005-kb908002-enu-x85.exe /T:”C:\Test” /C
For us it was Excel 2003 with .Net 2.0 and the extensibility.dll was missing. I don't think VS2008 / VS2010 have this as a prerequisite. The dll is not redistributable (According to this blog - see the "The Answer" section) - you must use the msi to redistribute it.