Different value for Namespace in EarlyBoundGenerator about dlab.xrm.xrmtoolboxtools HOT 10 OPEN

So would this mean creating an Entity/OptionSet/Action specific Namespace box, and if they are different, adding them as references to all files correct?

from dlab.xrm.xrmtoolboxtools.

Yep - I think would cover it.

from dlab.xrm.xrmtoolboxtools.

I'll look to adding additional namespaces as well for the XRM namespaces... It makes the generated code rather hard to read at times...

from dlab.xrm.xrmtoolboxtools.

To what would the XRM namespaces applied?

from dlab.xrm.xrmtoolboxtools.

Let me redefine. I would add some new using statements, so that everything doesn't have to be explicitly defined. You'd only ever care if you looked at the actual generated code. Make sense?

from dlab.xrm.xrmtoolboxtools.

Gotcha.

from dlab.xrm.xrmtoolboxtools.

Is this something that is still desired?

from dlab.xrm.xrmtoolboxtools.

Yes - definitely still desired - either have separate namespace boxes for entities, optionsets etc. - or have a Yes/No option saying "Add relative path to namespace" - when I define a namespace of "MyApp.Core", and a relative folder for the entities of "Entities" and for option sets of "OptionSets", I'd also like to be able to add these relative folder names to the namespace, e.g. "MyApp.Core.Entities" and "MyApp.Core.OptionSets".

Since we don't have that option, I must always

• edit the "Namespace" setting in the global section, generate the Entities
• then edit the "Namespace" again and edit the OptionSets
• and not forget to reset it back to the original value after this

All rather tedious ....

from dlab.xrm.xrmtoolboxtools.

@marcscheuner-bfh how would you propose handling local option sets? By default these are generated in the same file as the Entity. I'm assuming in that case, you would prefer to have the two different namespaces in the same file:

// Single file:
namespace X.OptionSets {
    // Local Option Sets
}

namespace X.Entities {
    // Entity Class
}

from dlab.xrm.xrmtoolboxtools.

@marcscheuner-bfh how would you propose handling local option sets? By default these are generated in the same file as the Entity. I'm assuming in that case, you would prefer to have the two different namespaces in the same file:

Yes - if you desire to have separate namespaces for entities and option sets, I'd also expect those to be applied even inside a single file.

from dlab.xrm.xrmtoolboxtools.