The NGWS runtime uses a hub and spoke model for packaging and deploying resources. The hub is the main assembly that contains the non-localizable executable code and the resources for a single culture called the neutral culture. The neutral culture is the fallback culture for the application. Each spoke connects to a satellite assembly that contains the resources for a single culture. Satellite assemblies do not contain code.
The advantages of this model are:
The disadvantages of this model are:
The NGWS frameworks provide APIs to manage resources deployed using the above model. While most Microsoft applications built for the NGWS platform are expected to use the hub and spoke model with one culture per assembly, the NGWS runtime does not require applications to use this packaging model. The following are some examples of packaging models an application can use:
The advantages of this model are:
The disadvantages of this model are:
An application that does not use the NGWS packaging and deployment model for resources will have to supply a custom resource manager to access resources. The Base Class Library provides APIs that can be used to build such a resource manager.