Hello ThinkGeo-Team,
we use Desktop Edition (v. 4.0.40.82) with .Net Framework 2.0.
Now I made some test with Daily Development Build 4.0.126.0 and recognized that I had to reference WindowsBase.dll with .Net Framework Version 3.0.
Does this mean that your upcoming release in November only supports Framework Version 3.0 or higher?
Thomas
Hi Thomas,
The reason why we add WindowsBase to reference is that we did some enhancement for GeoCollection, now it can raise events when you operate it, and also it will be easier to write xmal binding code for it in Wpf or Silverlight application. I think the next public release will supports .net framework 3.0 or higher because we did that. Sorry for inconvenice.
Right now, most of users install .net framework 3.0, it will make your programe more powerful.
If you want to solve this problem, you might create a ticket we can speed time to think a workaround.
James
Thomas,
To add a little to what James said… We try and keep compatibility with the oldest framework possible but it is very hard as new programing techniques are introduced that require us to rely on newer version of the framework. In this case it was the INotifyPropertyChanged which was requested by more and more customers who use MVVM and heavy data binding. Our official stance is that we will keep compatibility one framework behind the current one. For example the current framework is 4.0 so we will ensure that we will only use things from 3.5 or before. In most cases we stay even further behind that than, 3.0 in this case. We have to allow ourselves some wiggle room though to try and balance all of our customers expectations.
David