That last link is exactly the type of thing I had in mind.
Regarding the stability issue, I may have an idea on that. In all of the sample code I've been looking at, it all seems to derive from the same ultimate sample code. I've already fixed 2 bugs that I found in that sample code--and that's without really looking for bugs!
My guess is that whoever wrote that viewer just lifted the sample code and didn't change anything which is why it's not completely stable. My guess is that it shouldn't be hard to make it a bit more stable.
Regarding the language of choice, that brings up an interesting point. I was planning on making it in VB. There won't be any dependency issues since I can include the VB Runtimes and any and all DLLs that are necessary. I have seen some more examples in C++ that I could use but since the VB code was based off this code, I imagine the stability issues will still be there.
How about this...
I was thinking of writing this in C#. The upside is that I'm confident that it will be solid as far stability. The question is how many people who would use this app have the .NET runtime? Or a better question is how many people have access to the .NET runtime without requiring a download? It's a heavyweight runtime at 20+ MB. But it's included with Technet and MSDN and is freely downloadable off the web. I can even package 2 setups--one without the runtime and one with it included.
I've been working with .NET for about 6 months now and would like a real project to actually deploy to people. This seems like a good candidate. But at the same time I don't want to alienate too many people.
What do you all think?
_________________________
Stevie
