- Resources are created automatically by default by VS.Net for Windows forms. They can be plain text files for string resources or XML files for string and binary resources.
- You can select language for each form and have different layout for each language.
- This creates satiellite assemblies for each language which are used by runtime depending on the culture selected.
- Each satellite assembly resides in a culture specific folder which uses ISO naming convention for e.g. for UK English it will be en-GB and for US English it would be en-US.
- There is no code in the resource dll.
- Main assembly will use resourse dll in sub directories e.g. en-GB\assemblyName.resources.dll.
- You can add custom resources.
- Naming convention for custom resource file [resourceType].[culture].resx. This way the culture specific custom resouce files will be compile in the satellite assemblies [undocumented feature].
- Resouces files are deployed in \[culture] fodler for windows forms and \bin\[culture] folder for asp.net.
- You can access culture specific resource using ResourceManager.GetResourceSet(cultureInfo)
- If the resource manager can't find the specific culture resource, it will fall back to neutal resource. For e.g. en is neautral resource for en-US, en-GB or en-CA.
- If resource manager can't find netural resouce it will fall back to invariant resouce which is located in main aseembley.
- A resouce manager bases its resource lookup based on the current thread's UI culture.
HTML5 has introduced lots of new cool tags . Not all the browsers support all tags and also the implementation of these tags may be different for each browser. HTML5 specification defines the functional aspects of these tags and not the implementation. Also the general concensus is that by 2022 all browsers will support all new features of HTML5. Of all the modern browsers, Chrome seems to have implemented most, if not all, featutes of HTML5. IE9 supports few. Firefox sits in between. So as a developer how do you make use of the cool HTML5 features without causing any compatibility issues with existing browsers? Traditionally developers have used User Agent to detect browser type and use the features accordingly. However these days, you can easily change a User Agent by using addons in your browser. So you need a more robust way to detect the features supported by the browser as the same engine of two different versions of a browser mig...
Comments