Editing CAD Files in a Loop

[plant1]

Hello,

I want to edit some CAD Files in a Loop. I am opening the files with the following .net-command:

Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.Open(sCADFiles[i],false);

When I try to edit the opened files I get an elockviolation Error!

When I try to read readonly flag it is set to false!

Anybody an Idea?

Kind Regards

Karl-Heinz

[jimt]

This is a C# routine that I use to open all of the files in a folder.

// Application Session Command with localized name
        [CommandMethod("CommandGroup", "CommandName", "LocalCommandName", CommandFlags.Modal | CommandFlags.Session)]
        public void ExportDWG()
        {
            string strPath = "";

            strPath = BrowseFolder();  //Routine that shows dialog and returns path to a folder
            // Process the list of files found in the directory.
            string[] fileEntries = Directory.GetFiles(strPath, "*.dwg");
            foreach (string strFileName in fileEntries)
            {
                //Only Process Files that end with .DWG
                if (strFileName.EndsWith(".DWG", StringComparison.OrdinalIgnoreCase))
                {
                    Database acadDB = new Database(); 
                    //Open Drawing File
                    acadDB.ReadDwgFile(strFileName, FileShare.ReadWrite, true, "");
                    Transaction acadtrans = acadDB.TransactionManager.StartTransaction();
                    try
                    {
                        // Place Code Here
                        acadtrans.Commit();
                    }
                    catch (Autodesk.AutoCAD.Runtime.Exception)
                    {
                        acadtrans.Abort();
                    }
                    finally
                    {
                        acadtrans.Dispose();
                        acadDB.Dispose();
                    }
                }

            }
            
        }

[pjohnson.137155]

One of the key items in the code shown is that the CommandFlags.Session attribute is set to session.

Just thought i would point that out


Patrick K Johnson
http:\\www.cadenhancement.com