Autodesk-Forge / design.automation-csharp-revit.local.debug.tool

Design Automation for Revit Debug Tool:Run your Design Automation for Revit plugins locally with this tool
Other
26 stars 18 forks source link

Readme Clarity #4

Closed sanchez closed 4 years ago

sanchez commented 4 years ago

Hey I was wondering if you could clear some stuff for me that is noted in the README?

Line 53: so the design automation supports multiple input files but the local debugging does not support multiple files? (Is there currently a quick and easy work around for this issue?)

Line 29: Currently the automatic build deployment is pushing to AppData and not the ProgramData, should I be moving these files to ProgramData?

Thanks, Daniel

sanchez commented 4 years ago

I have also noticed the README references dotnet core but the samples are using dotnet framework, for debugging and design automation which dotnet version do we use?

anshivashankar commented 4 years ago

Hi @sanchez, thanks for reaching out. Sorry for the long delay, we typically are more responsive on Stack Overflow with the autodesk-designautomation tag, but I'll be sure to check here more often.

Line 53: so the design automation supports multiple input files but the local debugging does not support multiple files? (Is there currently a quick and easy work around for this issue?)

Correct. Unfortunately, there is no simple workaround. However, it should be straightforward when converting your app from local to Design Automation, please see the tutorial for Revit here: https://forge.autodesk.com/en/docs/design-automation/v3/tutorials/revit/step5-publish-activity/#step-1-create-a-new-activity

Line 29: Currently the automatic build deployment is pushing to AppData and not the ProgramData, should I be moving these files to ProgramData?

As far as I am aware, both are valid locations for Addins for Revit.

I have also noticed the README references dotnet core but the samples are using dotnet framework, for debugging and design automation which dotnet version do we use?

This is a typo, I'll fix it soon. We have used .NET Framework 4.8.

Please let me know if you have any more questions!

sanchez commented 4 years ago

That is all. Thank you for getting back to me