Build 4.1.925.5 requires a new key Follow
My 4.0 key as not recognized after installing build 925. I did not try reentering the key, I just started the 30-day free evaluation with 925.
Was this intentional?
Please sign in to leave a comment.
Hello,
4.0.1 should accept 4.0 license keys.
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”
In case anyone else runs into this, I too have noticed that starting around 923 I am being asked to re-enter my key, but that when I do so my key is in fact being accepted.
As an aside, these builds also start generating .4.1.resharper files in my solution folders, alongside my previous .4.0.resharper files, which seems both wasteful (given that they have no content differences) and odd in terms of numbering (given that we are talking about 4.0.1, not 4.1.)
Serge Baltic wrote:
>> My 4.0 key as not recognized after installing build 925. I did not try
>> reentering the key, I just started the 30-day free evaluation with
>> 925.
I had to re-enter my license key as well.
/jwh
Hello,
That (failure to upgrade the existing license key) was fixed.
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”
Hello,
It happened to be "ReSharper 4.0.1" v4.1. The title reads 4.0.1, but technically
we had to advance the DLL version number because of the binary incompatibility.
The solution settings file has a version number in its name to avoid conflicts
when running several R# versions on the same solution. As the components'
settings format evolves, the settings file contents changes. Running ReSharpers
of different versions in turn would result in changes to the solution file,
which is inacceptible when it's stored in the SCC.
—
Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”