locked
Extension libraries and namespaces

    Question

  • I am getting warnings that I have classes in namespaces that does not match the filename of my extension library. They compiler/linker is right about this as I had added some sub namespaces.

    I just want to clarify that an extension library can only export classes that are in the same namespace as the filename? Is this somewhere documented? Will this behavior stay this way in the final version?

    I would prefer to use some sub namespaces for better organization without creating a separate library for each one.

    Edit: Looks like I was too fast on the trigger.

    I found the following comment there: http://msdn.microsoft.com/en-us/library/windows/apps/hh441569(v=VS.85).aspx

    “Namespaces

    Notice that in this example the component namespace is the same as the Visual Studio project name: “mycomp”. This is a limitation in the current version of Windows Developer Preview.”

    So this is just a temporary limitation?

     

    Saturday, October 15, 2011 7:39 PM

Answers

All replies