Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations cowski on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

SW07 API book

Status
Not open for further replies.

ScottWisker

Mechanical
Jan 31, 2007
15
There's an API book on amazon for SW2006. I know quite a bit changed in the API from '06 to '07. Does anyone think it still may be worth while to get or does anyone know if/when an '07 API book will be available.

Thanks
 
Replies continue below

Recommended for you

If the book teaches how to use the SolidWorks API then, the changes between SW2006 and SW2007 will not be a big thing. You can always look in API help to see if the call is obsolete or not. The biggest change is that SolidWorks is going the way of .Net and changing over to using more objects.

SA
 
I've heard about the migration in fact I found this in the API documentation:

"If you developed your application using Visual Basic 6.0 on Windows XP, then the controls on your forms and dialogs might behave unexpectedly. Therefore, it is recommended that you port your application to Microsoft Visual Basic .NET or peruse Microsoft's Knowledge Base and the internet for possible workarounds."

But I've also heard that SW2007 isn't quite ready for .NET and at least at this time VB6 is the most stable and consistant.

Here's my situation. I have a HUGE macro that does a whole bunch of stuff - basic PDM functions/file management, Excel data tracking, and some CAD manipulation. I'm working on converting it into a stand-alone application, but before I get started I want to make sure I'm using the correct platform. I'm open to input.

Thanks
 
I have only started to play with VB.Net. From what I read, you cannot just paste your code into .Net and run it. There is some sort of conversion wizard but the books I have been reading really do not recommend it. As you have stated SW2007 still works with VB6 (version macros are created in). My advice, since you describe the macro as being huge, I would use VB6 to make sure the code works as expected as a stand alone and then convert it to .Net

SA
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor