Our application is a closed source commercial application that a user must log in with an account in order to use, however the installer for this application is freely available on our website. Is this considered permitted use or are we required to protect the assemblies?

So just to be very clear with the updated documentation, my issue previously was with the Powershell scripts not running and protecting the DLLs, that step was what causes difficulty. The only way I could get around it was to have Telerik support run the protection step for me and get the protected DLLs that way.

With the updated policy if I am using the NoXaml binaries from nuget, can I redistribute them with my Commercial WPF applications without having to run the Powershell scripts?

Thanks,

Eoin 

Please implement this for the next release. We had our build server set up to run the necessary batch files so we could just check in the latest Telerik code and have the NuGet packages built automatically, but since the introduction of .NET Core support the build fails in new ways each release and manual intervention is required so we end up spending several hours each new release just to get our licensed NuGet packages built. There is no reason we should be responsible for building these DLLs.

I badly need a simple non-intrusive way to authenticate build DLL's. Half of what I create are plugins for Autodesk software. Upgrading an existing project to a Telerik solution prevents my DLL's from loading into AutoCAD entirely and probably various others I haven't got around to trying yet. I can manually attach a reference and it runs great on my dev machine, but only on my dev machine. So, I have really cool and expensive tools, but if I can't use them in many of my frequently created projects. What's the point of having expensive and (theoretically) time-saving toys when you can't easily show them off? 

 

I'll probably create a ticket about this after some more tinkering, but I suspect this will be a nightmarish solution and it seemed like great example of why this topic does require attention. 

It would be great to have such feature to protect dll's.  its difficult to always keep eye's on privacy of software in the continuous releases. any solution would be really helpful.

 

Thanks,

Sarathi J

 

I agree, it would be nice to get closer to a one click solution where possible. Especially since the process is repeatable between releases and re-distribution is an important part of an application release, this process should be simplified.

Thanks,

Eoin