Is NSBASIC trying to keep VB6 alive?

[RhinoBull]

We are talking about the people that are still on VB 6 that dont make the jump to .NET because of issues like that and the one you mentioned.

For the ones that have never seen VB 6 then its irrelevant.

How is it irrelevant again? Rob, are you suggesting that spending hours on task like I posted is normal?
People that never used VB6 would never know that there was an extremly easy way to print few lines but they all are wondering why is it so compilicated?
So, please don't try to say it's not an issue because it is - everybody knows this.
All the pros in the world are trying to finally accept new "idea" however you can't full everybody - if you try to sell me something nthat was very easy and now it is not I will make some noise.
This is basically why we had 3 releases in three years - someone at MS made a big boo-boo... And they still trying to recover...

[RobDog888]

How is it irrelevant again? Rob, are you suggesting that spending hours on task like I posted is normal?
People that never used VB6 would never know that there was an extremly easy way to print few lines but they all are wondering why is it so compilicated?
So, please don't try to say it's not an issue because it is - everybody knows this.
All the pros in the world are trying to finally accept new "idea" however you can't full everybody - if you try to sell me something nthat was very easy and now it is not I will make some noise.
This is basically why we had 3 releases in three years - someone at MS made a big boo-boo... And they still trying to recover...

Again, my post is taken out of context.

I was stating that for the transition from vb 6 to .net reasons is irrelevant to a .net programmer only as they make do with the way .net operates. Sure, its not normal to spend allot of time on a print statement but thats not a reason to keep from using .net as you could very easily create a CR report and let it do the printing or use some other workaround.

If someone wants to stay with VB 6 because of a lack of information that would allow them to make a educated choice then thats one thing. But for someone to never have gave .net a look or chance then thats just biasism (is that a word?). I know you use .NET and VB 6 but it will take a few more years for .NET to have replaced VB 6 substancially and other solutions/fixes/workaround will have been created.

I dont care if someone loves one language vs another. I dont know why you think I care. I dont hound you to give up vb 6 do I? I still post in the VB 6 forum as I still have some apps written in vb 6 that arent going to be rewritten until later this year. Its a process and not an overnight one.

There is no "boo boo" that was made by MS as its an evolution process. 2002 wasnt too good, 2003 was better, and 2005 is to the point where it can actually be used in a production enviropnment. Within two more years Orcas should be out or close to it and I will be looking into the Orcas CTP preview as soon as I get Virtual Server installed.

[RhinoBull]

Again, my post is taken out of context.

I was stating that for the transition from vb 6 to .net reasons is irrelevant to a .net programmer only as they make do with the way .net operates. Sure, its not normal to spend allot of time on a print statement but thats not a reason to keep from using .net as you could very easily create a CR report and let it do the printing or use some other workaround.

If someone wants to stay with VB 6 because of a lack of information that would allow them to make a educated choice then thats one thing. But for someone to never have gave .net a look or chance then thats just biasism (is that a word?). I know you use .NET and VB 6 but it will take a few more years for .NET to have replaced VB 6 substancially and other solutions/fixes/workaround will have been created.

I dont care if someone loves one language vs another. I dont know why you think I care. I dont hound you to give up vb 6 do I? I still post in the VB 6 forum as I still have some apps written in vb 6 that arent going to be rewritten until later this year. Its a process and not an overnight one.

There is no "boo boo" that was made by MS as its an evolution process. 2002 wasnt too good, 2003 was better, and 2005 is to the point where it can actually be used in a production enviropnment. Within two more years Orcas should be out or close to it and I will be looking into the Orcas CTP preview as soon as I get Virtual Server installed.

We talking about two different things.

[RobDog888]

We talking about two different things.

Exactly as I was saying.

[rory]

Exactly as I was saying.

i still love Vbscript .. best thing MS ever came out with ..
well other than windows ..

It has its restrictions .. but still its a great little tool ..

[RhinoBull]

Exactly as I was saying.

I often don't understand what you're trying to say though.
You replied to what I posted but afraid you read between the lines.