It is C#, but it is still an uphill battle. I think vb.net would have been easier for me as it so much closer to vba, way easier to convert code. But now that I've gone this far I do see some of the points you and others make for it being a better language. A big help was finding the sites that offer VB.net and C# comparison.
Until then I was spending 2 hours searching for how to use something small like select case and then how to use more than one item in the case call.
switch (sOwner)
{
case "Ms": whereas I am used to case "Ms","ModelSpace" etc
I spent more than a day trying to get an arc to do what I wanted. And even after doing it in vba then transferring into C# again it took an hour to see what I had done wrong.
It is quite a shocker to get points in Ucs. Anyway I did get to pick 3 points anywhere and draw an arc through those points and since the arc is in any plane that took quite a few functions to be converted to achieve. I then realised that adding that to an arc jig was stupid so the arc jig is really quite simple. Damn it's good to whine. Anyway I'm still working through adding ents. Polylines are next and that's going to take a bit of work. At least the math is all there for the taking (although I still need to test it all out. Part of trying to find the problem with the Arcs , involved comparing CrossProduct w/ my CrossProduct function.), the curve class is awesome.
After the ents, I may concentrate on the parts that C# does that vba can't. Wipeout is a start then some viewport action. I figure I have about a year to convert the vba before vista hits our shop, so I'm taking it a bit at a time.
Without the support on this site I would definately given up a while a go. Perhaps in a couple of months I'll see a return that is better than the merely having to learn it as vba is dying.It really takes a long time to check your code.
