Hi Steve, Thanks for your answer. It sounds hopefull! I didn't know i could leave mappings out of my assembly. Because, always when i forget to set it as an embedded resource, i'm getting errors. Can you give me a hint on how to work with / where to place / a mapping file when i don't want embed it? Thanks for your help! Tys
On Jun 6, 7:35 pm, sbohlen <[email protected]> wrote: > Tys: > > There is no requirement that any (and certainly not all) mapping files be > compiled into your assembly as embedded resources. You can easily mix and > match embedded and stand-alone XML mapping files in your application. > > In your situation, I would embed the mapping file(s) not expected to change > into an assembly as resources but leave the mapping file(s) that are > expected to change as externalized file(s) that can be edited as needed > after the application is deployed. Since its all just XML, you can edit it > in any text editor, provide a custom application to your customer to enable > them to specify the name of the table they want in the mapping file, etc. > > Hope this helps. > > -Steve B. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
