netload does not load dll
I had an issue like that. There is some resource, etc. that that machine is lacking that causes a failure (unhandled exception) in your code and thus it won't load. Since you don't have VS on that pc to do debugging, what I did was create some temp debugging statements in the dll that printed status messages to the editor at key points in the code. e.g. "Stage 1 passed". That helps narrow down where in your code the error is occurring. You could also include something similar in your Try..Catch statements. If you are not using Try..Catch, you could be getting errors and not knowing it. In my case, I still had some legacy vba stuff that I was loading at startup and on some pc's, the vba enabler never got installed.
Also, since the dll is loading on an event, it behaves a little differently than manually loading it. When you manually load it, the event is not firing, thus your code doesn't execute. So the dll could be loading but not executing. You could also create a command that runs the delegate that the event calls. That way you could test it manually.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
Kelvin,
Thanks for requesting clarification. So when I said "it behaves", I didn't mean the dll load process, but code execution. My first suggestion addressed the possiblity that a runtime error in the Initialize method prevented the dll from loading. The second suggestion addressed the the possiblity that the dll did load, but without any observable effect.
Since the OP didn't post any code, I have to make some assumptions. Yes, the code in the Initialize method would run, but I don't know what that might be, if any. This is the statement I was addressing:
@Anonymous wrote:
even explicitly issuing the netload command and grabbing the dll manually does not work.
It sounded like he expected the code that runs in the dwg open event, to work when he netloaded it. So I was pointing out that the open event would not fire at that point. Therefore, it may only appear that the dll didn't load successfully. To test the code that runs in an event, he could create a command method that calls it, provided that any requirements that the code needs to run are met. Looking back, I also see I may not have understood one part. It appears that the problem dll is possibly being called from another dll during the dwg open event. That doesn't necissarly imply that any other action is happening upon dwg open. So we really have no clear idea what's going on until they provide more details. Until then, everybody's just throwing out ideas.
Thanks again.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
When you say, "it works"or "it doesn't work", we have no idea what that means. Think "here's what I think should happen" and "here's what actually happens" and then provide the details. Yes you can netload the dll, but what do you expect to happen after netload finishes? (note the side discussion on whether you have code in the Initialze method). If it loaded successfully, you should be able to see its commands listed if you run "ARX C". If not, you need to find ways to debug your code. If you can't run VS on the problem pc to do an actual debugging session, then you can code in some "progress markers" or other indicators of code execution. Even using a messagebox here and there works to display some status info.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
It may be possible, but you have to start testing and ruling out what you can. Why couldn't it be a problem with your code/dll? Try creating a test dll that just pops a message box that says "Hello World". Don't use the command line as that depends on references. If something simple works, you know its not file access rights. It could be something like that pc has acad installed differently and the mgd files can't be found.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
The suggestions I offered are a whole lot quicker than uninstall/reinstall. Give it a try. Until you verify through testing that the problem is NOT with your code, you're spinning your wheels testing the OS.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
I thought you were the programmer. Accurate information is important for troubleshooting. Think of it like working on a car. If your car doesn't start, what you you do first? Start replacing spark plugs, air filter and fuel filter, or run some diagnostic test to get information? Friday my son called me, his motorcycle had stalled. I could hear him cranking the starter and the battery was going dead. So we set out getting a new battery. It was late and we couldn't get one, so I brought the old one home and charged it hoping it would last long enough for him to get home. It cranked but the bike still wouldn't start. Then I found out it went dead because he had been cranking on it trying to get it started again. Wish he had told me that at first. Once I had some accurate info, I traced it to a disconnected vacuum line. Troubleshooting is all about getting good information. Since you aren't a programmer you may have missed it, but the suggestions I gave you are way to get info you wouldn't normally get. Like plugging in an engine analyser. Even though the dll works fine on most pc's, its still possible that the code can fail on one. The code uses the pc's resources. If it uses them improperly or if the resources aren't available, then the code fails. You're looking for some setting to be different on that pc, but you realize that something on that pc is different. That something could be a resource that the code depends on. The only way to know is to do some diagnosting testing. In the programming world, we call that debugging.
BTW, if you do get a simple dialog to display, that tells you that the basic framework is ok. The problem must lie with the dll that won't work. More thorough debugging would be required. In the car analogy, that's like eliminating a lot of possible problems by first checking for spark to see if its an electrical problem or a fuel problem.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
It would be interesting to see if it works.
Ed
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
How to post your code.
Please FULLY describe the problem you ran into. For example, when you said:
"MYCOMMAND" doe NOT return "Hello World",,,
Not returning what you expected, is just one of the possible symptoms that show "it does not work". Once you issued "MYCOMMAND" command, if the "Hello World" is not shown, does AutoCAD shows "Unknown command" (or something like that), of nothing at all (very unlikely, but according to your description, it seems the case?).
Does your DLL implement IExtenseionApplication interface? If yes, do you have proper try...catch exclosed the code in Initialize(). If not, exception in Innialize() would fail loading the DLL assembly (then, when you enter command MYCommand", you should get AutoCAD prompt for "unknown command").