com

I have a function writen in C++ with the next header: void EncodeFromBufferIN(void* bufferIN,int bufferINSize, unsigned char* &bufferOUT, int &bufferOUTSize); I've edited the .h and .cpp files like this, to be able calling the function by importing the DLL in C#: **EncodeFromBufferIN.h** extern "C" { __declspec(dllexport) void EncodeFromBufferIN(void* bufferIN, int bufferINSize, unsigned char* &bufferOUT, int &bufferOUTSize); } **EncodeFromBufferIN.cpp** extern void EncodeFromBufferIN(void* bufferIN, int bufferINSize, unsigned char* &bufferOUT, int &bufferOUTSize){ // stuff to be done } But

I have a very large amount of code written in VBA that I need to migrate to a .Net application. It isn't practical to rewrite all of it as there is just too much, so I was wondering if there is a way to call these vba functions from .NET Thanks. Update: I've been investigating these and it turns out they aren't appropriate. The application isn't Microsoft Office and doesn't expose any sort of "Run" macro functionality. Having done a comparison of the files produced by our legacy third party application and by the sample notepad application, the file formats (viewed in notepad) look very

I need to do the following thing. Create com+ application -> set activation type to Server type-> set identity as Network service->Add user group under creater owner. I am able to set activation type,but i am not able to set identity and the further steps. I am new to com+ applications. the script i have written is as follows $comAdmin = New-Object -comobject COMAdmin.COMAdminCatalog $apps = $comAdmin.GetCollection(“Applications”) $apps.Populate(); $newComPackageName = “test7” $appExistCheckApp = $apps | Where-Object {$_.Name -eq $newComPackageName} if($appExistCheckApp) {

We have an application with activex exe and a com dll. After installing we get an object created in DCOM config. If we try to delete this object from DCOM config, it goes off till we again reopen it. Want to know if there's any procedure to delete this object completely from DCOM and its registries. No idea why this would be tagged VB.Net, but... You can remove most of the server's registration entries by running the EXE with a command line switch as in: MyAx.EXE /unregserver However this leaves a system-synthesized entry under HKCR\AppID after first use. As far as I know you must manually

How can I find out the properties and methods of COM objects returned from some .NET functions, which do not appear to be documented? In the particular example I'm looking at, I'm inserting a picture into Excel using a function like: Set NewPic = ActiveSheet.Pictures.Insert(FileName) (See the SO post on this here .) However, the MSDN documentation for this function only says that Worksheet.Pictures returns an Object, and when I put a watch on the variable during debugging its type is System.__ComObject. Can I find out what other properties and functions might be available for that class (for

I seem to be having trouble getting my COM class library (.NET-based) to support early binding. I am creating a class library in VB.NET 2003 for use in Office 2003 VBA (and later for Office 2010). Documentation @ StackOverflow and elsewhere has brought me to this bit of code: Imports System.Runtime.InteropServices <InterfaceType(ComInterfaceType.InterfaceIsDual), _ ComVisible(True), _ Guid("<some valid GUID>")> _ Public Interface _TestCOMClass Function Test() As String End Interface <ClassInterface(ClassInterfaceType.None), _ ComVisible(True), _ Guid("<another valid GUID>"), _ ProgId(