DefaultInstances
January 21, 2005
Because you can’t see my face, I’ll narate – disgust and disbelief. Having said that I can see some instances in code conversion where this could bail some people out. But you’d want to refactor your code pretty quickly me thinks.
January 23, 2005 at 12:00 am
Hi Mitch,
The big question is why it’s being introduced at all when almost everyone posting is saying “please, please, please don’t do it”. No-one seems to be answering the question “who wants it in the first place apart from Paul?”.
Many of us have been “discussing” this with the group internally for many months.
Regards,
Greg
January 24, 2005 at 12:00 am
Hi Greg,
You’re right. It makes me suspect that it is an internal driver – and something to do with supporting code conversion tasks, which is far from a straight-forward task at the moment.
January 29, 2005 at 12:00 am
Uh… I didn’t know VB could go any further down hill. I now basically refuse to work on any VB based projects. They now go in the same boat as ASP, or VB6 project – in need of a rewrite, development can not continue.
I always knew that there’d be an ever-increasing number of reasons to support my move to C# almost 3 years ago.
January 29, 2005 at 12:00 am
Hi Tatham,
I haven’t quite written off VB yet but I enjoy C# a bit more at the moment. I would have thought that Adam would dictate what language you work in