We are happy to announce availability of SPAW Editor .NET Edition version 2.0.5.1 Release Candidate. This release fixes all the major issues found in the 2.0.5 Beta and now should be stable enough to be used in production sites. You can download it through our download page.

Here’s the change log for 2.0.5.1 RC:

1. FEATURE ADDED: Quick links in hyperlink dialog
2. BUGFIX: Text property wasn’t updated when SPAW was used with MasterPages, etc.
3. BUGFIX: paths were not correctly calculated when SPAW was used in applications residing in web site root directory
4. BUGFIX: it wasn’t possible to use SPAW when session state was stored in State Server or SQL Server (non-serializable data was stored in Session)
5. BUGFIX: on some installations there was “The Controls collection cannot be modified because the control contains code blocks (i.e. <% … %>).” exception generated in all dialogs.
6. INTERNAL CHANGE: only “secure” configuration settings are saved in Session now
7. LANGUAGE FILES FIXED: html entities were not defined in Spanish, Brazilian Portuguese and French language files

Please note that the current price for the Enterprise license will stay until the end of November and then go up. So make sure you reserve your copy this week with the 30% discount.

I’ve written a post in my personal blog about a way to ease ASP.NET control development using Express editions of Visual Studio.

Check it out if you this is something you are interested in. And don’t forget to “kick it” if you like it

It has come to our attention that whenever you use SPAW 2.0.5 .NET Edition Beta on a page with master pages you can’t access submitted content with the Text property of your SpawEditor object.

This is one of the most important and annoying issues in the beta but luckily there’s a workaround. While we are working on the next release you can access the submitted content through Request.Form[”editor_id”]. Obviously this is not an elegant solution and we apologize for the bug, but it works for now.

Thanks to everyone who reported and helped identify the cause of this bug!