COM Interop question in .NET 2.0

[Vish]

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the following
attributes for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I also
have two functions in the class to register and unregister the COM with the
registry. But when i try to build it in VS.NET 2005, i get the following
error "XXX.dll does not contain any types that can be registered for COM
Interop" and "XXX.dll does not contain any types that can be Unregistered for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody know of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

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

Vish,

Is it an error in the build process, or the registration process?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:19******** *************** ***********@mic rosoft.com...

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the following
attributes for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I also
have two functions in the class to register and unregister the COM with
the
registry. But when i try to build it in VS.NET 2005, i get the following
error "XXX.dll does not contain any types that can be registered for COM
Interop" and "XXX.dll does not contain any types that can be Unregistered
for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody know
of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

[Jason Newell]

Vish,

Could it be that ComVisible is false by default now in 2.0? Try the
following example and see if it works.

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]
[ComVisible(true )]
Jason Newell
Vish wrote:

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the following
attributes for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I also
have two functions in the class to register and unregister the COM with the
registry. But when i try to build it in VS.NET 2005, i get the following
error "XXX.dll does not contain any types that can be registered for COM
Interop" and "XXX.dll does not contain any types that can be Unregistered for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody know of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

[Willy Denoyette [MVP]]

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:19******** *************** ***********@mic rosoft.com...

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the following
attributes for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I also
have two functions in the class to register and unregister the COM with
the
registry. But when i try to build it in VS.NET 2005, i get the following
error "XXX.dll does not contain any types that can be registered for COM
Interop" and "XXX.dll does not contain any types that can be Unregistered
for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody know
of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

Don't know what exactly you do in the functions that register/unregister the
class, mind to post your code?
Willy.

[Vish]

Hi Jason,

Seems like that did the trick. i am able to build the class after setting
the ComVisible attribute of the class to true. I appreciate your help in this
matter.

Thank You,
Vish
"Jason Newell" wrote:

Vish,

Could it be that ComVisible is false by default now in 2.0? Try the
following example and see if it works.

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]
[ComVisible(true )]
Jason Newell
Vish wrote:

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the following
attributes for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I also
have two functions in the class to register and unregister the COM with the
registry. But when i try to build it in VS.NET 2005, i get the following
error "XXX.dll does not contain any types that can be registered for COM
Interop" and "XXX.dll does not contain any types that can be Unregistered for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody know of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

[Vish]

Hi Nicholas,

The error occured while building. But i was able to solve the problem by
setting the ComVisible attribute to true on the class according to Jason's
reply. I think the ComVisible attribute is set to false by default where in
it was true by default in 1.1.

I appreciate your help in this matter.

Thank You,
Vish
"Nicholas Paldino [.NET/C# MVP]" wrote:

Vish,

Is it an error in the build process, or the registration process?
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:19******** *************** ***********@mic rosoft.com...

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the following
attributes for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I also
have two functions in the class to register and unregister the COM with
the
registry. But when i try to build it in VS.NET 2005, i get the following
error "XXX.dll does not contain any types that can be registered for COM
Interop" and "XXX.dll does not contain any types that can be Unregistered
for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody know
of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

[Vish]

Hi Willy,

Jason's suggestion fixed my problem. Looks like the ComVisible property is
false by default in .NET 2.0 where in it was true by default in 1.1. If you
are still interested in looking at the code, let me know. I will post it. I
appreciate you help with this issue.

Thank You,
Vish
"Willy Denoyette [MVP]" wrote:

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:19******** *************** ***********@mic rosoft.com...

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the following
attributes for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I also
have two functions in the class to register and unregister the COM with
the
registry. But when i try to build it in VS.NET 2005, i get the following
error "XXX.dll does not contain any types that can be registered for COM
Interop" and "XXX.dll does not contain any types that can be Unregistered
for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody know
of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

Don't know what exactly you do in the functions that register/unregister the
class, mind to post your code?
Willy.

[Willy Denoyette [MVP]]

Can't be the reason as the default for ComVisible is still true.

Willy.

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:03******** *************** ***********@mic rosoft.com...

Hi Willy,

Jason's suggestion fixed my problem. Looks like the ComVisible property is
false by default in .NET 2.0 where in it was true by default in 1.1. If
you
are still interested in looking at the code, let me know. I will post it.
I
appreciate you help with this issue.

Thank You,
Vish
"Willy Denoyette [MVP]" wrote:

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:19******** *************** ***********@mic rosoft.com...

> Hi,
>
> I am trying to expose my .NET 2.0 class as a COM type using the
> following
> attributes for the attributes
>
> [ClassInterface( ClassInterfaceT ype.None)]
> [Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]
>
> I have the "Register for COM Interop" build property set to true. I
> also
> have two functions in the class to register and unregister the COM with
> the
> registry. But when i try to build it in VS.NET 2005, i get the
> following
> error "XXX.dll does not contain any types that can be registered for
> COM
> Interop" and "XXX.dll does not contain any types that can be
> Unregistered
> for
> COM Interop". The same code works perfectly in VS.NET 2003. Anybody
> know
> of
> any reasons why this is happeneing or what i am doing wrong?
>
> Thank You,
> Vish

Don't know what exactly you do in the functions that register/unregister
the
class, mind to post your code?
Willy.

[Jason Newell]

Vish,

Willy is correct per documentation:
http://msdn2.microsoft.com/en-us/lib...US,VS.80).aspx.

I'd be interested to know why explicitly settings [ComVisible(true )]
fixed the problem. Unfortunately, I don't have 2.0 or I'd test it myself.

Jason Newell
Willy Denoyette [MVP] wrote:

Can't be the reason as the default for ComVisible is still true.

Willy.

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:03******** *************** ***********@mic rosoft.com...

Hi Willy,

Jason's suggestion fixed my problem. Looks like the ComVisible property is
false by default in .NET 2.0 where in it was true by default in 1.1. If
you
are still interested in looking at the code, let me know. I will post it.
I
appreciate you help with this issue.

Thank You,
Vish
"Willy Denoyette [MVP]" wrote:

"Vish" <Vi**@discussio ns.microsoft.co m> wrote in message
news:19***** *************** **************@ microsoft.com.. .

Hi,

I am trying to expose my .NET 2.0 class as a COM type using the
following
attribute s for the attributes

[ClassInterface( ClassInterfaceT ype.None)]
[Guid("8D0240AD-1BBE-4831-8214-39DD46A4A797")]

I have the "Register for COM Interop" build property set to true. I
also
have two functions in the class to register and unregister the COM with
the
registry. But when i try to build it in VS.NET 2005, i get the
following
error "XXX.dll does not contain any types that can be registered for
COM
Interop" and "XXX.dll does not contain any types that can be
Unregistere d
for
COM Interop". The same code works perfectly in VS.NET 2003. Anybody
know
of
any reasons why this is happeneing or what i am doing wrong?

Thank You,
Vish

Don't know what exactly you do in the functions that register/unregister
the
class, mind to post your code?
Willy.

[Willy Denoyette [MVP]]

"Jason Newell" <no****@nospam. com> wrote in message
news:Oe******** ******@TK2MSFTN GP15.phx.gbl...

Vish,

Willy is correct per documentation:
http://msdn2.microsoft.com/en-us/lib...US,VS.80).aspx.

I'd be interested to know why explicitly settings [ComVisible(true )] fixed
the problem. Unfortunately, I don't have 2.0 or I'd test it myself.

Jason Newell

And not only per documentation ;-), it was the default since version 1.0 and
did not change in v2.0 (that would be a breaking change).
I tested this with v2.0 and I can confirm 'true' is still the default.

Willy.