Error using CryptoLicensing

[MidSilence]

Hello!

I'm using CryptoLicensing with Smartassembly and I've got some errors.
In VS2008 design-time, referenced CryptoLicensing assembly works perfect and builds the project. I can see assembly details.
When using Smartassembly, it adds multiples assemblies in project as follows:

SA 4.2

[Alex.Davies]

Yes, it sounds like SA might be finding the wrong version of your assembly.

Try the latest EAP of SA 5.5, there have been lots of improvements in this area.
http://www.red-gate.com/MessageBoard/viewforum.php?f=116

If not, you can force which assembly to use using MandatoryPath. Details are here:
http://www.red-gate.com/supportcenter/Content.aspx?p=SmartAssembly&c=SmartAssembly/help/5.0/SA_SearchingForDependencies.htm&toc=SmartAssembly/help/5.0/toc1032210.htm
_________________
Alex
Developer,
Red Gate .NET Tools

[MidSilence]

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!

[slaphead99]

I'm a little confused as to why you are processing these third party, obfuscated, assemblies? What happens if you do not apply any smartassembly features to the third party assemblies?

[MidSilence]

It's very simple.
Download CryptoLicensing (http://www.ssware.com/cryptolicensing/cryptolicensing_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.

[Alex.Davies]

The CryptoLicensing assembly is invalid. It has two Assembly metadata items.

The next EAP will read the first Assembly metadata item instead of the second, the same as the CLR does. This means that you can process your assembly.
_________________
Alex
Developer,
Red Gate .NET Tools

[MidSilence]

Thank you!
I'm waiting for the new EAP.
Sorry I didn't make myself clear in older posts.