Writing a 3dm File using Visual Studio C#

Replies to This Discussion

Permalink Reply by David Rutten on October 7, 2015 at 4:08am

I've never used this particular API, but your approach does seem strange. Why is the file variable called nurbssurface? Surely the surface is going to go inside the file, along with potentially many other shapes?

I'll look around in the SDK to see if it makes sense to me.

Permalink Reply by David Rutten on October 7, 2015 at 4:23am

Using the Rhino.FileIO namespace from within Grasshopper seems to work fine. I do not know however to what extend the functionality is available if you do not have RhinoCommon loaded. I imagine a lot of the geometry types actually aren't available, because they require the Rhino core. 

Attachments:

• writefile.gh, 2 KB

Permalink Reply by Henry Jarvis on October 7, 2015 at 6:33am

Hi David,

Thank you so much for the reply! I was missing the step that involved adding the objects to the object table. From what I understand all the objects in the table (or the table itself?) are then passed to the file3dm.Write() Method when it's used? Turns out it will work in the Visual Studio IDE perfectly well like this, Now I'm just sorting out the best way to create a surface.

If I can ask one more question, what does file.Polish() do?

using System;

using System.Collections.Generic;

using System.Linq;

using System.Text;

using System.Threading.Tasks;

using Rhino.Geometry;

using Rhino.FileIO;

using Rhino.Collections;

using Rhino;

namespace NurbsExample

{

class Program

{

static void Main(string[] args)

{

string output = "C:/WorkingFileExample.3dm";

RunScript(output);

}

private static void RunScript(string path)

{

File3dm file = new File3dm();

file.Polish();

for (int j = 0; j<=10; j++)

{

file.Objects.AddLine(new Line(j, 0, 5 - j, 5 + j, 0, j));

}

File3dmWriteOptions options = new File3dmWriteOptions();

options.SaveAnalysisMeshes = false;

options.SaveRenderMeshes = false;

options.SaveUserData = true;

file.Write(path, options);

}

}

}