Hi Trent,
Great addition!!!

I will be upgrading my VS this weekend to start testing the new stuff.

Edhy Rijo

One major feature that we failed to mention about the new update is the ability to localize the RBS security permissions and roles.  This was done in a way that you would not have to change your RBS security packages at all.  In fact, all you need to do is create localization keys for your application for any of the localization packages that you have that are getting loaded into your application, and the RBS will find them.

For example, I have a client localization package that is used for the main client EXE in our medical application.  This is where I chose to place the RBS permission keys.  There are really two things that needed to be localized, the key itself, and the description.

This is the format of localizing.  The actual permission is the root of the key.  So lets take the example of "Accounts Receivable Report" as my RBS permission.  I now need to create two localization keys for this, one for the permission and the other for the description.

1. Open up the localization project that will house the keys
2. For the permission, add "SEC_" (without the quotes) to localization the permission.  So in this example, it would look like this: SEC_Accounts Receivable Report
3. For the description of the permission, it will have the SEC_ at the beginning as well as _DESC at the end.  Like this: SEC_Accounts Receivable report_DESC
   
   
   (Note: These are just Text Values, NOT messages.  Just like any other localization text value only.)
   
   
4. Export the localization package and update your project.
5. When you run the RBS editor inside of your application at run-time, the keys should now reflect the appropriate language.

Let me know if you have any questions here.