Skip to content

Conversation

@DharmishthaVPatel
Copy link
Contributor

@DharmishthaVPatel DharmishthaVPatel commented Dec 18, 2025

As part of

Ensure the SMCU hyperlink to Launch RavenDB Studio (while in maintenance mode) points to RavenDB Studio on localhost.

@ramonsmits
Copy link
Member

Why not just host RavenDB always on localhost? The hostname is more meant for SC API'sl, I don't see why the RavenDB api should be remotely accessible by everyone

@DharmishthaVPatel DharmishthaVPatel marked this pull request as draft December 18, 2025 16:59
@DharmishthaVPatel DharmishthaVPatel force-pushed the ravendb-custom-host-name-bug-fix branch from 6ed16e7 to 51211ca Compare December 19, 2025 01:30
@DharmishthaVPatel DharmishthaVPatel marked this pull request as ready for review December 19, 2025 05:05
@DharmishthaVPatel DharmishthaVPatel merged commit 1a75511 into master Dec 20, 2025
62 checks passed
@DharmishthaVPatel DharmishthaVPatel deleted the ravendb-custom-host-name-bug-fix branch December 20, 2025 18:24
@cquirosj cquirosj added this to the 6.8.1 milestone Dec 23, 2025
@cquirosj cquirosj added the Bug label Dec 23, 2025
cquirosj added a commit that referenced this pull request Dec 23, 2025
# Fix RavenDB Management Studio link binding issue

## Summary
This PR fixes a property name mismatch introduced in PR #5237 that caused the RavenDB Management Studio hyperlink to be grayed out and non-functional in the ServiceControl Management UI.

## Problem
After merging PR #5237 "Point RavenDB Management Studio link to localhost", the RavenDB Management Studio link in the Advanced Options maintenance mode section became unresponsive. The link appeared grayed out and clicking it had no effect.

## Root Cause
PR #5237 renamed the property from `StorageUrl` to `RavenDbStudioUrl` in `ServiceControlBaseService.cs`, but the corresponding ViewModel property in `ServiceControlAdvancedViewModel.cs` was incorrectly named `RavenStudioUrl` (missing "Db"). This property name mismatch caused the WPF data binding to fail.

## Solution
- Fixed property name in `ServiceControlAdvancedViewModel.cs` from `RavenStudioUrl` to `RavenDbStudioUrl`
- This ensures proper binding between the ViewModel and the underlying ServiceControlInstance property

## Files Changed
- `src/ServiceControl.Config/UI/AdvancedOptions/ServiceControlAdvancedViewModel.cs`

## Testing
- RavenDB Management Studio hyperlink now appears as an active blue link
- Clicking the link properly opens the RavenDB Studio at `http://localhost:{port}/studio/index.html#databases`
- Right-click context menu "Copy to Clipboard" functionality works correctly

Fixes issue introduced in #5237
cquirosj added a commit that referenced this pull request Dec 24, 2025
# Fix RavenDB Management Studio link binding issue

## Summary
This PR fixes a property name mismatch introduced in PR #5237 that caused the RavenDB Management Studio hyperlink to be grayed out and non-functional in the ServiceControl Management UI.

## Problem
After merging PR #5237 "Point RavenDB Management Studio link to localhost", the RavenDB Management Studio link in the Advanced Options maintenance mode section became unresponsive. The link appeared grayed out and clicking it had no effect.

## Root Cause
PR #5237 renamed the property from `StorageUrl` to `RavenDbStudioUrl` in `ServiceControlBaseService.cs`, but the corresponding ViewModel property in `ServiceControlAdvancedViewModel.cs` was incorrectly named `RavenStudioUrl` (missing "Db"). This property name mismatch caused the WPF data binding to fail.

## Solution
- Fixed property name in `ServiceControlAdvancedViewModel.cs` from `RavenStudioUrl` to `RavenDbStudioUrl`
- This ensures proper binding between the ViewModel and the underlying ServiceControlInstance property

## Files Changed
- `src/ServiceControl.Config/UI/AdvancedOptions/ServiceControlAdvancedViewModel.cs`

## Testing
- RavenDB Management Studio hyperlink now appears as an active blue link
- Clicking the link properly opens the RavenDB Studio at `http://localhost:{port}/studio/index.html#databases`
- Right-click context menu "Copy to Clipboard" functionality works correctly

Fixes issue introduced in #5237
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants