Satellite assemblies are often used to deploy language-specific resources for an application. These language-specific assemblies work in side-by-side execution because the application has a separate product ID for each language and installs satellite assemblies in a language-specific subdirectory for each language. When uninstalling, the application removes only the satellite assemblies associated with a given language and .NET Framework version. No core .NET Framework files are removed unless the last language for that .NET Framework version is being removed
Login to rate this answer.
A private assembly is normally used by a single application, and is stored in the application's directory, or a sub-directory beneath.
A shared assembly is intended to be used by multiple applications, and is normally stored in the global assembly cache (GAC), which is a central repository for assemblies.
Login to rate this answer.
Satellite assemblies are used for the functioning of Globalization and Localization. Globalization involves providing code that is common to all languages and cultures for the application created. Localization involves converting the global application into particular sectoral usage like defining language, Currency format, Decimal Separator, Datetime format and so on. In order the localization performs well Satellite assemblies provide information on formatting functionalities involved in Culture, Language, Currency and DateTime formats of an application.
Login to rate this answer.
A .NET Framework assembly containing resources specific to a given language. Using satellite assemblies, you can place the resources for different languages in different assemblies, and the correct assembly is loaded into memory only if the user elects to view the application in that language."
This means that you develop your application in a default language and add flexibility to react with change in the locale. Say, for example, you developed your application in an en-US locale. Now, your application has multilingual support. When you deploy your code in, say, India, you want to show labels, messages shown in the national language which is other than English.
Satellite assemblies give this flexibility. You create any simple text file with translated strings, create resources, and put them into the bindebug folder. That's it. The next time, your code will read the CurrentCulture property of the current thread and accordingly load the appropriate resource.
This is called the hub and spoke model. It requires that you place resources in specific locations so that they can be located and used easily.
Login to rate this answer.
Yashwant singh
Answered On : Apr 15th, 2012
Through the satellite assembly we can change the language of browser
Login to rate this answer.
