What version of Visual Studio for this project?

[Anonymous]

I just installed the Revit API. Tried to compile this:

Custom Exporter to XML 

Custom Exporter to XML

and got many error messages.

TIA,

-Ramon F. Herrera
JFK Numbers

[RPTHOMAS108 · Accepted solution]

Looks like Revit 2014 (.Net 4.0 there was no change that year, changed to 4.0 for 2013 I believe).

The icon of the .sln file indicates: VS 2010. You can just upgrade it, the errors will be due to changes in the API since.

[Anonymous]

---

@RPTHOMAS108 wrote:

Looks like Revit 2014 (.Net 4.0 there was no change that year, changed to 4.0 for 2013 I believe).

I think the icon of the .sln file gives the game away: VS 2010. You can just upgrade it.

---

Yes, my icon says "2010". However, my VS-2017 chokes with namespaces, etc. I will go to the office where I have a PC running 2010 and another running 2013 to see what happens.

Thanks!

-Ramon

JFK Numbers

[RPTHOMAS108 · Accepted solution]

Was able to build it in 2013 for 2020, file attached.

Had to comment out the following as it is no longer valid:

//public void OnDaylightPortal( DaylightPortalNode node )
//{
//}

Apparently a lot has changed with the exporter since this was written so not sure if the results will be as desired.

[Anonymous]

---

@RPTHOMAS108 wrote:

Was able to build it in 2013 for 2020, file attached.

Had to comment out the following as it is no longer valid:

//public void OnDaylightPortal( DaylightPortalNode node )
//{
//}

Apparently a lot has changed with the exporter since this was written so not sure if the results will be as desired.

---

Do you mind trying to build the Exporter to XML?

I am so frustrated, that am considering using the Navisworks API instead.

-Ramon
JFK Numbers

[RPTHOMAS108 · Accepted solution]

It builds but it doesn't run, probably a required value is not set somewhere. This is an old file and they've changed the rendering mechanism in Revit since, there were a lot of changes to IExporter for that at the time.

[RPTHOMAS108]

@Anonymous  this seem to be working now, code was pointing to a hardcoded output path.

[Anonymous]

---

@RPTHOMAS108 wrote:

@Anonymous  this seem to be working now, code was pointing to a hardcoded output path.

---

Thomas: I downloaded and built your Custom Exporter Collada in VS-2017.

The only change needed was switching to Target .NET Framework to 4.7.1

Thanks!

-Ramon
JFK Numbers