He wouldn't, I do the same thing in VB.net when working with structure. It's a complicated process involving nestled loops that can quite easily go out of hand if not done right, but that's not the point.I think you are over analyzing the situation. Why would he need to go through C++ to have Tool generate a shader file, which it does already? All tool does is create a blank shader tag, based on whatever type you choose when prompted.
I'm not discouraging him from creating some competition here. I'm going to recommend he doesn't because I can guarantee that he will get frustrated and give up at it really fast. The features in Tool # and Tool ++ are not easy to duplicate because of their complexity (Like Tool ++'s RadioButton List and Tool #'s Guerilla-like functionality/shader detection), but if he's going to do something simple, like make a small little point and click application, he needs to do a little research on using "Process.Start" in Visual Basic, and how to use it.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks