|
CatchExAs wrote: But an executable has some obvious benefits,
Like what? 
The only "benefit" an executable has over a library is that it can be executed directly. For the vast majority of class libraries, executing them doesn't make any sense.
For example, what would you expect to happen if you executed mscorlib? System.Data? Etc.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
What if you required that they tested and verified themselves?
|
|
|
|
|
What do you mean by "tested and verified themselves"??
|
|
|
|
|
Say, main() by default was required to call a bunch of test suites that executed unit tests. I once worked somewhere where they did this btw.
|
|
|
|
|
Soooo, you're going to ship your unit tests with the code to the customer? That sounds stupid. That's like shipping the Paint Shop from the assembly plant with the car that it built.
|
|
|
|
|
Sounds more like including the diagnostic reader device with the car rather than requiring a visit to the shop when the check engine light comes on.
|
|
|
|
|
When was the last time you executed unit tests on customer site?
I've written seperate tools to diagnose database problems, but never to verify "the code". If the .EXE gets corrupted, chances are good it won't even run, and if it is corrupted, chances are good you've got hardware problems.
|
|
|
|
|
I never write or execute unit tests at all, anywhere.
I don't have the same concerns as the OP and I don't think we're talking about DLLs shipped with an application, but libraries provided to other developers for use in their applications -- like if I wrote an ISO 8601-compliant date handling library for example, but only distributed the DLL rather than the code.
Personally, when I get a DLL from some third-party (an ADO.net provider perhaps) I don't like having to create a Solution and Project, then add a reference just so I can use the Object Explorer to see what's in it. It would be convenient if it were an EXE and running it would provide (version-specific) documentation and such (hopefully more accurate than what's available on the developer's website, if any). Additionally, the Object Explorer only says what's in there, not how to use it, no documentation.
I suspect there must already be a tool that allows sort of a command-line Object Explorer, but I haven't looked. Certainly one could be written, but it still wouldn't provide everything that a custom baked-in tool would.
Seeing that given a DLL with some (public) class C with a (public) method M that takes a string parameter S and returns a string is all well and good, but wouldn't it be convenient to immediately be able to execute:
somelib test C.M "hello world"
and have it report the result? Without having to access an IDE and write a simple test app just to see what it does?
|
|
|
|
|
Or a compiler that bootstraps and tests itself?
Or an installable that operations can't f*** up?
There are always reasons for questions 
|
|
|
|
|
CatchExAs wrote: Or a compiler that bootstraps and tests itself?
Really? How often do you see that and how often are you going to use it?
CatchExAs wrote: Or an installable that operations can't f*** up?
Depending on what you mean by "operations", yeah, right. If you're talking about people, there's nothing they can't f*** up and there's always some situation that you're code isn't going to be able to recover from.
|
|
|
|
|
Dave Kreskowiak wrote: Really? How often do you see that and how often are you going to use it?
True, you see it rarely. But it is a useful technique to some, and so might be useful to others. You wouldn't know until you tried it.
Dave Kreskowiak wrote: Depending on what you mean by "operations", yeah, right. If you're talking about people, there's nothing they can't f*** up and there's always some situation that you're code isn't going to be able to recover from.
Of course, which is why we automate things in the first place but the point is that the deployed binary can run tests on itself 'in situ' rather than a test environment which may or may not be representative of the target production environment.
|
|
|
|
|
CatchExAs wrote: Can anyone think of a technical reason why you'd choose to build a library over
an executable?
..because the code is not an executable; that's the reason I did not include an entry point.
If I put a logger into a separate assembly, I can easily swap it with another, without ever touching the executable. The logger-class does not need to run independently of the main executable. Same goes for most code.
And yes, I've got some private projects where I use executables as if they are DLL's; it's just a collection of code after all.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
One thing I have considered (but never actually done) is to have a library as an EXE so it can print out documentation (to the console) and maybe allow testing and demoing the functions contained therein.
<aside>
In OpenVMS, the analog of a DLL is a "shared executable", which generally has an EXE extension.
</aside>
|
|
|
|
|
My thinking was along similar lines i.e. writing small executables that did one thing but did it well a la UNIX.
Except I would require that the default behaviour of a main() function was to run a test suite embedded in the assembly.
|
|
|
|
|
You can have a static int Test(string[] args) for that (unless you plan on using debug, vs stdout). Call it with the help of a shell-extension or external command that loads the assembly and executes your custom entrypoint 
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Having a separate console app that loads the Assembly would definitely be another way, but the only reason would be to simply remove the main, I don't see a big benefit.
|
|
|
|
|
I was thinking:
myProgram.exe -> runs a test suite
myProgram.exe /run -> runs a traditional program if implemented or returns if it's a library
|
|
|
|
|
That sounds kinda backward to me.
|
|
|
|
|
PIEBALDconsult wrote: I don't see a big benefit.
You'd be separating the "testing" code from the code being tested. Better yet, put it in your own class, as opposed to the Program class, and get the benefits of inheritance.
I can see how one would create an application that executes SQL from the command prompt, and references this as if it is a library to get the appropriate databaseclasses.
Then again, you don't want to be referencing a WinApp application from a Webapplication and have it load the complete Forms-environment and all its dependencies.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: referencing a WinApp application from a Webapplication and have it load the complete Forms-environment and all its dependencies
I don't think we're talking about doing anything like that. Just a regular library, but with the ability to self-identify at the console.
|
|
|
|
|
So, how are you going to share your reusable code? Executables? Or are you going to cut and paste? Oh, and if you're adding a reference to something like a standard .NET assembly guess what, that's a DLL? Simply, a DLL is a convenient way to share functionality.
|
|
|
|
|
Pete O'Hanlon wrote: how are you going to share your reusable code?
The same way, but as an EXE with some sort of helpful library-specific functionality in the main. :shrug:
|
|
|
|
|
Why would you want to make your code monolithic by including it in larger .EXE's, thereby increasing load time?
Why would you want to give the users the ability to launch a "library" .EXE that does nothing but return to the command prompt?
|
|
|
|
|
Dave Kreskowiak wrote: make your code monolithic by including it in larger .EXE's
That's not what he means.
|
|
|
|
|
I know.
I was just pointing out that some people can go overboard with the ILMerge tool and end up making an .EXE that's 10's or 100's of MB in size. Then they wonder why it takes so long to load.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
