[bjwade62]

I'm having Strange Problems w/ converted projects from VB6.

1. Step into debugging doesn't work.
2. Breakpoints are ignored no matter if debug or release are selected.
3. Build does not build a new instance of the app. Date never changes.

Everything works when I start a new project, it's just the converted ones that don't. Anyone else have these problems?

[reboot]

The best thing to do is convert your vb6 projects by hand. That conversion thingie is pretty sorry.

[AtmaWeapon]

Yeah, usually it's a strange occurrence if a project actually works after it goes through the converter. If you run into things you can't figure out to convert we have no problems helping you out. When there are no questions to answer I actually have to work at work and we can't have that can we?

[bjwade62]

My bad. I had build errors. I'm new to VB.net. I assumed when I was asked if I wanted continue even though there were build errors it would somehow run it in debug mode. It's a bit confussing.

Once I removed the build errors everything worked fine.

Now can I have my VB6 back???

Thanks,
Bernie

Originally Posted by AtmaWeapon

Yeah, usually it's a strange occurrence if a project actually works after it goes through the converter. If you run into things you can't figure out to convert we have no problems helping you out. When there are no questions to answer I actually have to work at work and we can't have that can we?

[AtmaWeapon]

Originally Posted by bjwade62

Now can I have my VB6 back???

Thanks,
Bernie

So long as you have this attitude you will NEVER learn how to use .NET.

Microsoft has killed VB6. Staying on that path has no future anymore. Tell it goodbye and join the rest of the programming community in the celebration.

I had to learn LotusScript when I started getting Notes projects. I found that at first, I was trying to figure out how VB .NET would do something, then trying to convert that to LotusScript. I was having lots of troubles and not accomplishing anything.

Then, I started pretending that LotusScript was my first programming language. When I didn't know how to do something, the only point of reference I used was the LotusScript documentation. Within a week, I had learned most of what there was to know.

So, too, must you shed your prior knowledge of VB6 when moving to .NET. Many things are similar, but many things are different. You will have a much easier time if instead of saying "How do I do this VB6 task in VB .NET" you start saying "I can't figure out how to do this in VB .NET." The difference is you aren't writing the same program twice. When this is done, it is easy to look at the .NET documentation for VB6 functions and assume that since they aren't spelled the same they must be different. Every time you start to work with a control, spend some time reading the "All Members" section of its documentation. You can learn a lot from the single-sentence descriptions, and usually after reading those you'll think "Oh, that's like <whatever> in VB6!" Now, this isn't bad. It is much better when learning a new language to tell yourself "This is the equivalent of the old language" than to say "What is the equivalent of the old language. The former is a mental construct that helps you make the move, the latter is a mental construct that keeps you stuck in the old language.

The sooner you can start thinking only in .NET, the sooner you will understand it. Then, when Microsoft releases the next big thing in 5-10 years and .NET is getting the boot, you can apply the same methodology and learn the next language faster.

[bjwade62]

I know you're right. I gets frustrating when the big shots are breathing down your neck and they have no idea how long something should or will take. It's hard for them to understand why similar projects used to take 1/2 the time now (for a while at least) take twice as long. They don't (and wont) see the big picture. They know I can produce well written programs in VB6 so... (in their words) why not use it instead of VB.NET.

I agree with you, just something I have to work out.

Thanks,
Bernie

Originally Posted by AtmaWeapon

So long as you have this attitude you will NEVER learn how to use .NET.

Microsoft has killed VB6. Staying on that path has no future anymore. Tell it goodbye and join the rest of the programming community in the celebration.

I had to learn LotusScript when I started getting Notes projects. I found that at first, I was trying to figure out how VB .NET would do something, then trying to convert that to LotusScript. I was having lots of troubles and not accomplishing anything.

Then, I started pretending that LotusScript was my first programming language. When I didn't know how to do something, the only point of reference I used was the LotusScript documentation. Within a week, I had learned most of what there was to know.

So, too, must you shed your prior knowledge of VB6 when moving to .NET. Many things are similar, but many things are different. You will have a much easier time if instead of saying "How do I do this VB6 task in VB .NET" you start saying "I can't figure out how to do this in VB .NET." The difference is you aren't writing the same program twice. When this is done, it is easy to look at the .NET documentation for VB6 functions and assume that since they aren't spelled the same they must be different. Every time you start to work with a control, spend some time reading the "All Members" section of its documentation. You can learn a lot from the single-sentence descriptions, and usually after reading those you'll think "Oh, that's like <whatever> in VB6!" Now, this isn't bad. It is much better when learning a new language to tell yourself "This is the equivalent of the old language" than to say "What is the equivalent of the old language. The former is a mental construct that helps you make the move, the latter is a mental construct that keeps you stuck in the old language.

The sooner you can start thinking only in .NET, the sooner you will understand it. Then, when Microsoft releases the next big thing in 5-10 years and .NET is getting the boot, you can apply the same methodology and learn the next language faster.

[AtmaWeapon]

Yeah, all too often management does not understand the gravity of the decision to move from one language to another. One particular individual I know has to listen to their manager talk about how much faster and easier he could have written their new database application in DOS. You have made the right decision in moving to .NET.

I really encourage you to read the documentation for the heck of it when you get bored. Half of the little tricks I have picked up came from noticing an interesting sounding method in the Intellisense popup and going to the documentation to investigate. There's a lot of neat things that most people never see, so every now and then pick a random class you are using and go through all of its members. You'll quickly know more about .NET than most people do.