For those new to message boards please try to follow a few simple rules when posting your question.
Choose the correct forum for your message. Posting a VB.NET question in the C++ forum will end in tears.
Be specific! Don't ask "can someone send me the code to create an application that does 'X'. Pinpoint exactly what it is you need help with.
Keep the subject line brief, but descriptive. eg "File Serialization problem"
Keep the question as brief as possible. If you have to include code, include the smallest snippet of code you can.
Be careful when including code that you haven't made a typo. Typing mistakes can become the focal point instead of the actual question you asked.
Do not remove or empty a message if others have replied. Keep the thread intact and available for others to search and read. If your problem was answered then edit your message and add "[Solved]" to the subject line of the original post, and cast an approval vote to the one or several answers that really helped you.
If you are posting source code with your question, place it inside <pre></pre> tags. We advise you also check the "Encode "<" (and other HTML) characters when pasting" checkbox before pasting anything inside the PRE block, and make sure "Use HTML in this post" check box is checked.
Be courteous and DON'T SHOUT. Everyone here helps because they enjoy helping others, not because it's their job.
Please do not post links to your question into an unrelated forum such as the lounge. It will be deleted. Likewise, do not post the same question in more than one forum.
Do not be abusive, offensive, inappropriate or harass anyone on the boards. Doing so will get you kicked off and banned. Play nice.
If you have a school or university assignment, assume that your teacher or lecturer is also reading these forums.
No advertising or soliciting.
We reserve the right to move your posts to a more appropriate forum or to delete anything deemed inappropriate or illegal.
Get this: GitHub - 5everin/3D-Model-Viewer: A software renderer written in vb.net[^] ... and see if it won't open without an error usg VS2010 (as you suggest) ... but regardless of whether it loads or not, dissecting the classes just to have a look at how something apparently more modern in it's approach to .obj manipulation and viewing could prove informative enough for you to have a go at it yourself ... starting with a VS2010 project, scratchwise.
I agree need to know what line is throwing the error.
Can you see what ex.StackTrace shows in your Catch ex as Exception block?
Below lets you create a breakpoint when an error is raised then you can resume to the line giving the error This is just to help you find your error line - use catch/try/end try otherwise
To debug remove your try, catch, end try then...
' <<Your code goes here>>' at end of function/sub add...
MsgBox Error, vbCritical, CStr(Erl) + " " + CStr(Err)
Resume 'quit_proc'< Note the comment before quit_proc. Put breakpoint at Resume line (F9) then when hit, step (F8) through to the line giving the error'Remove the 'comment before quit_proc when not debugging or else you will get in a loop if any error is raised or (better) revert to your Try, Catch, End Try construct