Have Geek Brain

Native C ++ or .NET for business applications?

Here's the deal: I'm planning a midsize business application that should definitely support Win2k. AFAIK, the official .NET support for Win2k was revised a while ago (IIRC, it settled on version 2.0).

I have now written (many years ago) C ++ libraries that allow me to accomplish the end result (ie, finish this project) as quickly as if I were writing this application using the .NET Framework - so the "advantage ".NET RAD is almost canceled.

I'm sure a lot of people here are working with business applications that need to support older operating systems. So, given my library situation, what's the advantage for me to use .NET over native C ++ and vice versa? I just don't know which one is right for the job because it seems like I can use too. Again, there is a problem with maintaining the frame to work with ...

I will gladly add additional information if required.

+1


source to share


6 answers


The latest version of .NET running on Windows 2000 is .NET 2.0 SP2. It includes the functionality required by System.Core.dll (which is part of .NET 3.5).

Answer: YES, you can use .NET 3.5 SP1 under Windows 2000 if you are not going to use .NET 3.0 libraries (WCF, WF, WPF, CardSpace). But you have LINQ, LINQ to XML, LINQ to SQL.

The only thing you need to do is deploy the three main .NET 3.5 SP1 files:



  • System.Core.dll
  • System.Xml.Linq.dll (LINQ to XML)
  • System.Data.Linq.dll (LINQ to SQL)

Disadvantages of this method (read carefully):

  • It is not possible to authorize or deny the license agreement (end user license agreement).
  • This scenario is not supported by Microsoft.
+1


source


I would see if Mono ( mono-project ) works . that is, it works on win2k - if it allows you to port your application to MS.NET and later OS versions, if it comes up later in the project. Any .NET will be easier than C ++ IMHO :)



0


source


The biggest difference is that you (or your boss) are more likely to find developers to support your .NET code after moving on to other things.

C ++ has the advantage of giving you stability - although that might not be what you want. :)

0


source


I think, given your situation, it comes down to making you feel more comfortable in writing. If C ++ is your preferred language, do it. This will help you get into the code and make it easier to finish.

I will also take care to accommodate the future. If the Win2K requirement falls, you may need to rewrite if you wrote in C ++. This may not be the case. Just keep this in mind when you decide how to proceed.

0


source


You can develop with .NET, but set compiler options to target the .NET 2.0 framework. If the OS will be updated in the near (or distant) future, you can update your targeting program for the 3.5 framework. I would take this route as it makes it easier to support the future for others.

0


source


Have you considered Delphi? You can download Turbo Delphi for free, and you can easily write code targeting Windows 2000. With Delphi, you get a great RAD (probably the best you'll find in C ++ ... if you don't use C ++ Builder).

Delphi generates native code and requires no runtime.

Of course the downside is that you don't know Delphi (which is Object-Pascal), you need to become familiar with the new language. However, if you know C ++, you will feel right at home in Delphi in no time.

0


source






More articles:


All Articles