From: Oren Ben-K. <or...@ri...> - 2002-12-06 19:17:40
|
Nathan Sharfi wrote: > in 3.3.5: > "For languages such as Java and C#, all type names based on reverse DNS > strings are > globally unique." > > true, but this is fairly irrelevant when it comes to C#. Oops. We'll have to fix the wording. Thanks. > the naming convention for library developers is > CompanyName.TechnologyName, ... > However, this doesn't provide a guaranteed unique name if more than one > YAML project > shows up in SourceForge (NAnt, at least at one time, used the namespace > SourceForge.Nant). Well, another project would use the namespace SourceForge.Whatever so there would be no collision. Presumanly there's little risk of collision in the company name level... As usual, Microsoft have came second to the scene, looked at the existing thought-out solution and how it avoids serious problems, and then went on to create their own solution that does _not_ solve these problems. Welcome to the new DLL hell :-( Have fun, Oren Ben-Kiki |
From: <rob...@ya...> - 2002-12-06 20:14:51
|
hi oren, > As usual, Microsoft have came second to the scene, looked at the existing > thought-out solution and how it avoids serious problems, and then went on to > create their own solution that does _not_ solve these problems. Welcome to > the new DLL hell :-( as someone who has done some programming in .net and written two articles about deployment and configuration in .net i happen to disagree. ;-) the way microsoft designed their deployment strategies in .net is exactly to prevent dll-hell. it is very well thought out concept for a system that is constantly upgraded with different versions and different localizations of the same component (aka windows). you really, really have to work for it in order to break it. and i crave to see something similar in java as i am in constant fight with my ejb servers to have the right version of my jars. jar-hell is a very common problem today in java. as for the reverse dns-string issue - this is only by convention (same as in java) nobody forbids you to use your very own naming convention - i use the java ones for c# classes. - the namespace(s) in a component are of no relevance for binding a class as it gets bound by the "strong name" of a component first and only then by the fqn. ciao robertj ------------------------------------------------------------ Robert Kuzelj Gaissacherstrasse 7 email: rob...@ya... 81371 Muenchen tel: 0177/5302230 the trinity of desirables of (software) architecture: Firmitas, Utilitas, Venustas (marcus vitruvius 20 BC) strength, utility, beauty |