AutoCAD 2025 with .NET Framework plugin

[paul_mace]

I've read @_gile's migration guide (thanks to @Jeff_M for the translation) and I've noted @norman.yuan's comments about .NET Framework plugins possibly still working.
I've tried loading our plugin into 2025 and it doesn't work (it doesn't load - no errors, messages or anything).
So, I was just after some confirmation that, this fact that it doesn't load confirms that we will need to migrate to .NET 8? There isn't anything else to change or modify that might allow it to run correctly in 25? I've updated the series Max in the PackageContents xml file to 25.0.
If we do have to migrate, then fine. It's a bit of a pain as we support the current and three previous versions of AutoCAD. I just wanted to make sure there wasn't anything else that we could/should change to potentially make it work in 25 before we go ahead and migrate.

Thanks

Paul

[_gile]

Hi,

Didi you try to NETLOAD the DLL instead of using the Autoloader mechanism?

[paul_mace]

Yes I tried the netload too and it just doesn't do anything. As I said, no errors, warnings or messages of any kind.

[_gile · Accepted solution]

---

@paul_mace wrote:

Yes I tried the netload too and it just doesn't do anything. As I said, no errors, warnings or messages of any kind.

---

So it looks like you have to upgrage.

Anyway, I think it's a good practice to have a class implementing IExtensionApplication in your project at least to inform the user the plugin correctly loaded or not.

public class Initialization : IExtensionApplication
{
    public void Initialize()
    {
        AcAp.Idle += OnIdle;
    }

    private void OnIdle(object sender, EventArgs e)
    {
        var doc = AcAp.DocumentManager.MdiActiveDocument;
        if (doc != null)
        {
            AcAp.Idle -= OnIdle;
            try
            {
                // Do the initilization stff here
                doc.Editor.WriteMessage("\nThe plugin correctly loaded.\n");
            }
            catch (System.Exception ex)
            {
                doc.Editor.WriteMessage($"\nError: {ex.Message}\n");
            }
        }
    }

    public void Terminate()
    { }
}

[paul_mace]

OK, thanks. It's pretty clear that our plugin has loaded when it does but I take your point.

[waga.asanka]

I've developed several plugins for my organization, and users have reported that while the plugin built with .NET 4.8.1 for Civil 3D 2024 works with Civil 3D 2025, they have to run 'netload' every time they start using it. Can anyone suggest a solution for this?

[_gile]

---

@waga.asanka  a écrit :

I've developed several plugins for my organization, and users have reported that while the plugin built with .NET 4.8.1 for Civil 3D 2024 works with Civil 3D 2025, they have to run 'netload' every time they start using it. Can anyone suggest a solution for this?

---

How were the plugins automatically loaded?

• If you use the Autoloader mechanism with a .bundle folder, you have to edit the "SeriesMax" attribute value in the PackageContents.xml folder: SeriesMax="R25.0".
• If you use the registry way, you have to copy the keys of your Applications in the corresponding "R25.0" key.

[waga.asanka]

@_gile 

thanks for the reply, I will try this and get back to you.

[ceethreedee.com]

@_gile .. yep setting the series max to "25.0" works... very nice!!