Hi Nenad,
[quote user="Nenad Poljcic"]I am using update 2.[/quote]
In my opinion any API error should always be tested using the latest MicroStation version, because I know about several different issues (some reported by myself ;-) that were already repaired. There is some progress in API tunning and polishing, so to remain on old CE versions brings only more pain to developers and no benefits.
As discussed in another thread, GetElementByID seems not work correctly (meaning "the same way as in V8i") in Update 4 too, but the other issues should be verified in U4 also.
[quote user="Nenad Poljcic"]I'll leave this one for Bentley people, they can test this faster and better then I can.[/quote]
If you want to speed up testing and make it easier, provide serious professional test case: working code plus dgn file.
[quote user="Nenad Poljcic"]There is a known fact that VS can perform strange when testing, debugging, running 64 bit application[/quote]
I don't know about such issue when debugging NET code. Do you have any reference?
[quote user="Nenad Poljcic"]I have not tried VBA or DgnTools.[/quote]
In my opinion any new code should be based on DgnTool, not only because it seems new managed API is better supported (but still incomplete, on the other hand Update 4 brings substantial progress), but primarily because it provides much better flexibility and comparing to it seem to be IPrimitive and ILocate classes very limited.
With regards,
Jan