Please, excuse us for any inconvenience or misunderstanding. We will do our best to answer your questions:1) Nevron thinks its acceptable to break properly licensed projects built with older Nevron toolkits just by installing the new toolkit?
No, our intention is not to break properly licensed projects. The current licensing model is based on a per developer (individual developer) using the Software for development purposes and per production web server deployment (for web based applications). Each developer who desires to use the Software must hold a valid Developer License. We are providing 3 type of licenses with the Vision for .NET products:
- Developer License – required for developing with the components.
- Server License – required for production web server deployment.
- Desktop License – required for redistribution of compiled desktop applications.
Each Developer License comes with one production Server License and one Desktop License by default. The controls are royalty free for redistribution with compiled desktop (WinForm and WPF) applications.
For web based applications - if you need to deploy your web application to multiple production web server, you need to obtain additional Server Licenses. There is no restrictions on the number of application per server, no restriction on the number of websites and no restrictions on the number of server CPUs. We do not charge for test servers.
The Developer and Server licenses are bound to specific machine IDs. Developer Licenses will unlock the product, removing the evaluation watermark and will allow debugging. The Desktop license will not work when you run the app in debug mode on another development machine.
For your nee development machine, you can simply request a license transfer. Your new Developer license will be activated based on the new development machine ID.2) Because your licensing is so strict why should I recommend to any of my clients to evaluate the Nevron toolkit knowing its going to break my projects when they do? I apparently should never consider building a development tool with it since a developer might want to use Nevron toolkits for their own projects. Is that how you'd have me to believe?
You can use Nevron components to build compiled applications. If you are building development tools using Nevron, your users will be considered developers and will have to obtain Developer license keys. If your users need to evaluate a development tool, which uses Nevron components, you can request an evaluation extension license key from Nevron to distribute with your project.3) I uninstalled the toolkit (as that's the only thing I can think of to tell a client) via the control panel and the same problem remains. Apparently, once installed my PC is broken forever. How do I truly uninstall the toolkit and repair the licensing impact its had on my PC? Is my new Win10 PC broken forever?
No, your new machine is not broken. It looks like you are running the development project on your new machine and you currently don’t have a valid Developer license for this machine. Once we activate your new Developer license you should not have problems.
If you are running a compiled desktop application (redistribution), the Desktop license key will take care of the licensing.
To completely remove Nevron from your new machine, you should uninstall from control panel -> programs and features, as well as clean any Nevron assemblies from the GAC. Depending on the version of .NET Framework, the assemblies in the GAC may not be visible from Windows Explorer and you can use a free tool like GAC Browser
to search and remove such assemblies.
Let us know if you have any questions or if there is anything we can assist you with.
Nevron Support Team