Mixing Foobar2000 with CLR (.NET) 2006-03-27 19:23:56 I’ve just about run out of ideas with this problem. Say I have an “empty” Foobar plugin with the following code (literally this is it):Code: [Select]#include "foobar2000.h"DECLARE_COMPONENT_VERSION("dotnet test", "1.0", "body massage!");When you compile it, it works perfectly in native mode. So, then let me turn on .NET support (/clr basically). component_client also needs /clr since it appears to contain the initialization of the component itself. The plugin compiles and works in Foobar just fine with /clr.But, there is an odd problem. Foobar’s drag and drop support becomes broken and the SysTreeView32 in 'Add Folder…' has vanished. It’s obvious the plugin hasn’t done anything explicit to cause these problems.These issues don't exist when making a CLR DLL for 0.8.3 in .NET 1.1. It's a new problem using 0.9 and .NET 2.0.So what could be causing this? I’m really stumped, it’s a very strange conflict. If anyone has an idea or even a hypothesis, it would be great to hear since I’m out of ideas.