SHP Import Locking .shp file

[mordend]

I want to be able to delete the .shp after importing it.

Attached code works but it leaves the .shp as read only until CAD closes. Am I missing something?

private void ImportShape(FileInfo file)
        {
            Stopwatch sw = new Stopwatch();
            sw.Start();
            MapApplication mapApp = HostMapApplicationServices.Application;
            using (Importer importer = mapApp.Importer)
            {
                importer.Init("SHP", file.FullName);

                string fileName = Path.GetFileNameWithoutExtension(file.FullName).Replace(" ", "");

                foreach (InputLayer inputLayer in importer)
                {
                    inputLayer.SetLayerName(LayerNameType.LayerNameDirect, fileName);
                    inputLayer.SetDataMapping(ImportDataMapping.NewObjectDataOnly, fileName);

                    inputLayer.Dispose();
                }

                importer.ImportPolygonsAsClosedPolylines = true;

                ImportResults result = importer.Import(true);

                sw.Stop();
                Quest_Common.ed.WriteMessage(string.Format("\n{0} object(s) imported in {1} sec(s)", result.EntitiesImported.ToString(), sw.Elapsed.Seconds));

                importer.Dispose();
            }

            file.Delete();
        }

[mordend]

I want to be able to delete the .shp after importing it.

Attached code works but it leaves the .shp as read only until CAD closes. Am I missing something?

private void ImportShape(FileInfo file)
        {
            Stopwatch sw = new Stopwatch();
            sw.Start();
            MapApplication mapApp = HostMapApplicationServices.Application;
            using (Importer importer = mapApp.Importer)
            {
                importer.Init("SHP", file.FullName);

                string fileName = Path.GetFileNameWithoutExtension(file.FullName).Replace(" ", "");

                foreach (InputLayer inputLayer in importer)
                {
                    inputLayer.SetLayerName(LayerNameType.LayerNameDirect, fileName);
                    inputLayer.SetDataMapping(ImportDataMapping.NewObjectDataOnly, fileName);

                    inputLayer.Dispose();
                }

                importer.ImportPolygonsAsClosedPolylines = true;

                ImportResults result = importer.Import(true);

                sw.Stop();
                Quest_Common.ed.WriteMessage(string.Format("\n{0} object(s) imported in {1} sec(s)", result.EntitiesImported.ToString(), sw.Elapsed.Seconds));

                importer.Dispose();
            }

            file.Delete();
        }

[Alfred.NESWADBA]

Hi,

have not tried your code, but see one issue with that:

If you use the using statement like that

using (Importer importer = mapApp.Importer)
   {
   }

then do not call

importer.Dispose()

 Because using(.....){...} includes importer.Dispose at the end of {...}

- alfred -

[Alfred.NESWADBA]

Hi,

have not tried your code, but see one issue with that:

If you use the using statement like that

using (Importer importer = mapApp.Importer)
   {
   }

then do not call

importer.Dispose()

 Because using(.....){...} includes importer.Dispose at the end of {...}

- alfred -

[norman.yuan · Accepted solution]

AFAIK, this has been a known issue for years, but I have not tried to see if it is fixed in later version after AutoCAD Map/Civil 2015.

[norman.yuan · Accepted solution]

AFAIK, this has been a known issue for years, but I have not tried to see if it is fixed in later version after AutoCAD Map/Civil 2015.

[mordend]

I'm aware that the using statement calls dispose when it's closed, and that is the point of it.

I had it in there to see if it made any difference. But thank you for pointing it out.

[mordend]

I'm aware that the using statement calls dispose when it's closed, and that is the point of it.

I had it in there to see if it made any difference. But thank you for pointing it out.

[mordend · Accepted solution]

So testing in 2017 it is still an issue.

But good news is that it seems to be fixed in 2020. YAY!!!

Thanks Norman.

[mordend · Accepted solution]

So testing in 2017 it is still an issue.

But good news is that it seems to be fixed in 2020. YAY!!!

Thanks Norman.