Topic: Interop at startup

[Chris K]

I have two .dll's that are loaded via netload from acad.lsp.  They each have
command methods that are accessed from lisp.  One functions correctly the
other does not.  However, both function correctly after the startup of
AutoCAD is complete (outside of Acad.lsp).  The only difference, from a
programming standpoint, is that one dll uses InteropServices the other does
not.  Does anyone know of issues with interop at startup?  I can post code
if anyone wants to give it a closer look.

[Jeff_M]

S.W.A.G.---->>>> Try using acaddoc.lsp since it loads later in the load cycle. Or, place the loading in the registry. I have an application that uses Interops and have never had a problem with it loading this way.

[Chris K]

Jeff_M thanks for the feedback.  Forgot to mention I've tried Acaddoc.lsp
and the registry.  Same effect.  Sounds like it's something else I'm not
seeing, considering you've done the same with success in the past.  Below
is a list of the external references I'm using, maybe this with help.

Code: [Select]

using Autodesk.AutoCAD;
using Autodesk.AutoCAD.ApplicationServices;
using Autodesk.AutoCAD.DatabaseServices;
using Autodesk.AutoCAD.Geometry;
using Autodesk.AutoCAD.Interop;
using Autodesk.AutoCAD.Runtime;
using acApp = Autodesk.AutoCAD.ApplicationServices.Application;
using lispTools = IMFTUtilities.AcadUtilities.LispTools;

using System;
using System.Collections.Generic;
using System.Data;
using System.Data.OleDb;
using System.Data.Common;
using System.Runtime.InteropServices;
using System.Text;
using System.Windows.Forms;
using sysMetadata = System.EnterpriseServices.Internal.GenerateMetadata;

One other thing I've noticed.  It only happens for the first drawing loaded
in a session.  For all subsequent drawings the .dll works perfectly.  This seems
to make sense, since the .dll is already loaded into memory. Any additional thoughts,
this one has really got me stumped?

