Hi all,
I've been learning API programming via the VBA macro tools in SolidWorks and was wanting to "expand" my horizon somewhat and go up to the next step which is full blown VB programming. I went looking to buy a copy of VB and it doesn't exist any longer :
Well, I'm back on my Python quest - but I haven't quite figured it out yet. It works if you know what you are doing, but it is not to the level I would like it to be for someone who knows nothing about programming. All of my headaches are due to Solidworks not implementing COM fully.
Anyway - in my opinion Python would be the ultimate solution provided it worked 100% with COM. If this fails to be possible I am thinking of writing a full wrapper around the API but that is a lot of work...
snipped-for-privacy@movingpart.com (Chris Dubea) wrote in news: snipped-for-privacy@posting.google.com:
It works fine. I've heard that SW 2004 will even have a VS.NET wizard for writing SW add-ins.
There was also a VB6 Standard edition which was probably priced the same as VB.NET standard. If you have any of those traveling computer shows coming to your area (e.g.
VB and VB.NET are very different. I'm in the midst of trying to adjust to VB.NET and it's quite an adjustment. Just trying to get acclimated to the .NET framework is a little overwhelming. For someone with little background in VB6 it might not be that bad.
However, there's no reason not to use VB6. It'll be a viable programming platform for quite some time (unless a new MS OS somehow breaks the VB runtimes). Plus all of the current API examples found on SW's site are either C++ or VB6 and any tutorials/documentation you find will be written for VB6.
I think C# will offer the same hurdles as VB.NET unless you've programmed C++ before.
Can you still buy SolidWorks 2001 anywhere?
They haven't abandoned them. They just expect those users to move on to VB.NET. Nothing new. You can't really expect MS to keep selling old technology expecially when they've invested so much time and money in the .NET initiative. .NET hasn't rendered all those millions of copies of VB5/6 useless--they can still pump out programs.
Joel Moore
The VB.Net change is larger if you have not written OOP type code. We have written over 46,000 lines in VB.Net and we really like it.
Just my opinion.
-- Bob Hanson CEO Custom Programming Unlimited LLC SolidWorks Solution Partner in two categories (SW API training/consulting and SW PDM provider)
SolidWorks 2003 World User Conference Exhibitor Booth #407
I'll certainly be sticking with it. I'm just amazed at the immensity of the Framework but it's also thrilling to discover all of the things you can do.
Have you seen the MS reference manuals for .NET?!? Back up the forklift!
"Robert V. Hanson" wrote in news: snipped-for-privacy@corp.supernews.com:
You are right regarding the reference manuals but the online documentation is very good along with the different newsgroups that have been setup. We are planning on building a series of Techsmith compressed avi files that customers can download for training in VB.Net for SolidWorks as well as our VB and VC++. The customer would be able to download a pdf manual and the avi files for training and reference.
I have been working with .Net since Sept. 2001 and it has come a long way with much promise.
Best Regards,
-- Bob Hanson CEO Custom Programming Unlimited LLC SolidWorks Solution Partner in two categories (SW API training/consulting and SW PDM provider)
SolidWorks 2003 World User Conference Exhibitor Booth #407
Have something to add? Share your thoughts — no account required.
Ask the community — no account required