Generics and COM Interop don't mix

Posted by: Rick Strahls WebLog, on 10 Jul 2007 | View original | NEW Bookmarked: 0 time(s)

COM Interop is rarely fun, but it looks like it's getting to be less and less useful as time goes on and new .NET Runtime features come along that don't work well over COM. It appears that Generic types can't be exported over COM and be usable to a client like Visual FoxPro. When I create a class like this: [ComVisible(true)] [ClassInterface(ClassInterfaceType.AutoDual)] public class Person { public string Name { get { return _Name; } set { _Name...

Advertisement
Category: .NET | Other Posts: View all posts by this blogger | Report as irrelevant | View bloggers stats | Views: 999 | Hits: 94

Similar Posts

  • 12 ASP.NET MVC Best Practices more
  • MSDN Guidance on ASP.NET MVC vs WebForms and its Impact on my EF + ASP.NET Work more
  • Sneak Peak: CSS Sprites Make Your Websites Faster more
  • New Entity Framework Feature CTP for VS2010 Beta 2 more
  • The Underground at PDC more
  • StackOverflow DevDays in London more
  • Welcome the WebUI Test Studio v2.0! more
  • Add Reference Dialog Improvements (VS 2010 and .NET 4.0 Series) more
  • Get Ready for Teleriks Custom-built Extensions for ASP.NET MVC more
  • Eschewing Date Types in our Database more

News Categories

.NET | Agile | Ajax | Architecture | ASP.NET | BizTalk | C# | Certification | Data | DataGrid | DataSet | Debugger | DotNetNuke | Events | GridView | IIS | Indigo | JavaScript | Mobile | Mono | Patterns and Practices | Performance | Podcast | Refactor | Regex | Security | Sharepoint | Silverlight | Smart Client Applications | Software | SQL | VB.NET | Visual Studio | W3 | WCF | WinFx | WPF | WSE | XAML | XLinq | XML | XSD