Advice wanted

[xterra]

How is everyone doing.

I'd appreciate it if I could hear some advice regarding some software I am in the process of making.

This is NOT an ad for my site, so I purposly took it off my signature in this post.

I've written alot of code that has to do with parsing source code, analyzing differences, reading VB project files, etc.

I have converted alot of my source code into an ActiveX control, one specifically that allows the user to add intellisense technology (like the one in the VB6 IDE) to their applications, that features color syntax highlighting, etc.

Now my question is this. I had it on the internet for a day but took it down but I didn't even know if I was waisting my time with it. Is that control even something people would be interested in?

Or am I better off writing articles to explain all my source code as a resource so I can teach others how to do similar things. Such as writing an article to explain how to do advanced parsing.

Then today I wrote a program to display all the procedures in a VB project and I was working on making it a code comparison program like version management, but that's been done.

So I have all this code, I don't want to waist it. Wrap it up as an ActiveX control? Write an article?

Any advice is appreciated.

Regards,
Rob.

[RobDog888]

You will want to do a search for other controls like yours and see what the competition looks like. If it is large but the products look inferrior then I say release it as a commercial product. You can alsways test the waters first this way and if it doesnt work out then I say try the article route. Once you write an article for it, your code will be out there and you cant sell it at all.

[xterra]

You will want to do a search for other controls like yours and see what the competition looks like. If it is large but the products look inferrior then I say release it as a commercial product. You can alsways test the waters first this way and if it doesnt work out then I say try the article route. Once you write an article for it, your code will be out there and you cant sell it at all.

Yeah true, I don't want to lose rights to it. Do you think it would be a better idea to not sell it commercially, not write an article for it, but just have the control for free? (Not free as in open source, but free of charge). I suppose this would bring more people to my site, and honestly I'd rather have impressions than purchases. I just want my site out there.

[RobDog888]

Yes, that is another option as it depends on what the ultimate goal is. If your trying to break into the control market then you can have a few beginner or such controls available as freeware. Then if they want controls with more advanced features or such they will have to pay. This will give the end user the ability to test out your controls but then it can also backfire.

You can also make your control a time limited control where its use is limited to something like 30 days or such. Then if they wish to distribute or use beyond the 30 days they have to purchase it.

[xterra]

Yes, that is another option as it depends on what the ultimate goal is. If your trying to break into the control market then you can have a few beginner or such controls available as freeware. Then if they want controls with more advanced features or such they will have to pay. This will give the end user the ability to test out your controls but then it can also backfire.

You can also make your control a time limited control where its use is limited to something like 30 days or such. Then if they wish to distribute or use beyond the 30 days they have to purchase it.

First off thanks for taking the time to help me out.

And you have a good idea about the trial version. I actually have it sort of implimented, I created an (easy to break haha) algorithm for generating serial numbers. And if the serial number is not entered, an ad is displayed. Otherwise, it is invisible.

I suppose I will try it again, since you have good advice. I will see how popular it gets (or doesn't get). I am afraid to sell it right now, because if there are bugs, I wouldn't know what to do!

Thanks again,
Rob.

[RobDog888]

No prob.

There is a good registration scheme done by MartinLiss.
Its located here. http://www.vbforums.com/showthread.php?t=232146

Also, search the Forums for time trial code as I know its been discussed alot already and you should be able to get some good code for it.

[Hack]

I am afraid to sell it right now, because if there are bugs, I wouldn't know what to do!

One of the reasons you might want to consider giving it, at this time, is for people to test in a variety of situations. Any bugs that got reported, you could then fix, and once you have a pretty stable control, then look into selling it. You could also tell folks that if they are interested in testing this for you, and reporting any bugs, then when your commerical version is available, they will get the first release free.

[RobDog888]

Thats also another good idea but I generally dont like giving out code that I intend to be commercial at any stage its in during development.

[xterra]

Maybe I'll try that beta test idea, because they wouldn't be getting any of the code since its a compiled OCX.

[Hack]

Thats also another good idea but I generally dont like giving out code that I intend to be commercial at any stage its in during development.

Oh, I didn't mean giving out the code...oh no....I meant giving out the compiled component.

As there seems to be an intent of someday marketing this product, the source code would remain exclusive.

[RobDog888]

Yes, then giving out buggy beta copies for free is worth it with the promise of free release versions in the future for their help is a great idea.

[xterra]

Very fast responses on this site!

To go along with both of your ideas, I think I am going to create a form that users submit to request a beta copy, and that way I have their contact info, I can send them the full versions upon final release.

What do you think?

[RobDog888]

Even better. Tell then that if they sign up they will be able to get updates on bugs that other members find so they are not duplicating their efforts.

[xterra]

Even better. Tell then that if they sign up they will be able to get updates on bugs that other members find so they are not duplicating their efforts.

Great! I'll get working on that email script then.


Thanks again guys,
Rob.

[Hack]

Very fast responses on this site!

To go along with both of your ideas, I think I am going to create a form that users submit to request a beta copy, and that way I have their contact info, I can send them the full versions upon final release.

What do you think?

Oh a global scale, this is along the lines of what Microsoft does when they need their new releases tested. Of course, the testers don't wind up with free copies of the releases (at least, I don't think they do).

I think this is a very good idea. Giving it to registers users will more than likely, get you some good feedback, plus, when you finally market the release version and are charging for it, they can have the bragging rights of saying "I helped test this!"

[RobDog888]

Not only that but also it will eliminate the issue of a person saying that they helped but they didnt get their release version. You need a way to track those that help if your going to be offering something in return. You dont need any headaches from someone wanting a freebie without doing the work.

[Hack]

Not only that but also it will eliminate the issue of a person saying that they helped but they didnt get their release version. You need a way to track those that help if your going to be offering something in return. You dont need any headaches from someone wanting a freebie without doing the work.

Absolutley.

Another reason you would want to keep track of who was doing your testing is that if you come up with a second product, you will have a database/card file/whatever of people to contact for more testing.