I cannot be the only one who is lost here ... but this is what I see when I try to get Fiddler.
"Fiddler4" is built for .NET 4, but installs as Fiddler2, and was just released "last month" (updated)
"Fiddler2" is build for .NET 2, and installs as Fiddler2, and was just released "last month" (updated)
"Fiddler2 Beta" is built for .NET 2, but says it is the upcoming version, but installs as just "Fiddler".
This is ... very confusing. Is there any chance we can get a clean, ironed out version in the future?
"Fiddler4" is built for .NET 4, but installs as Fiddler2, and was just released "last month" (updated)
"Fiddler2" is build for .NET 2, and installs as Fiddler2, and was just released "last month" (updated)
"Fiddler2 Beta" is built for .NET 2, but says it is the upcoming version, but installs as just "Fiddler".
This is ... very confusing. Is there any chance we can get a clean, ironed out version in the future?
3 Answers, 1 is accepted
0
Hi, Stacey--
Fiddler versioning is pretty simple with only one quirk. That quirk is that the major version determines whether it targets the v2 CLR (Fiddler v2.x) or the v4 CLR (Fiddler v4.x).
For instance, Fiddler 2.4.9.3 and Fiddler 4.4.9.3 are the same code targeting different CLRs.
For simplicity, Fiddler always uses the term "Fiddler2" for file-system folders and registry keys; this allows extensions that work in both versions to be installed identically.
Regards,
Eric Lawrence
Telerik
Fiddler versioning is pretty simple with only one quirk. That quirk is that the major version determines whether it targets the v2 CLR (Fiddler v2.x) or the v4 CLR (Fiddler v4.x).
For instance, Fiddler 2.4.9.3 and Fiddler 4.4.9.3 are the same code targeting different CLRs.
For simplicity, Fiddler always uses the term "Fiddler2" for file-system folders and registry keys; this allows extensions that work in both versions to be installed identically.
Regards,
Eric Lawrence
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Graeme
Top achievements
Rank 1
Rank 1
answered on 19 Aug 2014, 09:04 AM
Just out of interest; what is the advantage of having versions that use different CLRs?
0
Hello, Graeme--
The only advantage is that this allows Fiddler to work. :-)
Seriously though, prior to Windows 8, many users only have a v2 CLR and thus need a version of Fiddler that targets v2; we don't want to force them to download the whole v4 CLR to run Fiddler. Windows 8 and later users may not have a v2 CLR and only have a v4 CLR. Due to breaking changes in the .NET Framework (specifically around the JavaScript.Net libraries), the v2 version of Fiddler will not run on the v4 CLR.
The v4 build also unlocks a few other features, including higher-performing lock objects, the ability to enable TLS1.1/1.2 and miscellaneous other tiny things.
Regards,
Eric Lawrence
Telerik
The only advantage is that this allows Fiddler to work. :-)
Seriously though, prior to Windows 8, many users only have a v2 CLR and thus need a version of Fiddler that targets v2; we don't want to force them to download the whole v4 CLR to run Fiddler. Windows 8 and later users may not have a v2 CLR and only have a v4 CLR. Due to breaking changes in the .NET Framework (specifically around the JavaScript.Net libraries), the v2 version of Fiddler will not run on the v4 CLR.
The v4 build also unlocks a few other features, including higher-performing lock objects, the ability to enable TLS1.1/1.2 and miscellaneous other tiny things.
Regards,
Eric Lawrence
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.