I made a .NET COM DLL (VS2012, C#) it registers fine with regasm, but not with regsvr32. Also when I add the .tlb into installer and extract the com stuff (Installshield 2012) there is no registry entries after I have ran the installer. DLL is 32-bit and I'm using 64-bit Windows.
I am using office 2007 interop DLL to create an Excel sheet in c#.NET.
when I tried to test my app on a machine with office 2003 installed I get an exception because of the version number of the DLL . How can I determine in runtime what version of office is installed and then load the appropriate interop DLL for that version ?
If you do not need features which became available in Office 2007, just use an interop dll for old versions of Office also when current Office is installed! A PIA created with Office XP still works with Office 2010.
Otherwise, you have to find out the registry keys of Excel...
Sorry, my English sucks, I hope I can express clearly.i want to add a bar to the windows explorer,after a long time searching,i'v made a bar using BandObjectsLib(a C# library) and added it in to the Explorer window.but i have to open it through "Menu-View-Explorer bar",and the bar also came out in IE :<.my question is how to make it opened automaticly when Windows Explorer is opend.Or any other way to do this,i want to add a big horizontal bar actually a region in the bottom (or somewhere else) of Windows Explorer,so i can put my code and usercontrols into it.i use C#,vs2012,windows 7.thank you!
I've just been handed the task of replacing an existing COM component.
It has to stay as a COM component as we have no ability to change the caller.
It has to able to call a COM component, that again we can't alter. i.e. where changing the middle part of an existing process and have to do so transparently.
I've been doing some background research, and it looks like I can create a .NET COM component easy enough. I've got a few q's though.
When you create the COM interface and class they have GUID's, do these GUID's have to match the existing COM component? Or is it when the caller makes the COM call the OS determines the component based on name?
Another requirement is that the final COM call is 'dynamic' in that the method name we have to call might change, assuming the method will act on the same data is this doable?
Regarding the last bit, I have to call another third-party COM component. But as the third-party app might be replaced, if possible I'd like to be able to configure the name of the component and method called? (assuming the new and old method are similar in parameters etc)
I am trying to run a Simple CUDA program which queries the numbers of GPUs in the nodes using Open MPI v1.6.1 (64bit)inWindows 7 Professional 64bit Machines. When I run the application in root node, the correct GPU count is getting. But when the same application is tried to run in different nodes remotely using Open MPI, the GPU count is getting as0, ie, it is showing as No CUDA capable GPU is present in the node.
The root and the nodes havingCompute Capability 2.1 capable GPUs. I have built the code withCUDA 4.2. When a normal MPI application is running, it is working correctly.
Is there any special settings required for running a CUDA application in Windows 7 using Open MPI v1.6.1?
I have a piece of software written by someone else that has a couple COM+ Applications (which seem to work properly) and they need to in some instances talk to a Desktop type app that creates a DCOM object. For some reason this works flawlessly on Windows XP but does not work on Windows 7. Again to clarify the only problem is the link between the COM+ Applicaiton and the DCOM Object the rest of the code works great.
I am not sure that there are anymore COM developers. But I once wrote a COM DLL that I used in an MFC desktop application that was also used in a web application if that helps.
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
I'm investigating ways in which a COM component is exposed to the world wide web, preferably in IIS 7.
..you're posting a question - there's a difference.
Is this an exercise in futility, or do COM developers frequently write components to be executed in a windows desktop application as well as in a web application?
Though I do use COM-controls (written in .NET), they do not run on the webserver, but in the webbrowser. Meaning it has the same limitations as installed software, which has, obviously, the preference.
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
Last Visit: 31-Dec-99 19:00 Last Update: 27-Nov-15 2:38