Is there an existing issue for this?
What happened?
An upgrade from DNN 10.3.3 to 10.4.0 stopped at 50% during CheckAssembliesForRegistration. Owin.dll has FileVersion 1.0. Upgrade.EnsureAssembliesRegistered uses version.ToString(3), which throws an ArgumentException for a System.Version with only major and minor components.
Assembly registration should handle valid two-component file versions without aborting the upgrade.
Steps to reproduce?
Minimal .NET reproduction:
new System.Version("1.0").ToString(3);This reproduces the version-formatting exception, not a complete DNN upgrade.
Upgrade scenario inferred from the affected installation (not separately reproduced on a clean site):
- Start with DNN 10.3.3 and an unregistered Owin.dll in bin whose FileVersion is 1.0.
- Upgrade to DNN 10.4.0 using the official installation package and upgrade wizard.
- Assembly registration attempts to format the two-component version with ToString(3).
Current Behavior
Upgrade stops at 50% during CheckAssembliesForRegistration with an ArgumentException (fieldCount).
Expected Behavior
Assembly registration accepts valid two-component file versions and completes the upgrade.
Relevant log output
Argument must be between 0 and 2.
Parameter name: fieldCount
Anything else?
Affected version: DNN 10.4.0 (upgrade target). The form currently only offers 10.3.3 and develop; 10.3.3 is selected as the source version of this upgrade, not as the version containing the new failure.
Suggested correction: normalize missing build/revision components before formatting, or use an existing safe version-formatting helper. Check other callers with the same assumption.
Related assembly registration work:
Please confirm whether this case is already tracked and whether a fix is planned.
Affected Versions
10.3.3 (latest release)
What browsers are you seeing the problem on?
No response
Code of Conduct
Is there an existing issue for this?
What happened?
An upgrade from DNN 10.3.3 to 10.4.0 stopped at 50% during CheckAssembliesForRegistration. Owin.dll has FileVersion 1.0. Upgrade.EnsureAssembliesRegistered uses version.ToString(3), which throws an ArgumentException for a System.Version with only major and minor components.
Assembly registration should handle valid two-component file versions without aborting the upgrade.
Steps to reproduce?
Minimal .NET reproduction:
This reproduces the version-formatting exception, not a complete DNN upgrade.
Upgrade scenario inferred from the affected installation (not separately reproduced on a clean site):
Current Behavior
Upgrade stops at 50% during CheckAssembliesForRegistration with an ArgumentException (fieldCount).
Expected Behavior
Assembly registration accepts valid two-component file versions and completes the upgrade.
Relevant log output
Anything else?
Affected version: DNN 10.4.0 (upgrade target). The form currently only offers 10.3.3 and develop; 10.3.3 is selected as the source version of this upgrade, not as the version containing the new failure.
Suggested correction: normalize missing build/revision components before formatting, or use an existing safe version-formatting helper. Check other callers with the same assumption.
Related assembly registration work:
These do not establish a fix for this specific formatting failure.
Please confirm whether this case is already tracked and whether a fix is planned.
Affected Versions
10.3.3 (latest release)
What browsers are you seeing the problem on?
No response
Code of Conduct