Comments
Sort by recent activity
It's very simple.
Download CryptoLicensing (http://www.ssware.com/cryptolicensing/c ... ng_net.htm), install it, create an console project in Visual Studio and add the reference to LogicNP.CryptoLicensing.dll.
After, create a new SA 4/5 project and select the new console project .exe.
You'll see that SA 4/5 cannot read the CryptoLicensing assembly correctly, adding 3 assemblies in SA project file and show one empty item (item with no caption/text) on SA assembly dependencies list.
That's it. / comments
It's very simple.
Download CryptoLicensing (http://www.ssware.com/cryptolicensing/c ... ng_net.htm), install it, create an console project in Visual Studio and add the reference to LogicNP.CryptoLi...
Thank you!
I'm waiting for the new EAP.
Sorry I didn't make myself clear in older posts. / comments
Thank you!
I'm waiting for the new EAP.
Sorry I didn't make myself clear in older posts.
Using MandatoryPath doesn't work.
What happened is that SA doesn't recognize CryptoLicensing assembly correctly (the assembly is already obfuscated). It always found the assembly with wrong name.
If I use MadatoryPath with the AssemblyName = "LogicNP.CryptoLicensing, Culture=neutral, PublicKeyToken=4a3c0a4c668b48b4" I've got an error saying that the path assembly is not the same as its name. But, if I use AssemblyName = ", Culture=neutral, PublicKeyToken=null" SA founds the assembly but doesn't compile.
Since SA always rescan the dependencies I can't change project file to force to use the correct name; it always change the project creating 2 or 3 items with worng names in the SA project as I said before.
I'm still looking for a solution for this.
Thanks! / comments
Using MandatoryPath doesn't work.
What happened is that SA doesn't recognize CryptoLicensing assembly correctly (the assembly is already obfuscated). It always found the assembly with wrong name.
I...