Help to troubleshoot windows form in .NET dll

Anonymous — Fri, 05 Feb 2016 19:45:12 GMT

Greetings,

I work in an engineering group that manages six manufacturing buildings. Using VB.NET I have written some tools for use in AutoCAD which do the following:

- When invoked, a windows form is displayed which allows a user to select (via checkboxes) which level of a building and which disciplines are of interest. Then clicking "OK" x-references the selected files together into a single drawing.

- Each building has its own tool. They are nearly identical; in fact, I wrote the app for one building and simply copied/pasted to write code for the other buildings by simply changing the paths to the various drawings and changing checkbox names etc.

Engineers in our department are using a variety of desktop and laptop computers and all are using AutoCAD2015. The automation works perfectly for everyone except for one user. And for him, all of the tools for the various buildings work fine except for one.

For one building, for one user, the windows form which should display when the command is invoked won't display. He gets what appears to be a separate ACAD session which is labeled "Form1" (normal behavior), but it is a blank session and the form itself doesn't display.

Again, other apps which are written the exact same way work fine; the forms display when the command is invoked.

Other users are able to get the selection forms to initiate for all building apps.

Everyone is using the same dll file and invoking the command from the cui.

Just one user, just one building's attachment app; the windows form won't display.

I'm going nuts to figure out what's wrong. Can anyone suggest anything? Any ideas for a likely cause?

Thank you,

Erik

Re: Help to troubleshoot windows form in .NET dll

SENL1362 — Fri, 05 Feb 2016 20:06:53 GMT

There are a lot of reasons to think of.
Last year my program works great for all users except one. Searching, debugging, small test programs didn't gave me a solution. A few weeks ago another user failed. Again searching, a small WriteMessage program worked but as soon WPF's and ToolPalettes nothing goes. Long story short: .NET Frameworks was to blame. Upgrade to 4.5 and problem solved.
Also have a look to another threat of Alex with his save problem.
So i suggest try with smaller test programs to isolate the problem.

Good luck

topic Help to troubleshoot windows form in .NET dll in .NET Forum

Help to troubleshoot windows form in .NET dll

Re: Help to troubleshoot windows form in .NET dll