[It's Alive!]

are you implementing IExtensionApplication ?

[sinc]

Chances are good that we will not be able to help you with this unless you can post some code.

[Chris K]

Daniel,

Originally I was, but I thought that may have been the problem so I have a non-IExtension version that I've been working with lately.

are you implementing IExtensionApplication ?

[Chris K]

Sinc,

I can appreciate that.  Below is a .zip of the project with the required database in the IMFTLayerMaker folder.  The .mdb needs to be in a folder in the AutoCAD support search path.  The Lisp syntax for the use of IMFTLayerMaker is as follows:

Code: [Select]

(imftlayerdef '("Mview" ""))  ;;; 'Mview' is the layername and '' is the layerstatus..... '("33" "e") is another example

This should return a dotted list containing the layer setting info for layer "Mview".

Hope this helps.  If anything else is needed just let me know.  Any help is appreciated.

Chances are good that we will not be able to help you with this unless you can post some code.

[Glenn R]

Loading via lisp is too late for most things you need to do at startup with the 'higher/lower' level languages. This sort of thing is really a matter of 'when' in the startup order.

I'll try and look at your code over the next few days and see what's what. However, I have to ask, why are you using AutoCAD's Interop from a .NET application...you rarely if ever have to resort to this.

Also, unless I missed it in my brief scan of this thread, you haven't mentioned the following important pieces of information:

AutoCAD version you're targetting.
.NET Framework version you're targetting.
Visual Studio version (or whatever else IDE you're using).

[Chris K]

Glenn, sorry.  Acad 2009, DotNet 2.0 and VS2005.  I'm using interop to retrieve the file support file search path, there may be a better way, but this is the only way I know.  Still a bit green at this.

Loading via lisp is too late for most things you need to do at startup with the 'higher/lower' level languages. This sort of thing is really a matter of 'when' in the startup order.

I'll try and look at your code over the next few days and see what's what. However, I have to ask, why are you using AutoCAD's Interop from a .NET application...you rarely if ever have to resort to this.

Also, unless I missed it in my brief scan of this thread, you haven't mentioned the following important pieces of information:

AutoCAD version you're targetting.
.NET Framework version you're targetting.
Visual Studio version (or whatever else IDE you're using).

[Glenn R]

Chris, that helps alot - thanks.

However, my apologies - I neglected some other info I and others would need:

You mentioned something wasn't working - this generally signifies an error. What, if any, errors are you getting?
Also, without looking at your zip file and the only code you've posted 'in this thread' is 'Using' statements, I don't know what language you're using...?

Also, can you explain, what your application does, particularly why you need to use 'Interop' for certian parts (one dll as opposed to the other)?

[Chris K]

I'm using C# and the errors returned are below.  Also, I haven't been able to run in debug mode because the only error only occurs with the first drawing loaded of a session.  My inexperience is hurting me on this one.  Thanks for the help.  I'll remember what to include in the future.

Error#1
   ---------------------------
   GetLayerPropertiesDS
   ---------------------------
   System.Runtime.InteropServices.COMException (0x800401E3): Operation unavailable (Exception from HRESULT: 0x800401E3 (MK_E_UNAVAILABLE))
      at System.Runtime.InteropServices.Marshal.GetActiveObject(Guid& rclsid, IntPtr reserved, Object& ppunk)
      at System.Runtime.InteropServices.Marshal.GetActiveObject(String progID)
      at IMFTUtilities.AcadUtilities.MiscTools.Preferences.GetSupportPaths()
      at IMFTUtilities.AcadUtilities.MiscTools.Misc.IMFTFindFile(String pFilename)
      at IMFTLayerMaker.LayerMaker.GetLayerPropertiesDS()
   ---------------------------
   OK   
   ---------------------------


Error #2
   ---------------------------
   GetLayerDefinition
   ---------------------------
   System.NullReferenceException: Object reference not set to an instance of an object.
             at IMFTLayerMaker.LayerMaker.GetLayerDefinition(String& pLayerName, String& pLayerStatus)
   ---------------------------
   OK   
   ---------------------------

Chris, that helps alot - thanks.

However, my apologies - I neglected some other info I and others would need:

You mentioned something wasn't working - this generally signifies an error. What, if any, errors are you getting?
Also, without looking at your zip file and the only code you've posted 'in this thread' is 'Using' statements, I don't know what language you're using...?

Also, can you explain, what your application does, particularly why you need to use 'Interop' for certian parts (one dll as opposed to the other)?

[Glenn R]

Another thing I should have asked for:

What OS are you running this on Chris?

[Chris K]

I'm running XP 32-bit, SP2 on a Dell Optiplex GX620, 2GB, GeForce FX8500. 

Another thing I should have asked for:

What OS are you running this on Chris?

[Glenn R]

Are you using GetObject/GetActiveObject in your code and if so, why?

[Glenn R]

You're using this:

Code: [Select]

// Cast the current autocad application from .net to COM interop
Autodesk.AutoCAD.Interop.AcadApplication oApp;
oApp = (Autodesk.AutoCAD.Interop.AcadApplication)Marshal.GetActiveObject("AutoCAD.Application.17.2");

in a dll that runs INSIDE AutoCAD! You only need to use this construct if you're hooking into AutoCAD from an external process. This is a not the way to do what you want as you're ALREADY running inside AutoCAD in the first place!

You also go on to use this:

Code: [Select]

// Get the user preferences on the current profile
                AcadPreferences profile = oApp.Preferences;

                // Configure the default preferences
                try
                {
                    strPaths = oApp.Preferences.Files.SupportPath;
                    strPaths = System.IO.Directory.GetCurrentDirectory() + ";" + strPaths;
                    return strPaths;
                }
                catch (acRuntime.Exception e)
                {
                    MessageBox.Show(e.Message, "IMFTUtilities.ACADUtilities.Preferences.GetSupportPaths");
                    return string.Empty.ToString();
                }

when you could have ignored all that guff and just used this:

Code: [Select]

oApp = acApp.AcadApplication as AcadApplication;
string strPath = oApp.Preferences.Files.SupportPath;

It's late here and I'm tired, but that's pretty much how I remember it.