Support for C# ActiveX controls in MSOffice?

[Siegfried Heintze]

In 2004 (approximately) MS Tech support explained that while there was
limited support for native mode Active X controls in a few cases (like IE),
ActiveX controls should be all native code (especially for MS Office).

Has this change with VS2005? Does MSOffice Support ActiveX controls written
in J#, C# and Javascript.net?

Thanks,
Siegfried

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

Siegfried,

It never did. You can not create ActiveX controls with .NET (there are
hacks around this, but as you have figured out, they are unsupported).

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

"Siegfried Heintze" <si*******@heintze.comwrote in message
news:uP*************@TK2MSFTNGP06.phx.gbl...

In 2004 (approximately) MS Tech support explained that while there was
limited support for native mode Active X controls in a few cases (like
IE), ActiveX controls should be all native code (especially for MS
Office).

Has this change with VS2005? Does MSOffice Support ActiveX controls
written in J#, C# and Javascript.net?

Thanks,
Siegfried

[Willy Denoyette [MVP]]

"Siegfried Heintze" <si*******@heintze.comwrote in message
news:uP*************@TK2MSFTNGP06.phx.gbl...
| In 2004 (approximately) MS Tech support explained that while there was
| limited support for native mode Active X controls in a few cases (like
IE),
| ActiveX controls should be all native code (especially for MS Office).
|
| Has this change with VS2005? Does MSOffice Support ActiveX controls
written
| in J#, C# and Javascript.net?
|
| Thanks,
| Siegfried
|
|

No, .NET is not targeting AX control authoring. This is (and AFAIK remains)
the domain of unmanaged code. Note that this is not a language issue, it's
simply the CLR which doesn't expose the AX control interfaces, note that COM
interfaces are exposed (and imported) by the CLR, the .NET languages can't
even author COM objects.

Willy.