VB.NET Thread Titles

It seems that I am not the only one that thinks this (see posts #9 and #10 in here: http://www.vbforums.com/showthread.php?p=3558501)

Basically, with Visual Studio 2008 being able to target different versions of the framework it seems like it might be a better idea to have the threads in the VB.NET section marked with the .NET framework version rather than the VS version because the .NET framework version has much more effect on the code being posted in these forums (as that thread demonstrates).
I appreciate this might not be a quick or straight forward change but maybe it could be looked into?

Cheers
Chris

There is no good, easy solution to this. Many people don't know what version of .NET they are using, but they do know which version of VS they are using. To some extent, we have to rely on the poster to state the relevant information in their post/question. For example, I'd expect someone using VS 2008 to be using 3.5 unless they indicate otherwise.

We could switch to using the .NET Framework, but I think a lot of people would guess and possibly be wrong.....

Based on the amount of people who think that VB2008 fits in "VB6 and earlier", I suspect you are right.

I don't know if this would be any good, but we could potentially add extra options for the "non-standard" frameworks, eg: VB2008/2.0

Everyone should let the moderators know what make sense or what they would like to see. The moderators can then propose a course of action to our forum manager (Joe). If it has no negative impact on the forum, then I'm sure Joe will make it happen.

Brad!

I think leaving it as the VS version should be sufficient. If some one is using VS2008, odds are they are targeting 3.5. If they aren't, then they know enough to know how to change it, which means, they are not new to the game, and will hopefully know that they need to indicate what version of the FW they are targeting.

Biggest problem I've seen is the poster not indicating thier version of VB in the first place, or as Si noted, thinking that VB2008 belongs in the VB6 section some how.

-tg

There is no fool proof solution to this. There will always be misleading or incorrect thread title posting. All we can do is educate to help reduce it to a certain point.

If when we read/answer we see they are using a version of VS that supports multiple framework targeting then we should ask the question of what framework they are targeting if its not indicated.

I typically show for both VS 2005 and VS 2008. First I'll show the VS 2005 answer which'll work in both anyways, then I'll show the much easier way and note that it's only for VS 2008.

Then if the VS 2008 method requires something in the 3.0 or 3.5 frameworks, I'll also note that too. If the OP has no clue how to do it, then it's up to them to learn, but either way they have something that'll work anyways.