Topic: C# Code to Open AutoCAD (Existing Instance Issue)

[Bill Tillman]

I've been using this VB.NET code to check for existing instance of AutoCAD and use it or open a new one if none exists:

Code: [Select]

Dim vAcadApp As AcadApplication
        Dim vAcadDoc As AcadDocument
Try
            If Process.GetProcessesByName("acad").Length > 0 Then
                vAcadApp = GetObject(, "AutoCAD.Application.19")
            Else
                vAcadApp = New AcadApplication
            End If
            vAcadApp.Visible = True
            vAcadApp.WindowState = AcWindowState.acMax
            vAcadDoc = vAcadApp.Documents.Open(DwgPath & DwgName, True)I need to convert this over to C# and so far I've only got this part working:

Code: [Select]

using System;
using AutoCAD;

    class LaunchAutoCAD1
    {
        public static void StartACAD(string vFilename)
        {
            AcadApplication vAcadApp;
            AcadDocument vAcadDoc;
            try
            {
                vAcadApp = new AcadApplication();
                vAcadApp.Visible = true;
                vAcadApp.WindowState = AcWindowState.acMax;
                vAcadDoc = vAcadApp.Documents.Open(vFilename,true);
            }
            catch (Exception ex)
            {
                Console.WriteLine(ex.Message);
                Console.ReadKey();
            }
        }
    }

This works but unfortunately I seem to be having touble with the GetObject method to check if AutoCAD is already running. I've searched and searched and keep finding only VB.NET code or the same question by someone else which no one ever answered. Any advice would be appreciated.

[Jeff H]

Make the C# purist cringe and add a reference Microsoft.VisualBasic assembly then

Code - C#: [Select]

1.             Microsoft.VisualBasic.Interaction.GetObject(Class: "AutoCAD.Application.19");
2.  

There are some other useful ones in VB namespace

Code - C#: [Select]

1.             Microsoft.VisualBasic.FileIO.FileSystem.CopyDirectory("C:\\Old", "C:\\New");
2.  

           

[Keith Brown]

You might try Marshal.GetActiveObject Method.

[Bill Tillman]

Jeff H .... I know what you mean. I ran this through a VB to C# converter on line and that's what it came up with. Unfortunately this is a true VB.NET to C# conversion and there are some politics involved here (office politics) so taking any approach that leaves even the slightest bit of visual Basic in the new code will just defeat the purpose of converting in the first place. The VB.NET code has run rock solid for two years now but we have to move this over to C#.....because!

[MickD]

System.Diagnostics.Process.GetProcessesByName might be worth a look too -

http://msdn.microsoft.com/en-us/library/z3w4xdc9(v=vs.110).aspx

Although I don't see what all the fuss is about
Changing a solid code set from VB.net to C# just to change syntax is just inviting a chance for new bugs, I know you have little say in this but compiling the old code into its own dll and using it as a lib for use with new code would save a lot of work and headache IMO.
It's giving someone a job I guess