【转帖】imports interop verses imports sldworks

yang686526

imports interop verses imports sldworks?
i started looking at the macros in 2009 and noticed that when i create a macro using solidworks it imports solidworks.interop.sldworks and does the ctype conversion for modeldoc2 and other objects. when i first started using vb.net the conversions were confusing me so i just use imports sldworks and i quit using the ctype conversions.
question - what are the pro and cons of using imports interop verses using imports sldworks?
dan miel
sw 2008
i don't believe there are any real advantages, both tlb and dll files should be exported with each release and so in esscense should be the same, just one is using .net, the other is com. obviously com is technically quite legacy and so .net should be chosen to "keep up with the times", but for programmers i have yet to come across any advantages/disadvantages.
batchprocess at the moment uses com with no problem, but bp 2.0 will be using the .net libraries purely for conformity.
thanks for replying luke. i wasn't aware that it was a difference between using com and net but after reading this it seems like i did read that someplace.
thanks again
dan miel
quick