-
Bug
-
Resolution: Resolved Locally
-
Highest
-
None
-
None
-
None
-
Windows 10 Build 1478.
-
Severity 2 - Major
After I've updated to source tree 2.5.5 it prompted me:
---------------------------
SourceTree.exe - This application could not be started.
---------------------------
This application requires one of the following versions of the .NET Framework:
.NETFramework,Version=v4.7.1
Do you want to install this .NET Framework version now?
---------------------------
Yes No
---------------------------
However I CAN'T install this .Net FW version because my Windows 10 version, which is controlled by my company, doesn't support this FW version.
Version 4.6.2 is the last supported by this windows 10 Build 1478.
https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements
Please, roll back the support for .Net 4.6.2 OR prompt-me to install a new dotnet version BEFORE upgrading source tree version, it's in an unusable state
- is duplicated by
-
-
- Closed
-
[SRCTREEWIN-8613] Source tree requires .NET 4.7.1 AFTER update
The originally reported issue was not about the conflict between .NET versions 4.7.1 and 4.7.2, but rather that requiring at least 4.7.1 excludes a large batch of users on early versions of Windows 10 from using the software. Our corporate systems lock us at a certain version of Windows on which .NET 4.7+ can't be installed.
https://docs.microsoft.com/en-us/dotnet/framework/get-started/system-requirements
So we're just moving on to other tools. If you'd like us to use Sourcetree, you should evaluate whether you really need to require .NET version 4.7+.
T Ngo
added a comment - Adding the two registry entries keys from the bottom of this page (see the known issues section) worked for me.
T Ngo
added a comment - Adding the two registry entries keys from the bottom of this page (see the known issues section) worked for me. This is due to a bug in a release of Windows 10 Insider Preview, this shoudl now be fixed in the latest releases.
Do not update the file.
SourceTree\SourceTree.exe.config
You should update the config in this file
SourceTree\<LatestVersion>\SourceTree.exe.config
Vinay Chandra
added a comment - - edited Do not update the file.
SourceTree\SourceTree.exe.config
You should update the config in this file
SourceTree\<LatestVersion>\SourceTree.exe.config
Elias Rincon
added a comment - You need to put only one supportedRuntime, this config solve my problem
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2"/>
</startup>
Elias Rincon
added a comment - You need to put only one supportedRuntime, this config solve my problem
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2"/>
</startup> Using the "SourceTree.exec.config" only prompts an error:
Patrick Skjennum
added a comment - - edited Using the "SourceTree.exec.config" only prompts an error:
If 4.7 is required, the change to Version=v4.7 that Paul mentioned would be the preferred fix so it will run on any version of 4.7 rather than just on the .1 minor release, but just as a guess I would say they're probably using a .NET Standard 2 library to code share with the Mac release, which requires targeting 4.7.1 or newer. If that's the case, they really do need to restrict to 4.7.1 or greater, and they will have to do it like this:
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.1"/>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7.2"/>
</startup>
Sometimes it's really surprising and disappointing the quality of releases that come out for SourceTree. I remember the weird animation issue that caused all the text to be blurred for 2-3 seconds every time you transitioned screens and it took several months for that to be fixed. My team's already moved away from Atlassian products except SourceTree, and we're all finding ourselves using GitKraken and GitExtensions a lot more these days, which is a shame. SourceTree is my favorite but I can't convince my team to use them when we keep having breaking workflow issues like this.
lukevp
added a comment - - edited If 4.7 is required, the change to Version=v4.7 that Paul mentioned would be the preferred fix so it will run on any version of 4.7 rather than just on the .1 minor release, but just as a guess I would say they're probably using a .NET Standard 2 library to code share with the Mac release, which requires targeting 4.7.1 or newer. If that's the case, they really do need to restrict to 4.7.1 or greater, and they will have to do it like this:
<startup>
<supportedRuntime version= "v4.0" sku= ".NETFramework,Version=v4.7.1" />
<supportedRuntime version= "v4.0" sku= ".NETFramework,Version=v4.7.2" />
</startup>
Sometimes it's really surprising and disappointing the quality of releases that come out for SourceTree. I remember the weird animation issue that caused all the text to be blurred for 2-3 seconds every time you transitioned screens and it took several months for that to be fixed. My team's already moved away from Atlassian products except SourceTree, and we're all finding ourselves using GitKraken and GitExtensions a lot more these days, which is a shame. SourceTree is my favorite but I can't convince my team to use them when we keep having breaking workflow issues like this.
This change also worked for me too
// edit file SourceTree.exe.config <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.7"/> </startup>
can we see this is captured in the next release
Typical Atlassian nonsense.