dasBlonde - New Article on 15 Seconds - 10 Steps to Versioning and Deployment Success

Saturday, November 13, 2004

« New Localization Content | Main | VS Connections - Versioning and Deployme... »

New Article on 15 Seconds - 10 Steps to Versioning and Deployment Success

I recently wrote up an article that discusses best practices for versioning and deployment of .NET components. In the article, and in my sessions on this subject I emphasize code access security, running with least privilege, versioning issues, publisher policies and more. Check it out here: http://www.15seconds.com/Issue/041103.htm

On a related resource page, you can find the tutorial I wrote for the code sample: http://www.dotnetdashboard.net/sessions/versiondeploy.aspx

This month, you can expect an article explaining .NET runtime security and sandboxing.

Cheers!

Sunday, November 14, 2004 3:40:04 PM (GMT Standard Time, UTC+00:00)

Nice article, Michelle! I will be very interested in your article on security and sandboxing (which I have been writing about lately as well).

Robert Hurlbut

Tuesday, December 14, 2004 7:27:36 PM (GMT Standard Time, UTC+00:00)

I red your article on 15seconds and it helped me a lot with some decisions i had to take about re-deploying new versions of shared assemblies for my current client. Especially about redirecting multiple versions of an old assembly.

Well, it saved my day!

At one point in your article, you wrote : "In future versions of .NET, strong names will become a requirement. Get used to it!"

Could you send me the link where you got this information from ? I often have to preach for the good of strong name, this information would be really helpfull in my daily fight for new technology. ;-)

Thanks!

Dan

Monday, December 20, 2004 7:09:14 PM (GMT Standard Time, UTC+00:00)

There are discussion about requiring strong names for the Oras/Longhorn timeframe, and I provide one written reference to this in my article (see blog entry at the end). Although you can't rely on this as guaranteed requirement yet, it is still generally considered a best practice since there is absolutely no versioning, runtime security checks or security policy control for assemblies without a strong name.

Michele Leroux Bustamante

Name
E-mail	(will show your gravatar icon)
Home page

	Remember Me
Comment (HTML not allowed)