Is the .NET Framework a successful platform?
-
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?
There are loads. See elsewhere in this thread. Many are business applications though, so wouldn't be accessible to you. For a big Microsoft app. see BizTalk.
Kevin
-
John C wrote:
This kind of talk made sense 6 years ago but it's a done deal now.
Exactly. Even me found the time to learn parts of the large platform! I was one of those not interested in .net and finally found out it was because I was able to quickly code in what I knew but it took long to learn and code in .net. Fortunately I found some free time(it actually took months) and worked hard to learn both web based programming in asp.net and some basic C# skills. I feel much better now. However probably C# will be replaced by something new quickly, but I learned that in order to make a transition easier I shall start from day one when a good technology is being introduced. I remember I had discussions here and one of them, if I remember correctly, was with you who pushed me to learn it. Thank you. :)
"In the end it's a little boy expressing himself." Yanni
Hamed Mosavi wrote:
However probably C# will be replaced by something new quickly
I don't think so. It will be around for some considerable time.
Kevin
-
.jpg wrote:
not having deterministic deallocation is a big downside for me.
Why? (BTW, C++/CLI has deterministic finalization.)
.jpg wrote:
anyone know of any big app written in .NET?
.NET is used heavily in industry, so I assume you mean productised apps? You will find that a lot of Microsoft's newer applications are written substantially in .NET. BizTalk is a large application written in 100% C# apparently.
Kevin
-
Hamed Mosavi wrote:
However probably C# will be replaced by something new quickly
I don't think so. It will be around for some considerable time.
Kevin
Actually I don't care much about programming languages any longer. This is what I learned. Several years ago I started C++ and then MFC and loved them. Later on I fought years to believe MFC will be alive and still more important and useful than .net. I believe I found my problem. I had a goal which was to create best Windows applications in the world with MFC! I know you're laughing. :-D The problem was the MFC at the end. Now my goal is to: "Create most useful applications." Windows, c++, c#, etc. who cares. PL is important to me but not my goal definitely.
"In the end it's a little boy expressing himself." Yanni
-
Actually I don't care much about programming languages any longer. This is what I learned. Several years ago I started C++ and then MFC and loved them. Later on I fought years to believe MFC will be alive and still more important and useful than .net. I believe I found my problem. I had a goal which was to create best Windows applications in the world with MFC! I know you're laughing. :-D The problem was the MFC at the end. Now my goal is to: "Create most useful applications." Windows, c++, c#, etc. who cares. PL is important to me but not my goal definitely.
"In the end it's a little boy expressing himself." Yanni
Hamed Mosavi wrote:
Several years ago I started C++ and then MFC
Same here.
Hamed Mosavi wrote:
"Create most useful applications." Windows, c++, c#, etc. who cares. PL is important to me but not my goal definitely.
I just try to keep up to date with whatever is the latest stuff coming out of Microsoft - whether I like it or not. There's no choice if I want to stay employed in the Microsoft world. I could try and change to the non-MS world but unfortunately that would be equivalent to being a programmer with zero commercial experience again. It shouldn't be like that but that's the way the IT industry works. Even having just .NET 2.0 will before long render me unemployable in the MS world. So I'm desperately trying to get someone to give me a .NET 3.x contract! :) (I'm currently out of contract.)
Kevin
-
Hamed Mosavi wrote:
Several years ago I started C++ and then MFC
Same here.
Hamed Mosavi wrote:
"Create most useful applications." Windows, c++, c#, etc. who cares. PL is important to me but not my goal definitely.
I just try to keep up to date with whatever is the latest stuff coming out of Microsoft - whether I like it or not. There's no choice if I want to stay employed in the Microsoft world. I could try and change to the non-MS world but unfortunately that would be equivalent to being a programmer with zero commercial experience again. It shouldn't be like that but that's the way the IT industry works. Even having just .NET 2.0 will before long render me unemployable in the MS world. So I'm desperately trying to get someone to give me a .NET 3.x contract! :) (I'm currently out of contract.)
Kevin
Kevin McFarlane wrote:
I'm currently out of contract.
Same here. Finished last job a month ago feeling good to have some free time to read a few books and restart working on my own project until next contract. You'll certainly sign a good contract soon. Your profile is great. I too take a look at new technologies whenever I find free time. However not a lot of free time. We have to work a lot here to make a living.
"In the end it's a little boy expressing himself." Yanni
-
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:
not having deterministic deallocation is a big downside for me.
Why? (BTW, C++/CLI has deterministic finalization.)
.jpg wrote:
anyone know of any big app written in .NET?
.NET is used heavily in industry, so I assume you mean productised apps? You will find that a lot of Microsoft's newer applications are written substantially in .NET. BizTalk is a large application written in 100% C# apparently.
Kevin
-
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?
Whe have a huge application developed all in C#. Is a SFA solution, that has a Windows Mobile app (.Net Compact Framework 3.5 SP 1), a Desktop administration app (.Net Framework 3.5 SP 1), and a Web Service (.Net Framework 3.5 SP 1). It's operating with more than 100 devices (including pocket pc's and desktop pc's). .Net is simply great :D (PS: sorry about my bad english, I'm from Argentina) fisa (fisa.net@hotmail.com)
-
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?
I can think of at least one "enterprise grade" application that uses .NET - Laserfiche. The Laserfiche Scanning application is entirely written in .NET, the Workflow module is written using .NET WF, and I believe the new version of the Laserfiche Client is also written in .NET (but don't quote me on that one). Laserfiche has many millions a year in revenue, and it has 25,000 installations worldwide. It isn't cheap either - a few of the installations I did integrations for were 6 figures (without the integration), and I found most average around 30-50k. Laserfiche Company Info Page[^]
modified on Wednesday, October 8, 2008 9:02 AM
-
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 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?)
-
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?
What is the definition of success? Big apps written in .NET. They are out there. But if you're working deep in an enterprise environment, like many of us are, you're more likely working with product lines that began long before C# was around. So that environment isn't a good sample of the industry. I think it's undeniable that .NET is a "successful platform". The TIOBE survey has had it in the top 10 for quite a while now. And if MS' analysis is to be believed, half of the world's professional developers are working on .NET. Even if what they really mean is half of the world's Windows developers, that still smells like success to me.
-
For commercial products, there's a CRM product called Ascent (V.2) which is written in .Net. I used to work somewhere that had it [a major international EMC reseller], writing custom additions. There are LOTS of .Net backed websites/apps. (I note that this page itself has an ."aspx" extension...) There is plenty of C#/.Net work going on in UK-based Investment banking, Insurance etc. I also worked on a 2nd generation version of commercial Photo Kiosk software (used widely in US and UK, you know where you stick your camera card in and get prints/books/mugs/Tshirts/teddies) that was entirely .Net. Dunno if it ever got released as the company got taken over just about as it it was finished.
In the same vein, Hyland OnBase is moving to .NET as well.
-
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.