Linked by Thom Holwerda on Fri 24th Feb 2012 17:53 UTC
Thread beginning with comment 508821
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 06/13/13 14:35 UTC
Linked by Thom Holwerda on 06/11/13 17:07 UTC
Linked by Thom Holwerda on 06/10/13 23:13 UTC
Linked by Thom Holwerda on 06/08/13 14:57 UTC
Linked by Thom Holwerda on 06/07/13 11:40 UTC
Linked by Thom Holwerda on 06/04/13 12:45 UTC
Linked by nfeske on 05/31/13 10:12 UTC
Linked by Thom Holwerda on 05/29/13 16:59 UTC
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
More Features »
Sponsored Links



Member since:
2006-05-30
Errr... Sorry, that's FUD. Do you know how we deploy our .net apps? Simple, we copy the contents of the release folder to the target machines. Or we use the installer project. Either gives the same result. We argent .Net 3.5 and As that is part of Win 7, you know what? Most already have it. Do you know what? The runtime is generally installed on most Vista and SP3 XP boxes too.
Now, let's talk Delphi.... COM objects, DLL dependencies, database engines (client or c/s.) I've never seen a corporate Delphi app that was a "copy and go". Not that I've worked on, and I did Delphi development full time professionally from June 1998 till early 2006 then on and off till mid 2007 when I went full time .Net. I worked on all kinds of app, did some contracting, did Media, Financial, Defence, Logistics and some general Security including RFID integration, Mobile data (win mobile with in car black boxes) and some cool stuff with bespoke object based data storage (think, Object instances streamed in to a bespoke data store, fully indexed and fully networked with multiple user access.) All I can think is that your apps are quite trivial?