Inventor Customization

Inventor Customization

Reply
Valued Contributor
SteveX82
Posts: 69
Registered: ‎05-26-2010
Message 1 of 2 (365 Views)

Another iLogic bug - Microsoft .NET Framework error?

365 Views, 1 Replies
11-30-2011 04:24 AM

I've nearly finished creating my iLogic configurator,but have reached one last stumbling block during the save out process. As some brief background, the configurator was designed to do the following:

 

1) Use an iLogic form and rules to configure skeletal models as desired. This includes altering geometry AND suppressing unneeded subassemblies and components.

2) After the model is configured, the user can click a button to "finalize" the design. This includes deleting all suppressed components, and saving-as the skeletal components, subassemblies, and top-level assembly. The copy rule will also save out copies of some template drawings and replace the internal references to see the new models.

3) Finally (this is the step that is "causing" the issue), the template drawings must have rules that automatically run when the drawing is opened. These rules are necessary to rescale the drawing views, suppress views, etc.

 

After intoducing rules to the template drawings, I started to get a "Microsoft .NET Framework..... unhandled exception" error after the copy rule has finished running. It doesnt even matter what it actually contained within the rules; even a blank rule triggered by "After open" will trigger this vague error.

 

 

 

Since my actual configurator is too large to share, I created an example assembly that duplicates the problem. Please see the attached zip file (containing the models and top-level drawing) and the subassembly drawing. After saving/extracting the files to your harddrive, do the following to encounter the error:

 

1) Open "Top Level Assembly" and click "Copy Rule" on the form to begin the save-out process.

2) After choosing a filename and location, you'll notice that the new files are copied out without any errors, all suppressed components (the 3rd and 4th Block Subassmeblies at the top level, various Pins at the subassembly level) have been deleted, and the LOD has been changed back to "Master".

3) Now open up the original "Subassembly Drawing.idw" and unsuppress the Rule.

4) Repeat Step 1, and you'll get the "Unhandled exception" error at the end of the save-out process. You'll also notice that the suppressed components weren't deleted properly.

 

I'm hoping that somebody can suggest a fix or workaround, or at least some insight as to why this is happening.

 

Thanks in advance,

Steve

Mentor
LOONYLEN
Posts: 201
Registered: ‎03-16-2009
Message 2 of 2 (343 Views)

Re: Another iLogic bug - Microsoft .NET Framework error?

11-30-2011 03:04 PM in reply to: SteveX82

Hi Steve,

 

Try rearranging your code order. I know this helps because we sit next to each other and I already know this fixed the issue.

 

I'm just trying to get a Shameful "Solution Accepted" or a "Kudos" credit.

 

Heh, heh.

 

Thanks,

 

The Loon

Senior Designer/Cad Administrator
Inventor 2012, w/SP2
Dell Precision T3500, Intel Xeon CPU
W3680 @3.33GHz, 16.0 GB of RAM
Microsoft Windows 7 Pro, 64 Bit Edition
Version 2009, w/SP1
Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Announcements
Are You Going To Be @ AU 2014? Feel free to drop by our AU topic post and share your plans, plug a class that you're teaching, or simply check out who else from the community might be in attendance. Ohh and don't forgot to stop by the Autodesk Help | Learn | Collaborate booths in the Exhibit Hall and meet our community team if you get a chance!