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.
Related
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.
I am trying to run an .ocx library for a VB6 project that I have. However, every time that it calls the first object property, it generates the error below:
Line 937: Property OleObjectBlob in ICImagingControl1 could not be set.
Line 937: Cannot load control ICImagingControl1; license not found.
Some forums mention that the cause is using an old VB6 version, or a missing file FM20ENU.DLL in System32 (my case SYSWOW64). I already upgraded too the latest VB6 version (which is still quite old) and made sure the file was in the right folder. Neither of them worked for me, any ideas why is this issue happening?
Thanks
I installed and uninstalled several times the software, which created a reference to the wrong ocx in the registry. To solve this, I uninstalled IC Imaging Control, proceeded to erase the references in the tree, and reinstalled the proper version.
I was asked by a client of mine to edit an old vb6 project and ran in the same problem.
Googled for a solution until I found this:
https://jeffpar.github.io/kbarchive/kb/195/Q195353/
Downloaded and executed the program and the project could be perfectly edited.
Original text of this Microsoft article:
Q195353: FILE: VBUSC.EXE Provides Licensing for Discontinued Controls
Article: Q195353
Product(s): Microsoft Visual Basic for Windows
Version(s): 6.0
Operating System(s):
Keyword(s): kbfile kbusage kbCtrl kbLicensing kbVBp kbVBp500 kbVBp600 kbGrpDSVB kbFAQ kbVBp600FAQ k
Last Modified: 21-JUN-2002
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Visual Basic Learning Edition for Windows, version 6.0
- Microsoft Visual Basic Professional Edition for Windows, version 6.0
- Microsoft Visual Basic Enterprise Edition for Windows, version 6.0
-------------------------------------------------------------------------------
SUMMARY
=======
VBUSC.EXE is a file that installs the Design-Time Licenses for ActiveX controls
that shipped with earlier versions of Visual Basic, but are no longer supported
and have been discontinued with the current version.
MORE INFORMATION
================
The following file is available for download from the Microsoft Download
Center:
VBUSC.exe
(http://download.microsoft.com/download/VB60Pro/Install/2/Win98/En-US/VBUSC.exe)
Release Date: August 15, 2000
For additional information about how to download Microsoft Support files, click
the following article number to view the article in the Microsoft Knowledge
Base:
Q119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current
virus-detection software that was available on the date that the file was
posted. The file is stored on secure servers that prevent any unauthorized
changes to the file.
FileName Size
---------------------------------------------------------
VBUSC.EXE 88k
The following controls are no longer supported by Microsoft Visual Basic:
ActiveX Control Name Filename
------------------------------------------------
Desaware Animated Button Control ANIBTN32.OCX
Microhelp Gauge Control GAUGE32.OCX
Pinnacle-BPS Graph Control GRAPH32.EXE
Microsoft Grid Control GRID32.OCX
Microhelp Key State Control KEYSTA32.OCX
Microsoft Outline Control MSOUTL32.OCX
Outrider SpinButton Control SPIN32.OCX
Sheridan 3D Controls THREED32.OCX
The ActiveX controls listed above are no longer supported, but ship with the
Professional and Enterprise Editions of Microsoft Visual Basic for backward
compatibility when upgrading existing projects.
These controls do not ship with the Learning Edition of Microsoft Visual Basic.
For the Professional and Enterprise Editions, the controls are located on the
installation CDs at the following locations:
Microsoft Visual Basic Edition Location
----------------------------------------------------------------------
Professional 6.0 \Common\Tools\VB\Controls
Enterprise 6.0 \Common\Tools\VB\Controls
Visual Studio Professional 6.0 \Common\Tools\VB\Controls (CD2)
Visual Studio Enterprise 6.0 \Common\Tools\VB\Controls (CD3)
Each of these directories contain a README.TXT with instructions on how to
install the controls for design-time use.
NOTE: Using the Learning Edition to upgrade a project developed in an earlier
version of Microsoft Visual Basic might result in licensing problems for these
controls.
The VBUSC.EXE installs the design-time licenses for the controls listed above if
Visual Basic is detected on the computer.
REFERENCES
==========
For additional information, please see the following articles in the Microsoft
Knowledge Base:
Q194784 INFO: Controls Shipped in Visual Basic 6.0
Q172193 INFO: List of VB 4.0 Custom Controls Discontinued in VB 5.0
I got a installer for Visual Studio 2010 x86 from the msdn academic alliance, and I intalled on my computer with Windows 7 Home Premium and M460 i5 processor. It runs great, except it doesn't debug, neither C# nor C++.
If I build the project, and then press the debug button, it works. But why Debug button doesn't build automatically?
How can I make the debug button auto-compile and debug just clicking it, instead of first click build button and then click debug button?
SOLUTION: Oops, problem solved, it was just a silly thing ...
Tools > Options> Projects and Solutions > Build and Run > On Run, When Projects Are Out Of Date > Always build
UPDATE: Since the title is misleading, I think it is important to clarify that Visual Studio 2010 x86 (32 bits) installer works perfectly on amd64 (64 bits) machines. In fact,I think there is only x86 installer.
My VS2010 Pro x86 that I acquired via our WebsiteSpark membership works fine on my Win7 Home Premium 64bit on an HP Pavilion w/AMD Turion II Ultra M620.
Could you elaborate on what you mean by "debug button doesn't do it automatically"? What exactly are you expecting to happen, and what exactly is happening?
Also, from what you say, debugging does work... just not when you try to do it via a certain process.
It works just fine. I'm running it now. If you're having trouble installing, try right-clicking on the installer and selecting "Run as Adminstrator".
not to familier with the software but have had simlar problem with similar programs.
if there is yet a 64x c# or c++ if so try install them it may just update the win7 binery files needed for the scripts to 64bit (or relivent files needed)
possibly a long shot put worth ago
hope it helps sorry for bad spelling
I've downloaded a Vista icon from the web for a new application I'm developing. When I try to compile it in Visual Studio 2005 C++, I get an error message:
error RC2176 : old DIB in res\XXXXX.ico; pass it through SDKPAINT
The error message seems a little misleading, I think the "old DIB" is actually a newer format that it wasn't expecting. I've never heard of SDKPAINT, and Search doesn't find it installed on my system anywhere. Microsoft claims SDKPAINT comes with the Windows 3.0 SDK, but I can't download any SDK due to incompatibilities with our firewall.
I don't really need anything Vista specific in this icon, so anything that would dump the incompatible bits would be fine.
I did a little more digging, and I found this previous question:
Which Icon Editing Software would you recommend for creating icons for apps
The accepted answer for that question suggested IcoFX. I downloaded that and used it to delete the 256x256 and 128x128 versions of the icon, and now everything's fine.
There are two more ways to achieve this in Visual Studio 2005:
replace rc.exe and rcdll.exe of your Visual Studio 2005 installation with the ones from a newer SDK (e.g. Windows Vista, 7 ...) or DDK/WDK (ditto)
or integrate the newer SDK into your Visual Studio 2005 using the respective tool that comes with the SDK
The resource compiler is the part that creates the .res files and then the usual Visual Studio 2005 linker (with the first option) or the SDK tool chain's liner links that into the binary. Meaning that even in conservative scenarios where it is frowned upon to upgrade the tool chain as a whole, this should be harmless.
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.