Linked by Thom Holwerda on Mon 13th Dec 2010 19:27 UTC, submitted by lemur2
Thread beginning with comment 453506
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2010-12-14
Agreed - all this means is that those applications rely on an API that falls outside of Microsoft's assurances around patent infringement.
I'll bite. No it doesn't. All it actually means is that the text "using System.Linq" has appeared in the source file. It's entirely possible that nothing in that particular code file actually uses any member from that namespace. Useless 'using' statements tend to crop up a lot because there are no ill effects from having them and it is a pain in the ass to remove them without using some kind of automated tool. Who wants to wander through hundreds of code files removing using statements one after another and checking to see if the build fails?