DeployLX 4.1 r4474 Nightly Build supports .NET 4.0

Mon, 28 Jun 2010 19:09:01 GMT

We now have official full support for .NET 4.0 available in the nightly builds. This update includes runtime support for DeployLX CodeVeil code encryption features and better support for the updated .NET 4.0 runtime security model for all redistributable components.

Download Nightly Build

DeployLX 4.0 R4463 Released

Tue, 15 Jun 2010 01:20:20 GMT

This release addresses a number of edge cases and potential deadlocks discovered after the initial release of DeployLX 4.0. It also marks a step closer to full .NET 4.0 support.

Highlights

Minor usability updates and fixes to the Network Licensing system.
Stability issues in DeployLX application.
Fix problems with built in HTML Help using the disqus.com comment system.
Complete change log

Download Release Version

.NET 4.0 Support

We've been hard at work brining full .NET 4.0 runtime compatibility. Most of the work has been completed but is still being tested.

Download the latest experimental release

NOTE: The experimental release will overwrite any previous installs. You will need to completely uninstall the experimental release to restore the GA version.

Additional Samples

Two additional samples have been posted to demonstrate the use of DeployLX Licensing in a Windows Application and an ASP.NET application.

Licensed Windows Application Starter Kit

Licensed ASP.NET Application Starter Kit

.NET 4.0 Experimental Support

Sun, 30 May 2010 03:12:20 GMT

Experimental support for .NET 4.0 is now available.

Download it now

Supports runtime encryption for the 4.0 runtime
Supports new security settings for the 4.0 runtime.

Support for .NET 4.0

Mon, 19 Apr 2010 20:54:45 GMT

What about .NET 4.0?

Official support for .NET 4.0 will be announced a few weeks following the official release of .NET 4.0. Currently the Licensing component works without issues against the .NET 4.0 Release Candidate. The Code Encryption feature of the CodeVeil Component is not stable in applications running under the .NET 4.0 runtime.

Every time Microsoft releases a major system update for the .NET runtime we have to re-vet the entire runtime executive injected by CodeVeil. Each time it takes a few weeks to a couple months to rework with all the unpublished and undocumented changes that Microsoft has made to the core runtime. Our customers of course want 4.0 support so it is an urgent matter for us to get 4.0 compatibility as well.

DeployLX v4.0 Released

Wed, 21 Apr 2010 22:07:47 GMT

Subscribe Product Releases - Subscribe to receive notices about product updates.

Highlights

Windows 7 Support
Brand new Network Licensing support local, branch and remote network support including disconnected clients.
Hundreds of end user enhancements including better instructions, easier navigation, reduced prompts and others.
New Feature limit to support named features enabled by serial number or extension code.
New Feature Filter limit to enable or disable child limits based on enabled features.
New Type limit to filter license support based on licensed type.
New Reset limit to reset time and use state based on the success of other limits. Enables renewable grace periods.
New State limit to enforce different rules based on the state of other rules.
New Remote Desktop limit to control use over remote desktop sessions.
New Online limit to enable different rules based on Internet connectivity.
Dozens of system stability and compatibility enhancements for CodeVeil.
FIPS compliance.
Show license forms at any time to extend a license prematurely, enter a new serial number, activate on demand, etc.
Change Log

Compatibility with 3.x Licensing Runtime

This release can be used as a complete replacement for version 3.x. It is backwards compatible except for a few very specific breaking changes. Existing licenses can be validated with the new runtime license without change. License servers upgraded to the new 4.x runtime can validate and authorize 3.x licenses without change.

Update 4/21: A recent change to the bug tracking software has made all tags private resulting in an empty list of breaking changes. A clone of the list has been published as a backup.

What about .NET 4.0?

I Have an Assurance Contract, Where's My License?

Valid assurance contract holders will receive a private email with instructions on how to obtain their free covered upgrade. Make sure your account is up to date so that the instruction email is delivered to the right address.

I Have a 3.x License and Want to Upgrade

If you purchased on or after Feb 5, 2010 you will receive a complimentary upgrade. Look for an email from us in the next 2 weeks with instructions on how to obtain your upgrade.

To purchase an upgrade, contact sales with your current serial numbers to request a quote.

DeployLX v4.0 Release Candidate

Sun, 21 Mar 2010 14:44:11 GMT

It's finally here. We've been working hard to improve the developer experience and user experience with the DeployLX suite of applications.

Highlights

Reworked the Network Licensing system.
Windows 7 Compatibility.
Hundreds of end user enhancements including better instructions, easier navigation, reduced prompts and others.
4 Additional limits.
Limit filters to adjust rules based on the state of other limits.
Improved system compatibility.
FIPS Compliance.
Show license forms at any time after validation.
Breaking Changes

Change Log

Part of the new development efforts involved integrating a bug tracking/feature tracking system into our development process. We tried FogBugz, AxoSoft and finally settled on what we liked best - YouTrack by the same folks that make ReSharper.

You can find a complete change log for DeployLX on our YouTrack site.

What about .NET 4.0?

Getting the Release Candidate

The evaluation version of the 4.0 Beta can be downloaded directly from our site.

If you've purchased DeployLX 3.x you'll find the release version of the beta in your account downloads.

Final Release Date

Pending any major security flaws discovered in the release candidate, DeployLX 4.0 will be released for General Availability Monday April 5, 2010.

DeployLX 3.2 R3813 Released

Sun, 28 Feb 2010 19:56:29 GMT

Maintenance release. Some customers reported receiving Invalid Program exceptions with then encrypted version of the licensing runtime. The fix was discovered some time ago, but applied only to the 4.x release. The fix has been back ported and incorporated into the final 3.x release.

See the complete change log.

To download the update select Help | Check for Updates in the DeployLX Manager, or visit the My Account section of the website to download authorized installers.

DeployLX 3.2 R3751 Released

Sun, 28 Feb 2010 19:56:56 GMT

This is the final release of the 3.x line and includes a few minor usability enhancements and back-ports of fixes made to the new 4.x beta.

Experimental Support for Windows 7.
Fixed module load exception in Windows Server 2008 x64 with Kill Debuggers enabled.
Improved the Test License feature in DeployLX Manager.
DeveloperMode will reset any secure storage tamper detection and will report tampering in the error report.
See the complete change log and new xbugz.com site for more details.

Changing Windows Console to Use Monaco

Thu, 25 Feb 2010 03:53:27 GMT

I recently acquired a MacBook Pro for my mobile development and played around in Mac OSX before getting Boot Camp and Windows 7 installed. While exploring I kept reading text files in the Monaco font. I've known about it for a while and never liked it as a programming font. But I did like it for the console and SSH apps. But surprise when installing Windows, Monaco was not a available as a console font -- even after downloading it an configuring it for Notepad. So a little digging with Process Monitor I found the registry key needed to make it available:

Disabling Dr. Watson in Windows 7

Thu, 25 Feb 2010 03:53:47 GMT

When an application crashes on Windows 7 where Visual Studio is installed, you're normally prompted to Debug the application (after waiting for it to check for issues :( ). However some applications always get caught by Dr. Watson and never give you a chance to debug. There are a few articles out there on disabling Dr. Watson for XP, but Vista and Windows 7 are different enough that the other techniques often fail to help.