PC Review


Reply
Thread Tools Rate Thread

Creating an interop dll

 
 
Anders Eriksson
Guest
Posts: n/a
 
      1st Oct 2011
I'm using a COM server to access some hardware (Laser). The Supplier has
a strange idea that they don't update the version of the .exe (COM
Server). It's always 1.0.0.0

When I use this COM server VS2010 will create an Interop dll
automatically. This will also always have version 1.0.0.0 (I'm guessing
that it just copy the version from the COM server exe)

I guessing here but it seems like vs2010 will not recognize that a new
exe file has been installed and doesn't recreate the Interop dll.

First is this guess true?

Is there someway of changing the version in the COM Server / Exe file
without having the source code?

Any other idea is also welcome.

Yeah, the obvious solution is to get the maker of the COM server to
add/change the version, but I have tried that and no such luck...
--
English isn't my first language.
So any error or strangeness is due to the translation.
Please correct my English so that I may become better.
 
Reply With Quote
 
 
 
 
Anders Eriksson
Guest
Posts: n/a
 
      2nd Oct 2011
On 2011-10-02 00:35, Peter Duniho wrote:
> On 10/1/11 11:46 AM, Anders Eriksson wrote:
>> [...]
>> Is there someway of changing the version in the COM Server / Exe file
>> without having the source code?

>
> It's not pretty, but can't you just delete the interop DLL as needed
> when the .exe is updated, so that a new interop DLL is created? It's a
> manual process, but you seem to already have manual intervention anyway.
>

Well, that's what I do today, so I guess I will continue...

> Of course, there is also the question as to why a new interop DLL would
> be needed anyway. As long as the COM interface remains the same, a new
> version of the COM server should not require a new interop DLL. And
> except during initial development, any given COM interface really ought
> to remain static. If there's a need to change the interface, there
> should be a whole new interface, rather than changing the old one.
>

The problem is that I'm detecting bugs and needs that will change the
COM Interface. So almost every update of the COM server will change the
interface...

Well, just another thing to live with ;-)

Thank you for your answer!

// Anders
--
English isn't my first language.
So any error or strangeness is due to the translation.
Please correct my English so that I may become better.
 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Interop.CDO uses Interop.ADODB which has a higher version... muriwai Microsoft C# .NET 7 27th Oct 2011 08:00 PM
I need help with creating a Dll so I can call using COM interop =?Utf-8?B?UHVjY2E=?= Microsoft C# .NET 0 11th May 2006 03:03 AM
Creating a COM interop using VS.NET 2005? =?Utf-8?B?QXNhZg==?= Microsoft C# .NET 16 6th Jan 2006 02:56 AM
Creating a COM interop using VS.NET 2005? =?Utf-8?B?QXNhZg==?= Microsoft C# .NET 3 28th Dec 2005 05:53 AM
Need help with C# COM Interop, creating a DCOM server =?Utf-8?B?RGF2aWQgRG9saGVndXk=?= Microsoft Dot NET 0 10th Dec 2004 08:45 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 08:56 PM.