Correct.

Does your statement include the entire Role Based Security add-on?  I noticed dozens of records that I assume are used for RBS.   Are these pre-compiled into the RBS classes?

Example:
SFST_UserNameAtLeast3Chars
SFSTText - User Name

Are these message pre-compiled into SF and unchangable without manually changing them and recompiling the framework?

Ben

There are no pre-defined messages outside of the pre-localized messages for run-time components which are compiled into the SF assemblies.  If you want any localization messages then it is up to you to create these messages and embed (or distribute) them with your application.  As for the pre-localized messages these will not impact you and are not designed for direct calls within your application but rather the pre-localized controls (i.e. BrowseDialog, MaintenanceFormToolstrip, etc).

Hello,

In your Messages_1033.XML file you have dozens of pre-defined messages such as:

SFST_UserNameAtLeast3Chars

Are these compiled into the strataframe dll's that we distribute?  The reason I ask is instead of re-inventing the wheel for "standard" messages such as Security related messages, I want to know if I call

MessageForm.ShowMessageByKey("SFST_UserDeactived")

...that the message will appear on an end-users machine. 

Or do we need to build our own embedded XML file using the Localization editor (generate XML), and compile in the extracted XML messages into our own DLL's and executables?  Do we need to include this embedded XML resource in every DLL and EXE or just one?  If just one, how do we reference "external" resources such as this?

I did read the section on Localization and Messaging in the docs and it does not discuss whether or not your .XML file is included in the distributable SF DLL's nor anything about multi-dll projects and how to handle embedded XML resource files.

Also do you have a package file with these XML messages we can use to import into our package?  Then I can remove the unnecessary messages and create our own XML file.

Lastly, if we do define our own messages such as SFST_UserNameAtLeast3Chars but call it ETI_UserNameAtLeast3Chars, how do we tie or relate that message with the ILoginForm interface code?  I do not see "key" property overrides for any of these messages.  Or is there an event we must capture in our custom login from which is based on the ILoginForm interface class that we have to handle manually?

Thanks!

Ben