have an application which does a spatial query based on the extent of the map display. All the services and map are in the same custom projection. When I use the 2.0 API the query task fails due to using a WKT coordinate system however if I switch back to the 1.6 API everything works fine. I have tried explicitly setting all the spatial references for the query and geometry and the query still fails. I could switch back to 1.6 however I am using the 2.0 API geometry service to project user-defined geographic locations in to this custom projection which is not supported in 1.6.
Any ideas or thoughts would be appreciated?
Thanks
