Hei
I have created project for outlook Add-in in c#. I have to display the new menu item when i right click on one email or more .I have tried and have followed following link
https://msdn.microsoft.com/en-us/library/office/ee692172%28v=office.14%29.aspx#OfficeOLExtendingUI_NewItemsMenuforMailModule
I dont know if iam getting the right "idMso" iam stuck also since i have outlook 2016 installed on my computer and when i create new project from visual studio it displays me template Outlook 2013 AddIn
Anybody have experience with that ?? shud i need to install the outlook2013 version ?
You are looking at the right resource, just picked the wrong context to hook up with ("idMso"). Please look at the following:
Context Menu for a Mail Item
Context Menu for Multiple Selected Items
shud i need to install the outlook2013 version ?
You will be fine with your installation of Outlook 2016.
Related
I'm taking a VB course that uses the 6th edition of Gaddis (2012). It says that to add a module to the project I must do the following;
However, this option is missing in my install of VS 2017 Enterprise. Is my install messed up, or has this functionality changed since Gaddis 6th came out, or am I missing an installed piece? If my installation is incomplete, which feature should I install?
The selection of Project Item templates changes in every release of Visual Studio to help advertise whatever new features came out in that edition. Use the search box in the top right corner to search for "module".
You need to have the VB project selected in Solution Explorer for the Add New Project Item dialog to suggest VB items. If you're seeing C++ items then you're in a C++ project or you're in the "New File" or "Add New Solution Item" (not Project Item) dialogs:
File > New File
New Solution Item
New Project Item (Visual Basic)
I have some rules for work in outlook 2013 - however following my laptop crashing the other day, I can no longer run any rules, they simply do not work (I don't even get a debug notification). Upon checking my macros, I found that when I tried to click on any scripts I have and I keep getting the message 'This action is not available in the current mode'.
The option to create a new script has disappeared from the rule list too.
So far I have tried:
-Using the outlook 2016 fix by running the registry fix DWORD 1 (There is nothing out there for 2013). I have restarted my Pc and it still has not changed a thing.
-System restore to a previous date. This has literally changed nothing.
I'm a little stuck. I have attached screenshots to further explain exactly what I am experiencing.
Thanks,
Rachael
Some information has been whited out due to confidentiality.
Trust Centre Settings:
I encountered this issue after a Windows Update. Here's what fixed it for me:
Save everything below the line as a .reg file and then double-click it to run and launch (or manually add it your registry via regedit).
You should probably backup your registry first to be safe and please note that this was the correct location for my Office 2013 installation (yours may be different).
Office 2013 = 15.0
Office 2016 = 16.0
Save using Notepad as a .reg file to double-click and upload to your system's registry (Office 2013). I hope this helps someone else! -Mike
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Security]
"EnableUnsafeClientMailRules"=dword:00000001
here is a quick and dirty test to check whether vba code runs at all when email arrives
put it into "ThisOutLookSession" which is under "Microsoft Office Outlook Objects"
then send yourself an email ... if vba runs then you should see a popup
it will not solve your problem, but it will provide more info to help narrow down the cause
Private Sub Application_NewMailEx(ByVal EntryIDCollection As String)
MsgBox "you have mail"
End Sub
Or you can create .reg file Open Notepad and save-as .reg
Outlook 2010
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\14.0\Outlook\Security]
"EnableUnsafeClientMailRules"=dword:00000001
For Outlook 2013 use \Office\15.0\ and Outlook 2016 \Office\16.0\
Currently I am using Visual Basic 2008 (.NET Framework 2.0) to create a program. However, when I add or select controls such as panels, group boxes, etc. I get error messages. For example, when I try to add a panel control I get the following message,
After clicking OK button, the panel control is added but the following happens to the panel control,
Yet I can still add other controls inside it. When I save and re-open the project, it shows the normal panel control. But when I select the panel control it does as shown in the second image again.
I tried this in Visual Basic 2008, 2010, 2012 and 2013. Same thing. I have full administrator access to the computer.
What is the reason for this and how to fix it?
I re-installed Windows and then Visual Studio 2008. The error did not occur after that. But when I updated the computer via Windows Update, the error came back.
Try creating a new project, then copy and paste code from the old project. You may or may not have to recreate the forms in the designer. Also, make sure you have System, System.Core, System.Drawing, and System.Windows.Forms included as references for the project.
The error was due to a Windows Update. Because it does not show any errors on non-updated Windows 7. The error only appears after updating Windows 7
It was difficult to find which update was the reason for the issue. The solution was to install Windows 7 and Visual Studio and never update it. This way, it seems to fix the issue and it does not show the errors anymore.
Reference: https://social.msdn.microsoft.com/Forums/vstudio/en-US/76790023-4d01-43a5-b901-65ad93a5183d/visual-studio-visual-basic-protected-memory-error?forum=visualstudiogeneral&prof=required
I have the following situation. I installed Visual Studio Update 3 last night. Now I have a problem that when I open my projects (Universal Apps) which i have done while i had update 2, my designer won't load and it throws an exception:
Does anyone knows how to solve this? I guess this is not a bug because probably everything was tested by Microsoft, and this is not RC update. Im about to delete this update if i don't figure out the solution. I'm guessing that it might have to do with xaml if anything changed?
I figured out from the connect bulletin that there are two folders in your Windows profile that need to have their contents cleared out in order for the Visual Studio designer to work with Visual Studio 2013 Update 3.
The two folders are:
For Blend: AppData\Local\Microsoft\VisualStudio\12.0\Blend\ShadowCache
For Visual Studio 2013: AppData\Local\Microsoft\VisualStudio\12.0\Designer\ShadowCache
Don't delete these folders, just delete the content of those folders and you will be back to working happily with the XAML designer again.
Clearing the ShadowCache did not resolve this for me. Found a clue from an MSDN article and checked the event viewer for exceptions, look for XDesProc.exe.
The problem was an out of date driver for my graphics card.
Once that was updated all started working again
I have created a solution with a Outlook AddIn Project and a InstallShield LE Setup Project. I followed this Walkthrough to create the Setup Project:
Link
I installed my AddIn on a user-level. Here are some screenshots from my Setup Project:
Here I added the project output by going to "Add Project Output" and then selecting "Primary Output" from the list and clicking OK.
Here I added the registry keys for a user-level installation. I am not sure if what I did here is correct and I suspect that the error lies here. I have tried following the walkthrough but I am not sure if I added the keys for the AddIn and it's FormRegion correctly (The AddIn has exactly one FormRegion).
I added the FormRegion Manifest File according to this Walkthrough:
Link
Does anybody know what could be wrong here? I don't get any error messages and the AddIn shows in the COM-AddIn dialog in Outlook 2010 but after checking it, it doesn't load. After going into the COM-Addin dialog again, it has unchecked itself. I have also checked the disabled items, however, the AddIn does not appear here.
OK I found the problem. For some reason, the way I added the registry key for the FormRegion was not correct. The correct way is to add the Key with the corresponding class name, in my case IPM.Appointment. Then I had to add a string value with the full name, in my case Condato.Terminauswertung.CustomPropertiesFormRegion and the name of the Add-In with a preceding equal sign as value, in my case =Condato.Terminauswertung. You can find the first two values in the FormRegion class file near the top.