PathWave Licensing 9.16.x

Technical
1

Moving from 9.15.x to 9.16.x seems to break the development path and the PathWave Licensing package has to be added manually. Is this a bug or intentional?

1 Like
2

Hi Goran

image
image1372×173 10.3 KB

If you could use the latest version 9.16.4 , the problem would be resolved for you easily. If you need to use the 9.16.2 version , please update Package “Keysight Fixed License” to following version (Package Repository)

Please give it a try.

1 Like
3

OK, thanks. I have now tested with 9.16.4 and I get the same problem. I have to manually add ‘PathWave Licensing’ package to .csproj

4

Hi Goran,

It was nice you able to resolve the issue.
Just for me to understand how you resolve the
Did you use the Tag

<ItemGroup>
  <AdditionalOpenTapPackage Include="PathWave Licensing" />
</ItemGroup>

in your .csproj to install the “PathWave Licensing” to resolve it?

5

Yes, correct.
Why is this required in 9.16.x?

6

Hi Goran,

This look to be a regression introduced between Editor v9.16.2 (depending on PathWave Licensing) and Editor v9.16.3 (not depending on PathWave Licensing). I’ve reported this to the R&D team. For now you need to install PathWave Licesning manually.

BR
Witold

1 Like
7

Hi Goran,

I have confirmed that this is a regression. This will be fixed in the next release scheduled for end-February. In the meantime the workaround is to install PathWave Licensing manually.

BR
Witold

2 Likes