Message 1 of 3
Corrupted .NET DLL files
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Wondering if anyone had a similar experience and could explain how this problem fixed itself.
- Distributed an updated macro written in VB.NET as a DLL to be loaded with NETLOAD. The user copied the updated DLL file to the correct location under C:\ProgramData\Autodesk\ApplicationPlugins which obviously overwrote the existing file.
- Macro was running fine for a month
- Macro crashed on Wednesday. Crash meaning that Civil 3D disappeared without warning and the standard Autodesk error report dialog appeared. I believe Autodesk refers to this as a "quick exit". :). The typical .NET assembly error dialog did not appear.
- Rebooting the computer, restarting Civil 3D, even going back to an old copy of the DWG could not get the macro working properly again. The macro would load and work for a while but the act of switching stations to work on a particular section view would eventually cause a crash.
- The user had kept the files I sent him and re-copied the DLL file to the correct location under ApplicationPlugins.
- The macro is now running properly again.
The only thing I can think of is that it is possible for the assembly to be corrupted in the GAC and the above step #5 fixed the problem somehow. But I am not familiar enough with how that all works to say for sure and it doesn't explain the exact timing of the crash, stepping one by one to a particular section view or jumping directly to the specific station would cause the crash. And the problem would occur in different drawings as well.