Re: .Net packaging/wrapper application?

IMHO, I agree.

From my background in the late 80s dBase code needed a runtime and other supporting files etc to be on the machine to make dBase programs work. Along came Clipper which compiled essentially dbase code into one EXE and that one file could be put on any dos or windows computer and run from the command prompt or an icon etc. No installation or other files etc necessary. This was touted the new, much faster and better way to do things. I also worked with C and C++ back then and they also compiled to one EXE file.

Years later along comes .net and it's new and better to go back to needing something (.net framework) installed on a pc in order for you apps to run. I have to shake my head--but whatever. Perhaps I'm getting old and but what really bothers me is nobody seems to notice this--maybe the 80s was before they got into programming. Everyone seems so enamored by .net these days. I find it funny to think that in another 20 years, maybe less, .net will surely be just another memory, whatever is out then will be oh so cool and nobody will understand why anyone liked .net.

I don't mean to offend anyone with my comments, I surely appreciate the help I get here. I just wish more folks seemed to understand where I'm coming from. I might be happier with .net if I was allowed to jump to an exclusively .net world and get all into it, but I sit here tasked with writing web services in .net that sadly is to use a complicated assortment of Visual FoxPro tables as data sources.


Jeff Gaines wrote:
On 27/12/2007 in message <3d9fba1a222b18ca16f883192660@xxxxxxxxxxxxxxxxxxxx> Michael Nemtsev [MVP] wrote:

Hello jim,

ok, what's from that list cant be done with Windows Installer? :) except the point 3 the Windows Installed can do the same things, maybe not so silently

Looks to me like Jim is looking for the .NET equivalent of compiling with static libraries to produce a single executable. I'll add my vote to his wish list :-)

.