To view parent comment, click here.
To read all comments associated with this story, please click here.
Duckie said:
> I have never had, seen anyone or read about anyone having issues with using different versions of assemblies, or the framework itself. If there was problems, it was because of not following instructions.
Ok, I'll disclose that I'm a Java guy (both Rich Client and J2EE), but have written C# apps in the past. I have a friend who worked on a $NZ20 million (around US$15 millions) project for the New Zealand government that failed because they had trouble with getting all their assemblies built properly across the development team. They were a very experienced and dedicated team. Perhaps the project was too ambitious but "assembly hell" was a real issue for them. In contrast, we take a slightly different approach with our Java apps and while you have to be very mindful about different versions of JARS using the Java classloader, you can actually avoid some of the problems the .NET guys were confronted with. In very large applications .NET still has scalability problems.






Member since:
2006-04-10
None of your arguments "stick". I have used .net in a couple of years since 1.1, and i am still using it, both for win and web-developement.
I have never had, seen anyone or read about anyone having issues with using different versions of assemblies, or the framework itself. If there was problems, it was because of not following instructions.
I find it pretty funny you say i read to much marketing, and then afterwards you point me to a ancient marketing-slide. I am pretty sure that slide is insanely old, and it is _not_ correct. Avalon runs fine on xp.
Come with some sources for your points