I'd buy that for a dollar?

How many hours have gone into it?

The appropriate price is the highest one that most people would be willing to pay to purchase your product, so think along those lines. What would you pay to get a copy? For something like this I wouldnt go any higher than 30 US Dollars-- something around 20 bucks would be a realistic asking price, that is if Im picturing the components functionality correctly.
 
Sounds good except itd take a futher 35 hours to get the money in ;)
Still - the beta and documentation are here if anyone wants a look-see...
 
Theres a new version up on the site that exposes the print job collection (so you can iterate through it and do whatever) and the printer information (status i.e. out of paper, off line etc and location, comment, job count etc.) and its licensed until 2003-06-06 if anyone would like to give it a look-see ;)
 
I have to say Im surprised that the .Net framework does not already provide this sort of functionality.

On a usage note I for one would not want to have to distribute MerrionComputing.info to my customers. And why do you need Toolbox.bmp? Can it not be compiled into the assembly?
 
Originally MerrionComputing.info was a custom licensing requirement - but I have removed this. Just havent updated the documentation as my upgraded version of Document!X hasnt arrived.

There are lots of holes in the .Net framework that still require API coding - for example there seems to be no way to add/remove users from user permissions from a DACL without recourse to the AddAccessAllowedAce type API stuff. Im sure the framework will support this as soon as I have committed another hundred hours to getting it working :(...

Do you know how to compile the toolbox bitmap into the application? The attribute <ToolboxBitmap()> seems to require a filename, which is a bit odd. I suppose the default component bitmap isnt too bad anyway...
 
No, I have no idea, not having done any serious work with .Net yet. It just seemed like a weird thing to omit.

Hang on, whyd you need a toolbox icon distributed anyway. I assume that the license does not allow your customers to pass on the dev license to third party developers from their clients.
 
Ive added the "compile the toolbox icon into the component" to the ever expanding todo list...apparently it is done like this....
 
Last edited by a moderator:
In case anyone is interested, version 1.1 (the first "Release" build ) was posted today. Numerous bug fixes and enhanced operation.
 
Back
Top