"Single executable that doesn't require installation." Written in .Net 3.5. Once upon a time, an app like this would have been written in Delphi, because it would have been "the" go-to small-app development environment. Embarcadero really needs to work on perception and knowledge of Delphi in the wider developer environment. IMO (and I haven't asked them) it's quite possible the company, porting their very popular Mac app to Windows, have never even heard of Delphi.

"Single executable that doesn't require installation."  Written in .Net 3.5. Once upon a time, an app like this would have been written in Delphi, because it would have been "the" go-to small-app development environment. Embarcadero really needs to work on perception and knowledge of Delphi in the wider developer environment. IMO (and I haven't asked them) it's quite possible the company, porting their very popular Mac app to Windows, have never even heard of Delphi.

http://calca.io/store/calca-for-windows

If you've never tried Calca, by the way, give it a go. I have the Mac version installed, not Windows, but the idea is fantastic: a Markdown-formatted editor which includes a calculator allowing natural language variables, so you can write down (advanced!) math in your text document and it will solve it for you on the fly. I wish I had thought of it!
http://calca.io/store/calca-for-windows

Comments

  1. David Millington If that is the case about the single executable I would use Delphi to do it on a single form, my executable is a single file, I can generate a report using Fast Reports, use my TMS Components for visual and stay away from .NET which is horrible, as it was stated before, one MS update and your executable has a possibility of not working, have seen that even with a major company (Carbonite, Turbo Tax, etc)

    If I am working for any client within a complex that wants Visual Studio then I do not have a choice but these types of companies do not upgrade their machines that easily.

    ReplyDelete
  2. Richard Baroniunas Most of the time, the upgrade is made automatically... Windows Update sometimes consider that the .Net framework is part of the OS, so the upgrade is part of the mandatory security updates... And most IT would include those by default... Killing the .Net apps without wanting to...

    ReplyDelete
  3. A. Bouchez In most production environments no WIndows Updates or .NET updates are allowed unless they have been approved by a QA department. 

    In a small shop environment, they do not have restrictions such as stopping Windows Updates or .NET Updates from happening nor do they have a IT department.

    I have seen Windows Updates screw up SQL Servers and .NET updates stop other applications from running.  Best advice is to make sure you have backup plan in the event the update messes up a machine.

    ReplyDelete

Post a Comment