I'm not talking about general version changes (e.g., [language-v1] -> [language-v2]) but specifically between updates that are nothing but bug and performance fixes.

In particular, I'm talking about tags that have different ones per "service pack:"

(x3609) (x120)

(x708) (x26)

(x10745) (x161)

And to a lesser extent:

(x11021) (x46)

Tags also exist for Windows XP but there have been major core changes between those versions so they do not apply here.

As I understand, changes between .NET 3.5 and SP1 (also applies to ASP.NET and Visual Studio 2008 by extension) are primarily just fixes and performance improvements and there isn't much changes in how the frameworks/tools are used. The only breaking change that I know of (that is worth mentioning) is how Enumerable.Cast<T>() no longer performs conversions.

Changes between Visual Studio 2010 and SP1 are not that significant to me to warrant the distinction (or at least, I'm just not as familiar with the changes to fully understand how different they really are). I can see possible need for distinction here as there might be questions based on the additions this service pack introduced (including but not limited to Silverlight 4, HTML 5, etc.) but perhaps someone else who is more familiar with them could clarify.

If there are other core changes that I am not aware of, then please share them.

Should this distinction exist? The 307+ questions that use these tags could get more eyes on their questions without a problem IMHO. Otherwise, how often are problems about the specific changes going to come up? Not enough to deem these tags necessary IMHO.

What do you think?

  • Hmm. There are significant changes between VS 2008 RTM and SP1, and VS 2010 RTM and SP1. Specifically, there are the type of changes that cause subtle bugs and changes in behavior, which are the type of questions that get asked on SO. People who have had trouble with the service pack should probably tag their question with the appropriate version of the service pack. – Cody Gray Jul 4 '11 at 8:13

As Cody answered in his comment: yes for Visual Studio (major changes), no for .NET framework.

I instituted that change.

As for philosophy of version tags, they should generally be avoided altogether, except in the case where you have a strong and compelling reason to believe your question will only ever be relevant to one particular version of whatever the heck it is you are asking about.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .