Help with SDK "copy design" copydesign.exe crashing with Inventor 2022

[chrisw01a]

Hello group,

Hoping I can connect with someone who can give me some direction here.  Years ago, we modified the copy design program to meet our needs.  It functions like so:  An inventor file is selected, the program recognizes all linked files and then you choose a path of where to copy them to (or rename in the current folder).  During the copy process, we rename the leading characters of the files up to a dash"-" to match a job number so when the files arrive in the new folder, they all contain job numbers.

Example:

original file: 12345-101

new file: 33333-101

It is a simple program but it is the cornerstone of our engineering process for generating jobs from our standard part templates.

SO, I am very exited to implement Inventor 2022 and make full use of the new Model States feature however, our file copy program crashes if a model contains any model states.

Would any of you know what might be causing this?  I would suspect it has something to do with model states... I think the program was built in VB.net 2005 Express but I am still working on trying to find that info.

Attached are the source files and the "filecopy.exe" in the "bin\debug" folder will run the program.

[chrisw01a]

Here is the exception:

[A.Acheson]

I would have this post moved over to the ilogic forum. @CGBenner or 

@johnsonshiue can hopefully move this for you. 

[chrisw01a]

We seem to have misplaced our VB Studio 2008 installer.  Does anyone have a copy?

If anyone has time to run a debug and give me some suggestions, I would really appreciate it!

[chrisw01a]

Thank you

[matt_jlt]

Not sure if it is related but Vault 2022 copy design doesnt work properly on files with model reps either, the only reason we haven't gone to Inventor 2022 yet.

[CattabianiI]

HI @chrisw01a,

> Hey guys/gals, I have a similar issue here do you think this is related?

Yes it could be, try to use currentFile.FilePropertySets instead of currentFile.PropertySets.

Btw if you want someone here to try your code, migrate it properly to Inv2022: proper visual studio version, framework version and mostly create the smallest version of your program that can reproduce the issue.

[chrisw01a]

Thanks for the idea.  It has been 10 years since I did the program so still trying to figure out VB Studio 2022 at the moment.  Had some missing references but I think I got it fixed.

Will try the change and report back.

[chrisw01a]

So it is no longer crashing with your suggestion, but now it is not changing the part number like it is supposed to.

If I breakpoint, it shows the correct value of "-101" but in the finished part, it still shows "Part1" as the part number.

[CattabianiI]

Has 99999-101.ipt been migrated?
Does it have level of details/ model state?
How do you save the document? You could try PropertySets.FlushToFile API (follow the link to check a sample)
Check openedDoc.FullDocumentName value.

[chrisw01a]

I believe it has been migrated because the program checks for migration before doing anything.

'Make sure the version is current
        If openedDoc.NeedsMigrating = True Then
            'MsgBox("The File " & openedDoc.FullFileName & " needs updated to the current version.  Please update it and try again.", MsgBoxStyle.Exclamation)
            'Call resetForm()

            addUnmigratedFile(openedDoc.FullFileName)

            'Exit Sub
        End If

Yes, one model state: 

I'll attach the part here.

The file is saved by:

' Get the FileSaveAs object.
        Dim fileSaveAs As Inventor.FileSaveAs = apprentice.FileSaveAs
' Do the save copy as of all the files.
        fileSaveAs.ExecuteSaveCopyAs()

[baris.uyarD9VEA]

Is there any update on this? Because SDK\UserTools\CopyDesign is not working with ModelStates correctly. If I open the assembly file, change the model state, save it, and close it, the .idw file still points to the previous active model state. And copy design is fail. But Design Assistant 2025 works. If my drawing file is more complex, like having all the different model states on the same drawing file, the SDK tool fails again. Vault CopyDesign or Design Assitant is working correctly all the time.

So, it seems like there is no issue with the API but something missing in the CopyDesign SDK. Could you please help us with what we are missing?

@Markus.Koechl 

[Markus.Koechl]

Hi, @baris.uyarD9VEA. You probably mentioned my name when you were thinking about Vault CopyDesign. But the API used here is Inventor only. I hope you understand this is not my focus, and I won't chime in.

[baris.uyarD9VEA]

Hi, thank you so much for the explanation. Who from Autodesk can help us with Inventor API?

[baris.uyarD9VEA]

Hi, thank you so much for the explanation. Who from Autodesk can help us with Inventor API?