Hi
We have been using KernelCAD 3.2 in our app for a while. We are looking to upgrade to the latest DGK version. Should I expect problems with that?
Regards
Mike
VB6 to DGK upgrade (restored)
-
Prashant Kande
- Posts: 55
- Joined: Tue Jun 18, 2024 6:12 am
Re: VB6 to DGK upgrade (restored)
Hi Mike
Everything should work with v6.2 in the same way as the version you currently have. We do not plan any changes which would prevent this in the future
Generally though, my personal opinion is that new development should not be done with VB6, unless you do not plan to retire in the next five years.
I recommend porting your application to .NET as soon as possible. It is much more productive. I am working 90% of the time with C++, but when I need to do something in .NET it is a joy. Everything is consistent, lots of free functionality. Everything is on high level. All well-documented.
VB6 is quirky. It means that it is expensive to get working something inside. The worst thing is that it is not supported and not developed. Also I think in 3-5 years time it will be hard to find 32 bit applications. So customers will demand 64 bit.
With .NET you would have much more options for components and many things either available in .NET or are easy to implement by yourself.
It will take time to learn to be productive, but not that long. I did not actually read any books on it. I could learn it but doing it. The documentation is good. There are lots of samples.
Porting the code is a big job of course, but may not be that much. There are tools which automatically convert code. This saves lots of time, although manual work will be needed.
You will have to do it eventually. So it is better to start it earlier so that less code will be needed to port.
Regards
Everything should work with v6.2 in the same way as the version you currently have. We do not plan any changes which would prevent this in the future
Generally though, my personal opinion is that new development should not be done with VB6, unless you do not plan to retire in the next five years.
I recommend porting your application to .NET as soon as possible. It is much more productive. I am working 90% of the time with C++, but when I need to do something in .NET it is a joy. Everything is consistent, lots of free functionality. Everything is on high level. All well-documented.
VB6 is quirky. It means that it is expensive to get working something inside. The worst thing is that it is not supported and not developed. Also I think in 3-5 years time it will be hard to find 32 bit applications. So customers will demand 64 bit.
With .NET you would have much more options for components and many things either available in .NET or are easy to implement by yourself.
It will take time to learn to be productive, but not that long. I did not actually read any books on it. I could learn it but doing it. The documentation is good. There are lots of samples.
Porting the code is a big job of course, but may not be that much. There are tools which automatically convert code. This saves lots of time, although manual work will be needed.
You will have to do it eventually. So it is better to start it earlier so that less code will be needed to port.
Regards
-
Prashant Kande
- Posts: 55
- Joined: Tue Jun 18, 2024 6:12 am
Update June 2024
The original 3.2 interface is still supported and .glm save/load still works via the converter. But for performance and productivity we recommend implementing new functionality based on .mdg format and the new _DG set of interfaces
Regards
Regards