TSVN update notification not working, nightly builds missing

[Tobias Knauss]

TSVN does not notify about updates anymore, as you can see from the "current version" in the following dialog:

Also, I found that there are no more nightly builds available, most likely because the build log also says "BUILD FAILED".

[Stefan]

On Sunday, September 30, 2018 at 1:43:52 PM UTC+2, Tobias Knauss wrote:

TSVN does not notify about updates anymore, as you can see from the "current version" in the following dialog:

That's strange. The version.txt file was updated properly:

https://tortoisesvn.net/version.txt

 

Also, I found that there are no more nightly builds available, most likely because the build log also says "BUILD FAILED".

I fixed the code so it compiles again. the next nightly build should be available again.

Stefan

[Tobias Knauss]

Am Sonntag, 30. September 2018 20:49:19 UTC+2 schrieb Stefan:

On Sunday, September 30, 2018 at 1:43:52 PM UTC+2, Tobias Knauss wrote:

TSVN does not notify about updates anymore, as you can see from the "current version" in the following dialog:

That's strange. The version.txt file was updated properly:

https://tortoisesvn.net/version.txt

 

Is this information cached somewhere locally inside TSVN?

Still wrong value in the notification dialog.

[Stefan]

no, there's no cache in TSVN. Especially not for that. Using URLDownloadToFile API for this:

https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms775123(v=vs.85)

Stefan

[Tobias Knauss]

no, there's no cache in TSVN. Especially not for that. Using URLDownloadToFile API for this:

https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms775123(v=vs.85)

Stefan

After talking to our IT department, they tested TSVN on a new computer and the update notification worked.

So I did more tests like bypassing the proxy server of our network, but the update still failed.

Then I checked which destination address was used in both cases:

With proxy, TSVN connections came no further than to the proxy.

Without proxy, TSVN connected to 52.29.122.124 (aws-eu-central-01.ostyserver.net). When opening this address in Firefox, I got a certificate failure, saying

"52.29.122.124 verwendet ein ungültiges Sicherheitszertifikat. Das Zertifikat gilt nur für folgende Namen: www.visualsvn.com, visualsvn.com"

Looks like the Visual Studio Plugin "Visual SVN" somehow changed the address where TSVN looks for updates.

You maybe want to call them and complain.

How can I fix that?

I already checked some registry keys, I found:

[HKEY_CURRENT_USER\Software\TortoiseSVN]
"NewVersionLink"="http://tortoisesvn.net"
"NewVersionText"="A new version of TortoiseSVN is available. Please go to http://tortoisesvn.net to get it."
"NewVersion"="1.9.7.27907"
Actually I don't understand why you save the content of your version.txt there. Is this the problem maybe?

EDIT:

After more searching I found:

[HKEY_LOCAL_MACHINE\SOFTWARE\TortoiseSVN]
"UpdateCheckURL"="http://www.visualsvn.com/visualsvn/download/tortoisesvn/version-5.1.txt"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TortoiseSVN]
"UpdateCheckURL"="http://www.visualsvn.com/visualsvn/download/tortoisesvn/version-5.1.txt"

Stupid VisualSVN!!! I want my money back!...

Now you definitely may want to call them and complain.

Which is the correct URL for these reg keys?

[Stefan]

On Tuesday, October 9, 2018 at 4:45:21 PM UTC+2, Tobias Knauss wrote:

no, there's no cache in TSVN. Especially not for that. Using URLDownloadToFile API for this:

https://docs.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms775123(v=vs.85)

Stefan

After talking to our IT department, they tested TSVN on a new computer and the update notification worked.

So I did more tests like bypassing the proxy server of our network, but the update still failed.

Then I checked which destination address was used in both cases:

With proxy, TSVN connections came no further than to the proxy.

Without proxy, TSVN connected to 52.29.122.124 (aws-eu-central-01.ostyserver.net). When opening this address in Firefox, I got a certificate failure, saying

"52.29.122.124 verwendet ein ungültiges Sicherheitszertifikat. Das Zertifikat gilt nur für folgende Namen: www.visualsvn.com, visualsvn.com"

Looks like the Visual Studio Plugin "Visual SVN" somehow changed the address where TSVN looks for updates.

You maybe want to call them and complain.

How can I fix that?

I already checked some registry keys, I found:

[HKEY_CURRENT_USER\Software\TortoiseSVN]
"NewVersionLink"="http://tortoisesvn.net"
"NewVersionText"="A new version of TortoiseSVN is available. Please go to http://tortoisesvn.net to get it."
"NewVersion"="1.9.7.27907"
Actually I don't understand why you save the content of your version.txt there. Is this the problem maybe?

That's where the update check function stores the latest info it gets from the server, so the update notification can be read without network access in the commit dialog.

 

EDIT:

After more searching I found:

[HKEY_LOCAL_MACHINE\SOFTWARE\TortoiseSVN]
"UpdateCheckURL"="http://www.visualsvn.com/visualsvn/download/tortoisesvn/version-5.1.txt"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\TortoiseSVN]
"UpdateCheckURL"="http://www.visualsvn.com/visualsvn/download/tortoisesvn/version-5.1.txt"

And this is where Admins can redirect the update check:

https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-admins-upgradecheck.html

Which is the correct URL for these reg keys?

just delete those registry keys (the HKLM ones) and TSVN will use the default again.

Stefan