Hello,
first of course thanks for your effort.
I'm using your wrapper inside of a custom .NET 2.0 library. When updating the wrapper dll from 2.3.4 to 2.5.14 (both .NET 2.0 versions) and using the custom .NET 2.0 library in a .NET 4.0 Client WPF project, which is using the class System.Collections.Specialized.NotifyCollectionChangedEventArgs, I get an conflict that the type 'NotifyCollectionChangedEventArgs' exists both in your wrapper and .NET.
Error CS0433 The type 'NotifyCollectionChangedEventArgs' exists in both 'Microsoft.Win32.TaskScheduler, Version=2.5.14.0, Culture=neutral, PublicKeyToken=0d013ddd5178a2ae' and 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
I'm not sure if this is a configuration problem on my side or an unwanted behaviour of the wrapper. Maybe someone dealed with that issue as well and have a simple solution (other than switching my custom library to .NET 4.0).
Crayjin
first of course thanks for your effort.
I'm using your wrapper inside of a custom .NET 2.0 library. When updating the wrapper dll from 2.3.4 to 2.5.14 (both .NET 2.0 versions) and using the custom .NET 2.0 library in a .NET 4.0 Client WPF project, which is using the class System.Collections.Specialized.NotifyCollectionChangedEventArgs, I get an conflict that the type 'NotifyCollectionChangedEventArgs' exists both in your wrapper and .NET.
Error CS0433 The type 'NotifyCollectionChangedEventArgs' exists in both 'Microsoft.Win32.TaskScheduler, Version=2.5.14.0, Culture=neutral, PublicKeyToken=0d013ddd5178a2ae' and 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
I'm not sure if this is a configuration problem on my side or an unwanted behaviour of the wrapper. Maybe someone dealed with that issue as well and have a simple solution (other than switching my custom library to .NET 4.0).
Crayjin