Duplicate licenses

I was wondering as to the logic that is employed when duplicate licenses are detected on the network.

Currently the 2nd instance of R# remains working while the 1st instance is prompted to enter a new license or disable.

Surely it would make more sense to leave the 1st instance running and prevent the 2nd instance from starting, prompting them for a new license.

This is most annoying on our network when we have someone entering a license on a newly built machine and entering another persons license. The legitimate user is disabled while the new one is able to work just fine..

Thanks.

4 comments
Comment actions Permalink

Hello alastair,

on the other hand, let's figure out that you're running ReSharper on your
('first') machine and you've just logged into another ('second') machine
on the network and launched VS with ReSharper. In this case you would certainly
prefer the second instance to work, since it is the instance you are likely
going to work with. Given that the second machine may be your home computer
connected via VPN into the network, and the first machine is
your workstation, and there may be no easy way to shut down ReSharper on
the first machine (e.g. if it cannot be connected to with Remote Desktop),
the choice to leave the newly launched instance running looks quite reasonable.


Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


I was wondering as to the logic that is employed when duplicate
licenses are detected on the network.

Currently the 2nd instance of R# remains working while the 1st
instance is prompted to enter a new license or disable.

Surely it would make more sense to leave the 1st instance running and
prevent the 2nd instance from starting, prompting them for a new
license.

This is most annoying on our network when we have someone entering a
license on a newly built machine and entering another persons license.
The legitimate user is disabled while the new one is able to work just
fine..

Thanks.



0
Comment actions Permalink

Yes, yes. Please don't change this behavior :-p

"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8945d18548c96bfb5c80ee0e@news.intellij.net...

Hello alastair,

>

on the other hand, let's figure out that you're running ReSharper on your
('first') machine and you've just logged into another ('second') machine
on the network and launched VS with ReSharper. In this case you would
certainly prefer the second instance to work, since it is the instance you
are likely going to work with. Given that the second machine may be your
home computer connected via VPN into the network, and the first machine is
your workstation, and there may be no easy way to shut down ReSharper on
the first machine (e.g. if it cannot be connected to with Remote Desktop),
the choice to leave the newly launched instance running looks quite
reasonable.



0
Comment actions Permalink

I would prefer to be asked to shut down either instance and be given the
choice. This is somewhat frustrating for me because I have a desktop
computer that uses a domain account and a notebook computer that is not part
of the domain and I often switch between the two. Since ReSharper assumes
the two are different users with the same license, it most often prompts to
close the wrong instance (e.g. I'm developing on my notebook and login to my
desktop to test with domain authentication or I'm developing on my desktop
and login to my notebook to test anonymous authentication). Currently, I
have to close Visual Studio, switch computers, then restart Visual Studio in
the right order. I actually use the same username on both computers, but one
is DOMAIN\User and the other is COMPUTER_NAME\User.

--


"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8945d18548c96bfb5c80ee0e@news.intellij.net...

Hello alastair,

>

on the other hand, let's figure out that you're running ReSharper on your
('first') machine and you've just logged into another ('second') machine
on the network and launched VS with ReSharper. In this case you would
certainly prefer the second instance to work, since it is the instance you
are likely going to work with. Given that the second machine may be your
home computer connected via VPN into the network, and the first machine is
your workstation, and there may be no easy way to shut down ReSharper on
the first machine (e.g. if it cannot be connected to with Remote Desktop),
the choice to leave the newly launched instance running looks quite
reasonable.

>
>

Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>
>
>> I was wondering as to the logic that is employed when duplicate
>> licenses are detected on the network.
>>
>> Currently the 2nd instance of R# remains working while the 1st
>> instance is prompted to enter a new license or disable.
>>
>> Surely it would make more sense to leave the 1st instance running and
>> prevent the 2nd instance from starting, prompting them for a new
>> license.
>>
>> This is most annoying on our network when we have someone entering a
>> license on a newly built machine and entering another persons license.
>> The legitimate user is disabled while the new one is able to work just
>> fine..
>>
>> Thanks.
>>
>



0
Comment actions Permalink

Hello Lothan,

we've got such an idea but it's not easy to do technically. For now, every
launched instance of VS with ReSharper listens to the network
and shuts down when duplication license on another machine is discovered.
So it is the first instance who reveals that there are duplicate licences.
At the moment of its launch, the second instance is actually unaware of this.
In order for it to become aware of the license violation, it should broadcast
its license data so that other instances could receive it and respond. This
protocol just looks too complex - for instance, should it wait (and,
if yes, for how long) for responses or should it continue to run until the
responses are received and violation is discovered? Moreover, in order to
distinguish between the first and the second instances, a sort of timestamps
(when each instance was launched) will be necessary. This makes
things a bit complicated.

Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


I would prefer to be asked to shut down either instance and be given
the choice. This is somewhat frustrating for me because I have a
desktop computer that uses a domain account and a notebook computer
that is not part of the domain and I often switch between the two.
Since ReSharper assumes the two are different users with the same
license, it most often prompts to close the wrong instance (e.g. I'm
developing on my notebook and login to my desktop to test with domain
authentication or I'm developing on my desktop and login to my
notebook to test anonymous authentication). Currently, I have to close
Visual Studio, switch computers, then restart Visual Studio in the
right order. I actually use the same username on both computers, but
one is DOMAIN\User and the other is COMPUTER_NAME\User.



0

Please sign in to leave a comment.