Things had started to lag a bit, but an email from Tom Luther and his patch a few days later brought a sudden influx of activity. He helped fix some of the events problems, and it now seems to work in the most part - and uncover a couple of other bugs!

The major feature which is missing is the databinding. The original GMap.Net Control had a good method for this, but it was hard wired into the main GMap class, and made for bulky code. I tried to break it down into more of a pattern form, but this hasn't had the desired effect (it doesn't work!), and so we need to keep on debugging it.

I've also started work on creating Unit Tests. Using NUnit I have created empty unit testing classes for all the GMap classes, I just need to now implement testing methods. My work so far has achieved a small 4% code coverage, showing there is still a long way to go. If anyone is contemplating helping out, this would be an excellent place to start.

The control is improving steadily, today I added support for Google Map GControls to the GMap.Net version 2. This is a good step forward, the map is slowly looking better and working as it should.

But I noticed a lot of major bugs/Todo areas:
Databinding does not work - I created a new namespace and classes specifically for creating objects by databinding, but it does not seem to be working at all! This is either due to something wrong with my new databinding methods, or more likely I haven't updated the GXPage/XSL files to accomodate them.

Events are not working either - Using the same methods from GMap.Net version 1, I basically copied and pasted the code to accomodate for the new events in Google Map API v2. Somewhere along the lines it has decided to stop working, I think this is the most frustrating of all the bugs. I had a plan to change the Callback function, and make events a bit more extensible, but I'll put it on hold until I can get the simple function working. I would also like to make the events return 'void' instead of 'string', but again I'll wait until I get the basics working.

XSL - with all the new classes added to GMap2 this file, and all the XmlSerialization need a lot of work done before they will come up to scratch. If I tackle this one class at a time, hopefully it will start showing signs of improvement!

FxCop - I'm trying to make the control as compliant as possible, so I'm continually checking it with FxCop, so I can spot problems with the framework and change it so it behaves as users would expect. When I first ran it when I started work on the project, I got around 600 errors and warnings, now I've whittled that down to 375. As I mentioned above, I would like to change the events to return 'void' instead of 'string'. If we could get that sorted I think FxCop would reduce to about 100!