Translating a legacy VB into the new VB.Net

Hi there,

I have an old code written in the legacy VB.net format and i am trying to translate it to the new VB.net. In my attempt I always bump into this error

"error: Index was out of range. Must be non-negative and less than the size of the collection.Parameter name: index (line: 0)"

I understand that this means there is something wrong with my data lists. I feed the same data to both scripts. The legacy one operates smoothly, but the new doesn't. has anybody been through a similar case?

Regards,

Replies to This Discussion

Permalink Reply by David Rutten on July 3, 2011 at 1:31pm

Hi Marios,

without seeing any code I won't be able to give any support.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Marios Tsiliakos on July 3, 2011 at 1:36pm

Yeah David I know,

That makes sense, I wanted to, but unfortunately I can't share it at the moment cause it is a commercial project. This error is usually a data list length error isn't it?

Thanks in advance,

Permalink Reply by David Rutten on July 3, 2011 at 4:18pm

Typically yes, you're trying to access an element in a collection, list or array that is outside of the bounds.

The odd thing is the error happens at line 0. Does this error happen after you compile the script or is it something that happens while the script runs?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Giulio Piacentino on July 4, 2011 at 1:41am

This might be understandable: the line refers to the highest frame in the stack, and this frame is the .Net one (it is in mscorlib.dll, in System.Collections.Generic.List.Item(index) I would say), not the one in Grasshopper.dll. This is probably why the runtime cannot solve the line number.

- Giulio

_______________

giulio@mcneel.com
McNeel Europe

Permalink Reply by Marios Tsiliakos on July 4, 2011 at 3:23am

Thank you Giulio,

I will try and re-write the code from scratch in the new VB.net and not just translate it. That might solve give me some hints. I will post back if I make some progress.

Thank you for you help.

Permalink Reply by Marios Tsiliakos on July 4, 2011 at 3:17pm

Sorry David,

For some reason I missed that answer of yours. No, it happens when I compile it. As I said to Giulio I think I will write the whole script from scratch in case i am missing something. thanks for your help. if i manage to find what is going on I will let you know

Permalink Reply by Marios Tsiliakos on July 7, 2011 at 9:48am

Here is something strange.

I have just decided to give the code another try. I transferred the component in a 'fresh' file and it works!!! Without changing a single bit of the code. ......weird.....And I was so frustrated that I began a whole discussion on the matter. Pfff.

Anyway thanks to everyone for their help. I will try my components in new files first in the future..

Permalink Reply by David Rutten on July 7, 2011 at 9:56am

This is very strange. Scripts inside components get compiled from scratch whenever a solution is run and the script isn't compiled yet. It could either be in an uncompiled state because the ghx file was only just opened, or because someone specifically destroyed the compiled code (as I do when you close the Code Editor window).

Copy/Pasting a component into a different file will obviously result in a recompile, but then so should opening the same file again.

What happens when you paste the component back into the original file?

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Marios Tsiliakos on July 7, 2011 at 2:13pm

Copying at the first file to the same file doesn't work. Copying from the new file to the first is ok.. I have no idea what is wrong...

RSS