Completed
Last Updated: 18 Mar 2021 13:28 by ADMIN
Mihail
Created on: 13 Aug 2020 14:25
Type: Bug Report
2
DebugWindow host configuration is not respected when the process is started
When the ports with which the DebugWindow should operate are changed in the DebugWindow host configuration the process is started with the default values instead of the new values.
5 comments
ADMIN
Ivo
Posted on: 18 Mar 2021 13:28

Hello Sean,

It was pleasure for me to assist you. Wish you a great day.

Regards,
Ivo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Sean
Posted on: 17 Mar 2021 15:29
I can confirm that this worked.  Thank you!
ADMIN
Ivo
Posted on: 17 Mar 2021 10:36

Hello Sean,

In the very first beta release of the DebugWindow feature, it uses the configuration file to set up the endpoint ports. Later we have changed the approach in order to be able to assign dynamically the ports depending on the running Visual Studio instances, but we forgot to remove the endpoints section in the service host configuration. It is an obvious defect that could easily lead to confusion and needs to be fixed.

Probably the next reasonable question would be: It is fine, but how can I change the ports then?

Currently, the DebugService service port configuration is controlled via Windows registry, you can use DebugWindowPortRangeStart and DebugWindowPortRangeEnd DWORD registry values to configure the port range. Both values should be entered by hand under HKCU\Software\Telerik\JustMock and should allow at least 4 values (equal to the number of the exposed services per host instance), see below:

Please verify inside Visual Studio Output Pane that the newly entered port range is accepted and the background service process is started successfully:

In the near future, we will expose a dedicated UI for this purpose, but for now, this is the only way to do so.

I hope you find this information helpful. Do not hesitate to contact us if there is something unclear.

Regards,
Ivo
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Sean
Posted on: 16 Mar 2021 22:11

This is still happening.

JustMock Version R1 2021

 

Edited this line:

<endpoint address="net.tcp://localhost:10001/TraceEventsPublishingService" binding="netTcpBinding" bindingConfiguration="TcpBinding" contract="Telerik.JustMock.DebugView.Service.Model.ITraceEventsPublishingService" />

to use port 10005:

<endpoint address="net.tcp://localhost:10005/TraceEventsPublishingService" binding="netTcpBinding" bindingConfiguration="TcpBinding" contract="Telerik.JustMock.DebugView.Service.Model.ITraceEventsPublishingService" />

but the process is still using port 10001

 

ADMIN
Mihail
Posted on: 02 Feb 2021 12:14

Hi,

The fix is available with R3 SP1 2020 release and all the latest versions.

Regards,
Mihail
Progress Telerik

Virtual Classroom, the free self-paced technical training that gets you up to speed with Telerik and Kendo UI products quickly just got a fresh new look + new and improved content including a brand new Blazor course! Check it out at https://learn.telerik.com/.