Skip to main content
added 205 characters in body
Source Link
Mawg
  • 40.5k
  • 110
  • 334
  • 582

A change needs to be made in a DLL. The DLL was originally coded in VB6 (not by me), and the source code lost.

It is very simple in its functionality, so I recreated it from scratch, but I only have access to VB Express 2008.

I created it first as a normal DLL then realized it had to be a COM DLL. Fortunately, an excellent article at http://www.codeproject.com/KB/COM/nettocom.aspx tells me how.

But, I don't know anything about GUIDs...

Should I use the same GUID as the original DLL or not? Does it make any difference?


Edit: Does it really matter since it's a COM DLL? It is called into by an Active X control & I can see no reference in the web page to the GUI ... (but I'm just a n00b, so what do I know? ;-)

A change needs to be made in a DLL. The DLL was originally coded in VB6 (not by me), and the source code lost.

It is very simple in its functionality, so I recreated it from scratch, but I only have access to VB Express 2008.

I created it first as a normal DLL then realized it had to be a COM DLL. Fortunately, an excellent article at http://www.codeproject.com/KB/COM/nettocom.aspx tells me how.

But, I don't know anything about GUIDs...

Should I use the same GUID as the original DLL or not? Does it make any difference?

A change needs to be made in a DLL. The DLL was originally coded in VB6 (not by me), and the source code lost.

It is very simple in its functionality, so I recreated it from scratch, but I only have access to VB Express 2008.

I created it first as a normal DLL then realized it had to be a COM DLL. Fortunately, an excellent article at http://www.codeproject.com/KB/COM/nettocom.aspx tells me how.

But, I don't know anything about GUIDs...

Should I use the same GUID as the original DLL or not? Does it make any difference?


Edit: Does it really matter since it's a COM DLL? It is called into by an Active X control & I can see no reference in the web page to the GUI ... (but I'm just a n00b, so what do I know? ;-)

Source Link
Mawg
  • 40.5k
  • 110
  • 334
  • 582

Recreating a COM DLL, do I need to worry about the GUID?

A change needs to be made in a DLL. The DLL was originally coded in VB6 (not by me), and the source code lost.

It is very simple in its functionality, so I recreated it from scratch, but I only have access to VB Express 2008.

I created it first as a normal DLL then realized it had to be a COM DLL. Fortunately, an excellent article at http://www.codeproject.com/KB/COM/nettocom.aspx tells me how.

But, I don't know anything about GUIDs...

Should I use the same GUID as the original DLL or not? Does it make any difference?