Maintain For Mutiple Version Dynamo Package Publish

[chuongmep]

If this is an issue for Dynamo Core, please submit your issue on the Dynamo Core issues page or if this is an issue for Dynamo for Revit, please post your issue on the Dynamo for Revit Issues page.

If this issue is not a Wishlist request, please check the Dynamo forum, and start a thread there to discuss your issue.

What improvement/feature would you like to see in Dynamo?

I would like to see something that can clearly define loading and define versions similar to the definition when creating a plugin in revit. This problem will be serious if packages are not properly maintained and cause errors when publishing to dynamo package, then I want to maintain my package to support lower revit versions. How? It's confusing and they make me stop developing support packages in dynamo instead of addins, consider this. Because if not, the only way I can do it now is to put them on github and develop run each installation file.

How would you see this improvement/feature working?

one xml defind something like that:

<ApplicationPackage SchemaVersion="1.0.0" AppVersion="1.0.0" ProductCode="57C26AE0-0AB6-40C5-9EC6-3D1C2A5FB397">
<RuntimeRequirements OS="Win64" Platform="Revit" SeriesMin="R2020" SeriesMax="R2023" />

<Components Description="2020">
<RuntimeRequirements OS="Win64" Platform="Revit" SeriesMin="R2020" SeriesMax="R2020" />
<ComponentEntry AppName="Fammer" ModuleName="Contents/2020/RevitAddin.addin"></ComponentEntry>
</Components>
<Components Description="2021">
<RuntimeRequirements OS="Win64" Platform="Revit" SeriesMin="R2021" SeriesMax="R2021"/>
<ComponentEntry AppName="Fammer" ModuleName="Contents/2021/RevitAddin.addin"></ComponentEntry>
</Components>
<Components Description="2022">
  <RuntimeRequirements OS="Win64" Platform="Revit" SeriesMin="R2022" SeriesMax="R2022"/>
  <ComponentEntry AppName="Fammer" ModuleName="Contents/2022/RevitAddin.addin"></ComponentEntry>
</Components>
  <Components Description="2023">
    <RuntimeRequirements OS="Win64" Platform="Revit" SeriesMin="R2023" SeriesMax="R2023"/>
    <ComponentEntry AppName="Fammer" ModuleName="Contents/2023/RevitAddin.addin"></ComponentEntry>
  </Components>
</ApplicationPackage>

Please provide any sketch/mock-up or video of your requested improvement/feature

(Fill in here)

[Amoursol]

@saintentropy thoughts on the above?

[erfajo]

There is a serious problem concerning the package manager and having the same package for parallel versions. This was one of the reasons why I left using the package manager years ago. However, over the years have I also recognized that it is very complex if the package manager should be able to handle this situation.

One thing is handling different versions numberings, another ball game is handling all the assemblies. My package contains 12 assemblies and 10 xml files for every version (I maintain packages for the last four Revit versions)

Just as an idea if the package manager should be able to work with parallel versions. On the upload side, should it be manageable to upload package content towards a specific version (or range of versions) under the same package name but with individual version numbers. Meaning that it should be doable to hold several editions of the same package under a shared package name targeting specific Dynamo/Revit versions. On the download side, should a user be able to download from inside a dynamo version and get the exact package meant for that version. It would be a good thing if several versions could be installed at the time, but this is where it gets tricky, how should a given open Dynamo app know of the existence of other Dynamo versions!? For my package do users download an executable for each version, so I have neither solved that issue.

Lastly, If I ever should return using the package manager should I be able to upload using something like Github Desktop or from inside Visual Studio, AND I should be able to control versioning etc. No restrictions should be applied by the package repository.