A Simple Question: .NET or Win32

on 10.09.05, 02:33pm in software • comments (11)

Thought I would take a quick informal survey for all you software developers who read Furrygoat: Are you using .NET or Win32 for your client applications? (and as a followup: what are you planning to use in the future?)

File this under "just curious".

11 Comments

    Randy (October 9, 2005 @ 4:45 pm)

    .NET here for my own coding at home. Goes faster and is easy to work with for the stuff I work on: relatively simple applications with a bunch of third party controls.

    .NET for my stuff at work too, since my automation framework is .NET centric; also Reflection has been handy when coding for new apps that have known information.

    It fits my needs and is the best tool to use, at the moment; as always, I say the best tool for the job, rather than sticking with one or the other for the sake of the tool.

    Lou (October 9, 2005 @ 7:42 pm)

    Having worked with C# for a number of years, I have to say I really prefer good old C++. It is efficient, deterministic, debuggable.

    C# and the .net framework hide many details making it easy to get 80% of where you need to go. I’ve found that it is great for building simple apps, but for anything of scale: you are better off with C++.

    Mark Finkle (October 9, 2005 @ 8:32 pm)

    We build commercial software. It’s WIN32/C++ and will be for several more years.

    .NET is currently a nice wrapper framework around WIN32, but I can get smaller, lighter frameworks that work just as well.

    ken partridge (October 9, 2005 @ 10:19 pm)

    Win32/C++ until we can be sure that there wont need to be a huge download of .NET file to run the application.

    laurence timms (October 10, 2005 @ 1:45 am)

    .NET every time, both at work and personally. We find that the .NET approach makes ‘more sense’ to developers, and they tend to be more productive more quickly.

    You could always push the envelope with Win 32 apps, but the cost was lower maintainability, less stability on newer Windows platforms, and the worry of breaking the app with MDAC updates and the like.

    David Brabant (October 10, 2005 @ 3:51 am)

    We use both. Gradually migrating the existing code (some part of it being close to 10 years old …) towards .NET and the managed world (meaning we are also heavily using managed C++ to avoid complete code rewrite).

    thomas woelfer (October 10, 2005 @ 6:00 am)

    .Net and .Net

    WM_FYI
    thomas woelfer

    Sencer (October 10, 2005 @ 8:01 am)

    Both .NET and Win32, but I have to say getting serious with .net is a lot more work than you would anticipate and debugging is a really BIG pain.

    Rick Lobrecht (October 10, 2005 @ 8:49 am)

    We’re using both. We have tons of C++ and VB6 code that just isn’t going away any time soon. We have a few new apps that are C#. I’ve been doing C# exclusively for a year, but there are a bunch of VB6 DLLs which I maintain, and I’m sure one of them will need a fix eventually.

    bg (October 11, 2005 @ 6:05 am)

    our comercial software is mostly vb6/mfc6, and we are adding to it from .net - mainly controls embedded in mfc as activex controls.

    The future for us is probably java. I doubt we will use the new version vs due out in novemeber.

    Chris Hynes (October 11, 2005 @ 9:27 am)

    .NET all the way. Prodictivity is phenominal, and with P/Invoke and unsafe code you can do pretty much anything you need to do in Win32 if necessary. A managed c++ wrapper is the last line of fallback…

Sorry, the comment form is closed at this time.