WebORB for .NET 3.0 Release Candidate 2

One week later after we released RC1, there is a new update addressing all the reported bugs. We pushed Release Candidate 2 out tonight with the following fixes/improvements:

• Fixed code generation for the ARP framework for AS2
• Added code generation for the ARP framework for AS3
• Fixed Cairngorm code generation template
• Added code generation support for generics
• Added support to visualize array return value in TestDrive
• Client code for the value object classes not explicitly exposed by remote methods is now generated
• Added console configuration modules for WebORB Logging and Client/Server class mapping (see the Configuration panel)
• Added WebORB diagnostics utility (see the Troubleshooting tab)
• Fixed installer to use internationalized version of the "NETWORK SERVICE" user identity
• Fixed licensing to allow 3.0 and previous versions to coexist on the same machine
• Fixed deployment bug preventing web.config of the target application from being properly updated.

My favorite feature is the diagnostics page. Some users reported difficulty porting WebORB to their own application and in most cases it was a configuration problem. That led us to create the new diagnostics utility. The concept is very simple, connect to a dynamic script running out of the weborb assembly, and it checks if all the required settings and permissions are in place. It is very easy to run the diagnostics:

When you deploy WebORB into your application, copy diagnostics. aspx from the root folder of the default weborb installation (notice it is /weborb30 in rc2) to the root folder of your application. Once the file is there, point your browser to it:

http://localhost/[app-name]/diagnostics.aspx

Alternatively, if you already registered weborb.aspx as an http handler, you can run the diagnostics without copying diagnostics. aspx as shown below:

http://localhost/[app-name]/weborb.aspx?diagnostics