Is there default integration between Outlook 2010 64 bit and NAV 2009 R2? If not, is there any work around to use Outlook 64 bit as default mail client for NAV 2009 R2?
Thank you in advance.
After a research I realized that NAV 2009 supports only Office x86. In my opinion you must write your own automation (.dll libraries) in order to use x64 Office.
You can try to use dotnet Interoperability in your Dynamics NAV code.
Just add a dotnet var to your globals and find the subtype Microsoft.Office.Interop.Outlook
If you tell me what you are trying to integrate maybe I can help.
Related
Hey Helpers from Stackoverflow!
I am from the Netherlands, so sorry for my English, with that out of the way I have a question. I own a mc67(portable scanner) running windows mobile 6.5 professional, I am trying to make an application where I can scan some bar codes and email it. I am making the application in visual basic in visual studio 2008, why? I got the scanner only working correctly with vista where I already had vs 2008 installed. I found out that I can't use system.net.mail, I am not a Pro at Visual basic but I know a bit, but I am new to windows 6.5 mobile development. So my question is how do I make this work?
Thanks in advance.
-Kgeest
First look at the sample code for barcode scanning coming with the EMDK (SDK) from Zebra/Motorola/Symbol.
When you are familar with barcode scanning, you can start to look at Windows Mobile Outlook Session to create an email and send by code (C# example at https://github.com/hjgode/eMdiMail/blob/master/eMdiMail/sendMail.cs).
If you have no programming experience, look for a software partner.
I have created a small application to send emails via Outlook. The application opens an Outlook mail item with various pre-configured templates.
Now, the application was first build for Outlook 2010 using the Interop version 14. When testing on Outlook 2007, the application fails to create the required MailItem. I was assuming that the Interop would be backwards compatible, but that doesn't to be the case.
I have already tried using the Interop v12 instead, but then the application doesn't work on version 2010.
How can I make this application work with both Outllok 2007 and 2010.
Cheers,
Martin
You need to develop using the lowest supported version of Outlook (2007).
What exactly does not work when running under Outlook 2010 when you are using the 2007 interop?
Windows 8 had released! I want to create a metro style DESKTOP application like GitHub-for-Windows(http://windows.github.com/).How can I develop this kind style? WPF,WinForm or others.
Does Microsoft supply solutions for Desktop Metro applications at Visual Studio 2012?
Have a look at Mahapps.Metro
It is exactly for what you want.
I have used it and I found it very easy to get in to.
EDIT
You could also have a look at the more recently released Modern UI for WPF
I'm not sure if this is the right forum for this. But anyway, you can check this out
Microsoft does provide Visual Studio Express for Windows 8.
does anyone know if there is a guide to creating an outlook add in for office 2010 that runs in 64bit mode?
I have an add in that DOES work on in Outlook 2010 32bit but it doesn't appear in 64bit - in the add in section its set to disabled.
I have tried to compile under different target CPU's but that hasn't helped..
This: Link has a section on 32\64 bit compatibility.
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.