Just a quick message to anyone who happens to be reading
this that I'm still around. I've just been quite busy recently and have not had
the time to really write anything profound. There's lots of stuff I'd like to
write about, but it's not very clear if they're "permitted" topics.
We have a bit of a problem with running .NET code against
Excel in non-EN-US locales at the moment, and it's been eating up a lot of my
time. There's a KB
article about the problem but unfortunately the solution it provides is
incomplete (the fact that I know the Q# off the top of my head is scary...).
Basically, VBA always talks to COM objects in a US context, whereas .NET always
talks to COM objects using the current user locale. This causes problems when
the installed Office version doesn't match the Windows Regional Settings, or
when developer's expectations about the behaviour of date strings, etc. is
broken. There are some ways that developers can work around these problems, but
we're trying to investigate alternate solutions.
Two interesting things I learned last week: