By SkySigal on 9/6/2008 4:06 PM

I'm starting to agree with this recommendation (wish I had known about it a long time ago):

<<<

It is an annoying process to add security after the fact, the best
recommendation I've seen is to develop as a least permission user (VS
Debugger user etc) or to remove all default permissions with [assembly:
PermissionSet(SecurityAction.RequestOptional, Unrestricted=false)] up
front.
As you add functionality and it throws security exceptions run you can
research what permissions each object needs.

>>>

Src: http://www.secnewsgroups.net/group/microsoft.public.dotnet.security/topic11068.aspx

By SkySigal on 9/3/2008 4:39 AM

"At this year’s TechEd conference, Juval Löwy was interviewed on the principle of interface-based programming vs coding to abstract classes.  Not many .NET developers know the difference between an interface and an abstract class, and even less when and why to prefer one to the other (hhmmm…sounds to me like a good post to write soon).  If you didn’t get a chance to hear his full talk on the subject at Tech Ed 2008, I strongly suggest to invest 16 minutes today to watch this interview."

Src: Brian Di Croce

Links:

http://blog.briandicroce.com/2008/06/21/juval-lwy-on-the-importance-of-interface-based-programming-teched-2008/

By SkySigal on 9/3/2008 4:32 AM

 

"Krzysztof Cwalina has published a condensed version of the Microsoft .NET Framework Design Guidelines which he co-authored with Brad Abrams a couple of years ago.

You can find the Framework Design Guidelines Digest  here as a PDF file (9 pages long).

The document is very useful if you desire to set up a standard, practical and ubiquitous approach of programming with .NET in your own organization in no time and without much effort (the job is already done for you!)."

 

Links:

• http://blog.briandicroce.com/2008/04/09/a-cheat-sheet-on-net-framework-design-guidelines/
• Framework Design Guidelines Digest