It looks to me you submitted to the wrong place. No one was interested in the topic. They were only interested in converting you to a dual coder.

I myself don't care which language samples are in, but you have a very valid point as far as toolkits go.

I think Microsoft should be releasing them in both languages at the same time, but I can see why you would be concerned if the language your company is building in gets put on the back burner.

We are coding in C#. So far Microsoft has been releasing the toolkits we are using in C#. Hopefully that continues.

Thanks for the feedback Peter.

It was a weird thread/forum. I don't know why everyone is dual code oriented and felt the need to preach it, but 1/3 of my .NET career has been using VB.NET. So the dual code speeches were not needed. They seem to be on the Rockford Lhotka bus. I know to stay away from them now.

The toolkits are my main concern also. We are using the CAB, EL 2.0, and the GAT on our project but would not be if they had only been released in VB.NET at this point. I am currently consulting in a C# shop, so they only consider C# toolkits. They also only read C# examples. They have been a C# shop from the beginning and are not interested in anything VB.NET, including samples. We are also using the Smart Client Baseline Architecture Toolkit, but would not be if it was in VB.NET.

It appears they have re-opened the thread after closing it yesterday. I got this this morning…

Dear Tad Anderson,

Thanks you for you topic report. I have opened it again and i have escaled the topic to Microsoft.

To give you a brief update, Microsoft discussing this thread internally with our MSDN folks as well. Tom Archer is on the thread and should give a response to the forums soon.

I hope to see you again on the forum!

Kind Regards,

P.J. van de Sande

Tom Archer response to the thread (link above).