Is the .NET Framework a successful platform?
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?
Paint.NET is one of the mostly widely known and LARGE C# application with a few modules written in C++
___________________________________ Heston T. Holtmann, B.Sc.Eng., EIT. Senior Software Engineer
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?
I'm not sure what you mean by big, but I have a suite of desktop apps written in C# that handle complete oil reservoir evaluations, from geological and petrophysical models, to extensive production histories, to test modeling and simulation. The system is interactive, extensible and modular. And it runs slick as greased lightning on Vista. It may be partly due to my own limitations, but part of what made the system possible and manageable is the use of C# generics and other features of .NET. Some of my current efforts, besides extending the base system, is adding real time control and expert systems using F#. I can't imagining trying to combine and manage a project using both imperative and declarative code outside of .NET -- and,yes, I've tried. With C# and F# both using .NET, it's actually fairly manageable, at least in my preliminary tests. So, yes, I'd say that .NET is a successful platform.
The PetroNerd
Walt Fair, Jr. Comport Computing Specializing in Technical Engineering Software
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?
not having deterministic deallocation
You don't have deterministic finalization for memory, but we have it for other resources, with the using keyword. For memory, deterministic finalization is not a big deal. .net memory allocator is much faster than C++ allocator.
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?
.jpg wrote:
However, not having deterministic deallocation is a big downside for me.
You must hate Java, then.
.jpg wrote:
Besides, anyone know of any big app written in .NET?
Do large websites count? If so, there are a number of them. Since I'm too lazy to go identify them at the moment, you may feel free to vote me a 1 :)
-
I guess it depends on what you consider 'big'? SAS[^] writes their Enterprise Guide[^] product largely in .NET The dotnet rocks guys[^] are always hawking for Infusion[^] who appear to be doing large .NET project all over the world. I believe that VS 2010 will be largely .NET based. You can always implement a deterministic allocation/deallocation with .NET if you really want to (just imagine allocating a large block of memory and hanging on to it through the life of the program :-) We have lots of different frameworks, and lots of different computer languages, cause there are lots of different problems to solve. .NET works well for some of them, not so well for others ... the trick of course is figuring out before you start which is which ;-) What sort of work are you doing that can't tolerate non-deterministic deallocation? (control systems?)
grgran wrote:
You can always implement a deterministic allocation/deallocation with .NET if you really want to (just imagine allocating a large block of memory and hanging on to it through the life of the program
LOL now there's a blast from the past...We had problems with a heap management system for a particular C compiler back in the '80s...most of the time it worked, but one project just killed it because of the enormous amount of thrashing that occurred...so we did just that: a big block of memory allocated for the life of the program just for allocating fixed-size chunks for one particular problem...eventually we moved to another C compiler, but kept the specialized memory management for the entire life of that product.
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?
dot net nuke, paint.net, community server ... you name it
-
CodeProject is a web application. Yes, ASP.NET is powerful but we talk about whole platform. Can you tell me a big desktop application written with .NET?
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?
.Net is pretty successful in the enterprise. I am a working consultant and even thought I do some work on Win32 using C++, most of my clients have huge apps written using .Net. One of my clients built a very cool middleware for systems integration to communicate very different systems. I would think, having a background in C++, that .Net would not be fast enough, but it is. Its performance is great. I understand the need for deterministic deallocation, but I think having all the other advantages does make up for it. Besides, if you really need deterministic deallocation you can use C++/CLI in the parts that you need it, and do the other components in C#. They are all still in .Net.
-
I love the C# language and the .NET BCL is very well written and clean. However, not having deterministic deallocation is a big downside for me. Besides, anyone know of any big app written in .NET?