Com connection

[dave]

Hi,
Can any one tell me what`s the diffrent bettwin the two configuration to
expose a C# class to a com object:

[Guid("B6F829AA-D1D0-4f14-9B3E-D8D4FA033819")]

public class ConfigurationBuilder : IConfigurationBuilder

{...}

[ClassInterface(ClassInterfaceType.None)]

public class ConfigurationBuilder : IConfigurationBuilder

{...}

when should i use GUID and when should i use the ClassInterfaceType
attribute and whate the comoiler do with this attribute?

Thanks.

[Nicholas Paldino [.NET/C# MVP]]

Dave,

You should actually be using BOTH of these attributes, as they both do
different things. The Guid attribute on the class is going to declare what
the CLSID of the COM component will be. The ClassInterface attribute will
indicate that the class will not export an interface of its own. They
should both be on there.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"dave" <Da************@verint.com> wrote in message
news:O$**************@TK2MSFTNGP12.phx.gbl...

Hi,
Can any one tell me what`s the diffrent bettwin the two configuration to
expose a C# class to a com object:

[Guid("B6F829AA-D1D0-4f14-9B3E-D8D4FA033819")]

public class ConfigurationBuilder : IConfigurationBuilder

{...}

[ClassInterface(ClassInterfaceType.None)]

public class ConfigurationBuilder : IConfigurationBuilder

{...}

when should i use GUID and when should i use the ClassInterfaceType
attribute and whate the comoiler do with this attribute?

Thanks.

[Francis Gingras]

And what is the advantage of declaring a CLSID vs. letting the VS create
one?

Do we need a different CLSID for every class, or only one for the dll?

Francis

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in
message news:eO**************@tk2msftngp13.phx.gbl...

Dave,

You should actually be using BOTH of these attributes, as they both do
different things. The Guid attribute on the class is going to declare what the CLSID of the COM component will be. The ClassInterface attribute will
indicate that the class will not export an interface of its own. They
should both be on there.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

[Nicholas Paldino [.NET/C# MVP]]

Francis,

When you let .NET create the CLSID, it will create a new one every time
you build the application. This can get quite messy, and locating the
registry entries (if you have to) can be a pain.

You will need to create one for every class that you plan on exporting
to COM, as well as every interface you want to export to COM.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com

"Francis Gingras" <pr*****@nowhere.com> wrote in message
news:%2***************@tk2msftngp13.phx.gbl...

And what is the advantage of declaring a CLSID vs. letting the VS create
one?

Do we need a different CLSID for every class, or only one for the dll?

Francis

"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard.caspershouse.com> wrote in message news:eO**************@tk2msftngp13.phx.gbl...

Dave,

You should actually be using BOTH of these attributes, as they both do different things. The Guid attribute on the class is going to declare

what

the CLSID of the COM component will be. The ClassInterface attribute will indicate that the class will not export an interface of its own. They
should both be on there.

Hope this helps.

--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com