Just my $0.02 as I have done this a couple of time - plus I wrote some of the
Mono.Security.dll.
* Use properties
.NET developers find it very strange if simple attribute assignment should be handled
through method calls. If there are additional checks/functionality involved with the
assignment put that in the set{} method.
Of course there is a fine line when something should be moved a method - but as a general
rule I found that properties are used when you operates on data that keeps the state of
the object - where methods are used when you execute functionality.
* Use capital on the first letter for properties/methods.
Yep - this is different from Java ;) Small note, .NET doesn't (typically) expose any
properties/methods that starts with Get/Set...
* Mono tool chain works great
I used Mono + NAnt + NDoc + NUnit for my work - and it worked great. I basically built a
development environment as I would have done when coding Java. Of course the work I did on
Mono.Security.dll was done on their branch following their rules. Deployment was .dll
files that were then used by .NET developers using the M$ environment.
(And yes, the development was done because 1) M$ security dll didn't contain the
needed functionality 2) license issues 3) support multi-platform development)
HTH - feel free to ask :)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4206558#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...