Pros and Cons of using .NET
-
Hi all, I was wondering if anyone out there could point me towards a good business-focussed discussion of the benefits and pitfalls of developing Windows software, particularly database-centric client/server and n-tier systems, in .NET. Bit of a wish, but any suggestion appreciated.
-
Hi all, I was wondering if anyone out there could point me towards a good business-focussed discussion of the benefits and pitfalls of developing Windows software, particularly database-centric client/server and n-tier systems, in .NET. Bit of a wish, but any suggestion appreciated.
Dunno of any specific discussions apart from those on CP. From what angle are you asking ? Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002 -
Dunno of any specific discussions apart from those on CP. From what angle are you asking ? Christian No offense, but I don't really want to encourage the creation of another VB developer. - Larry Antram 22 Oct 2002
C# will attract all comers, where VB is for IT Journalists and managers - Michael P Butler 05-12-2002
Again, you can screw up a C/C++ program just as easily as a VB program. OK, maybe not as easily, but it's certainly doable. - Jamie Nordmeyer - 15-Nov-2002Hiya Christian, I work at a company that builds a Windows POS product. To date we've used MFC and in the Dark Ages Borland OWL, but now that .NET has appeared on the scene it appears to be a good candidate for the development of some new and significantly large features we're taking on, not least because of the speed of developing user interfaces, easy memory management, and because we're looking for an alternative database access technology to the outdated BDE, making ADO.NET an attractive candidate. As we move towards an enterprise solution that includes non-POS clients we're considering a more tiered architecture with one or more business object layers. We've done a bit of this with COM already, but also want to consider using .NET objects because of the relative ease of development and apparently flatter learning curve for new developers. Our other choices for moving forward are to stick with MFC, COM/DCOM and probably OLEDB, all good technologies but falling steadily behind the main MS push, I feel. Anyhow, I've got a week to present a summary analysis of the potential use of .NET technologies in our products... When it comes to supporting a decision either way, it looks like my task is a bit harder than I first thought :~ Thanks for the reply (ps, do I remember rightly that you're also hangin' here in sunny Brisbane?)
-
Hiya Christian, I work at a company that builds a Windows POS product. To date we've used MFC and in the Dark Ages Borland OWL, but now that .NET has appeared on the scene it appears to be a good candidate for the development of some new and significantly large features we're taking on, not least because of the speed of developing user interfaces, easy memory management, and because we're looking for an alternative database access technology to the outdated BDE, making ADO.NET an attractive candidate. As we move towards an enterprise solution that includes non-POS clients we're considering a more tiered architecture with one or more business object layers. We've done a bit of this with COM already, but also want to consider using .NET objects because of the relative ease of development and apparently flatter learning curve for new developers. Our other choices for moving forward are to stick with MFC, COM/DCOM and probably OLEDB, all good technologies but falling steadily behind the main MS push, I feel. Anyhow, I've got a week to present a summary analysis of the potential use of .NET technologies in our products... When it comes to supporting a decision either way, it looks like my task is a bit harder than I first thought :~ Thanks for the reply (ps, do I remember rightly that you're also hangin' here in sunny Brisbane?)
Choosing .NET is a matter of application need you have. I would choose .NET in the long run if the application does not really need high performance (GC is a show stopper, lot of memory overhead), and has a strong web exposure (ASP.NET). Choosing .NET is not a matter of underlying technologies such as COM, etc. since .NET supports them as well (both ways).
-
Hi all, I was wondering if anyone out there could point me towards a good business-focussed discussion of the benefits and pitfalls of developing Windows software, particularly database-centric client/server and n-tier systems, in .NET. Bit of a wish, but any suggestion appreciated.
I can tell you from experience use .NET, if you don't want to take my word for it, go to www.microsoft.com/net[^] you'll find plenty of info.
R.Bischoff | C++ .NET, Kommst du mit?