Fix all-users addin manifest path for Revit 2027+

[tay0thman]

Fix all-users addin manifest path for Revit 2027+

Problem

Revit 2027 changed how all-users add-in manifests are discovered. The previous three paths behave as follows:

fixed #3275

Path	Revit 2027 Behavior
%ProgramData%\Autodesk\Revit\Addins\2027	Ignored — journal says "won't be loaded"
C:\Program Files\Autodesk\Revit 2027\AddIns\	Rejected — reserved for signed internal add-ins only
C:\Program Files\Autodesk\Revit\Addins\2027	Works — new shared third-party location

The current GetRevitAddonsFolder() builds the second path (install-dir based) for 2027+ --allusers attachments, which Revit rejects with "not signed as internal addin".

Revit 2027 journal explicitly states:

Add-in manifest file from: C:\ProgramData\Autodesk\Revit\Addins\2027\pyRevit.addin, won't be loaded. All-users Add-in manifest files must be installed to: C:\Program Files\Autodesk\Revit\Addins\2027

Fix

Simplified GetRevitAddonsFolder() in RevitAddons.cs to use the correct shared path for Revit 2027+:

C:\Program Files\Autodesk\Revit\Addins\<year>

Removed the RevitProduct.ListInstalledProducts() registry lookup which was building the wrong base path.

Changed files

• dev/pyRevitLabs/pyRevitLabs.TargetApps.Revit/RevitAddons.cs — core path fix
• Updated binary files (bin/, bin/netcore/, bin/netfx/)

Testing

• pyrevit attach <clone> default --installed --allusers places manifest at C:\Program Files\Autodesk\Revit\Addins\2027\
• Revit 2027 loads pyRevit tab successfully from the new path (no signing errors)
• Revit 2026 and earlier still use %ProgramData% path (unchanged)
• Per-user path (%APPDATA%) unchanged for all versions
• pyrevit env shows correct attachment info for all Revit versions (2023–2027)

[devloai]

Unable to trigger custom agent "Code Reviewer". You have run out of credits 😔
Please upgrade your plan or buy additional credits from the subscription page.

[tay0thman]

@jmcouffin minor fix, but a copilot review still welcomed.

[jmcouffin]

Please wait before merging. I need to validate actual wip do not work with Revit 2027.

[Copilot]

Pull request overview

Updates pyRevit’s Revit add-in manifest placement logic to match Revit 2027+’s new all-users discovery rules, ensuring --allusers attachments are written to the shared third-party location that Revit 2027 actually loads.

Changes:

• Simplified RevitAddons.GetRevitAddonsFolder() to route Revit 2027+ all-users manifests to C:\Program Files\Autodesk\Revit\Addins\<year>.
• Removed the install-dir/registry-based path construction for Revit 2027+ all-users attachments (now uses the fixed shared location).
• Updated shipped binaries (bin/netfx, bin/netcore) to reflect the code change.

Reviewed changes

Copilot reviewed 1 out of 5 changed files in this pull request and generated 2 comments.

File	Description
dev/pyRevitLabs/pyRevitLabs.TargetApps.Revit/RevitAddons.cs	Adjusts all-users add-in manifest folder logic for Revit 2027+ to the new shared location.
bin/netfx/pyRevitLabs.TargetApps.Revit.dll	Rebuilt binary containing the updated add-ins path logic (net48).
bin/netcore/pyRevitLabs.TargetApps.Revit.dll	Rebuilt binary containing the updated add-ins path logic (net8.0-windows).

[tay0thman]

Please wait before merging. I need to validate actual wip do not work with Revit 2027.

I won't merge anything.

[jmcouffin]

@tay0thman did some tests + reviewed, logic seems fine.
Please address the copilot comments if you can, then OK to merge.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 5 changed files in this pull request and generated 1 comment.

[tay0thman]

@jmcouffin I pushed a new commit

[tay0thman]

@jmcouffin these DLL conflicts are sticky, can you compile them when merging?