4 ms·

Respectfully, that's nonsense. I don't even work in their department. I've been online for 20+ years, blogging for like 12 years and I've worked at MS for 6. T

Respectfully, that's nonsense. I don't even work in their department. I've been online for 20+ years, blogging for like 12 years and I've worked at MS for 6. The blog is a blog. This post is just a post. I get in trouble for blogging a few times a year, and that suits me just fine. It's just a job.

yuhong 13y ago
OT, but on the .NET Framework versioning, the support lifecycle of 2.0/3.0/3.5 is a mess that needs to be cleaned up: http://support.microsoft.com/kb/2696944 http://support.microsoft.com/kb/2696944 The lifecycle policy of 3.5 SP1 should also be applied to 3.0 SP2 and 2.0 SP2, for example.
- shanselman 13y ago
  Thanks, I've sent this note to the Lifecycle guy and I'll get you a response.
- jamshedd 13y ago
  Thanks for the feedback Yuhong. As you correctly pointed out .NET 2.0 SP2 and .NET 3.0 SP2 are sub-components of .NET 3.5 SP1 so it makes sense to have these on the same lifecycle. The good news is that this is already the case, the Knowledge Base Article 2696944 clarifies that when .NET 3.5 SP1 is installed the same lifecycle will apply to .NET 2.0 SP2 and 3.0 SP2 too. This is the relevant snippet from that KB article - ...snip... However, Microsoft will provide support for the .NET Framework 2.0 and .NET Framework 3.0 components for customers who install the .NET Framework 3.5 for as long as the .NET Framework 3.5 remains in support. ...snip... Thanks, Jamshed Program Manager, .NET Framework Fundamentals team
  - yuhong 13y ago
    But why 2.0 SP2 and 3.0 SP2 has a different lifecycle if 3.5 SP1 is installed vs if it is not installed?
taspeotis 13y ago
OT, but do you think you could point me in the direction of whoever's responsible for WPL/AntiXSS? It's been broken for ages [1] [2]. There seem to be no reliable HTML sanitization library for .NET right now. It looks like the best I could do is to copy and paste a bunch of code and hope that it works [3]. [1] http://wpl.codeplex.com/releases/view/80289#ReviewsAnchor http://wpl.codeplex.com/releases/view/80289#ReviewsAnchor [2] http://wpl.codeplex.com/workitem/17246 http://wpl.codeplex.com/workitem/17246 [3] http://eksith.wordpress.com/2011/06/14/whitelist-santize-htmlagilitypack/ http://eksith.wordpress.com/2011/06/14/whitelist-santize-htm...
- deleted 13y ago
  [deleted]
- shanselman 13y ago
  Let me ask around. It's handled by a group that isn't ASP.NET.
  - taspeotis 13y ago
    Any effort is appreciated. Thank you.
tinco 13y ago
Thank you for your blog, the posts are always entertaining and informative :)
test-it 13y ago
Wow, Mr Hanselman himself. I'm a big fan - listen to all episodes of your podcast. Just watched a few presentations from this year Build. You should really give other MS employees a course on public speaking - they are sooo slow and boring compared to you ;-)
- scrabble 13y ago
  He's got a course on public speaking available on TekPub.

yuhong 13y ago

OT, but on the .NET Framework versioning, the support lifecycle of 2.0/3.0/3.5 is a mess that needs to be cleaned up: http://support.microsoft.com/kb/2696944 http://support.microsoft.com/kb/2696944 The lifecycle policy of 3.5 SP1 should also be applied to 3.0 SP2 and 2.0 SP2, for example.

shanselman 13y ago
Thanks, I've sent this note to the Lifecycle guy and I'll get you a response.
jamshedd 13y ago
Thanks for the feedback Yuhong. As you correctly pointed out .NET 2.0 SP2 and .NET 3.0 SP2 are sub-components of .NET 3.5 SP1 so it makes sense to have these on the same lifecycle. The good news is that this is already the case, the Knowledge Base Article 2696944 clarifies that when .NET 3.5 SP1 is installed the same lifecycle will apply to .NET 2.0 SP2 and 3.0 SP2 too. This is the relevant snippet from that KB article - ...snip... However, Microsoft will provide support for the .NET Framework 2.0 and .NET Framework 3.0 components for customers who install the .NET Framework 3.5 for as long as the .NET Framework 3.5 remains in support. ...snip... Thanks, Jamshed Program Manager, .NET Framework Fundamentals team
- yuhong 13y ago
  But why 2.0 SP2 and 3.0 SP2 has a different lifecycle if 3.5 SP1 is installed vs if it is not installed?

taspeotis 13y ago

OT, but do you think you could point me in the direction of whoever's responsible for WPL/AntiXSS? It's been broken for ages [1] [2]. There seem to be no reliable HTML sanitization library for .NET right now. It looks like the best I could do is to copy and paste a bunch of code and hope that it works [3]. [1] http://wpl.codeplex.com/releases/view/80289#ReviewsAnchor http://wpl.codeplex.com/releases/view/80289#ReviewsAnchor [2] http://wpl.codeplex.com/workitem/17246 http://wpl.codeplex.com/workitem/17246 [3] http://eksith.wordpress.com/2011/06/14/whitelist-santize-htmlagilitypack/ http://eksith.wordpress.com/2011/06/14/whitelist-santize-htm...

deleted 13y ago
[deleted]
shanselman 13y ago
Let me ask around. It's handled by a group that isn't ASP.NET.
- taspeotis 13y ago
  Any effort is appreciated. Thank you.

tinco 13y ago

Thank you for your blog, the posts are always entertaining and informative :)

test-it 13y ago

Wow, Mr Hanselman himself. I'm a big fan - listen to all episodes of your podcast. Just watched a few presentations from this year Build. You should really give other MS employees a course on public speaking - they are sooo slow and boring compared to you ;-)

scrabble 13y ago
He's got a course on public speaking available on TekPub.