One web resource per entity
One web resource per entity ribbon
Generic or utility web resources
Anything that is not specific to an entity needs to be in a separate library. Use common sense here please. Don’t create a large number of libraries containing only a few functions, but group them together along common functionality lines.
Maybe something like this:
- String and data-formatting functions
- General utility functions
Tool-specific resources: jQuery, JSON2, XrmSvcToolkit
Any time you have to include a tool such as jQuery or the XrmSvcToolkit, you should always create separate libraries for those unique pieces of code.
Note: I would like to advise you to NOT put the version number in the library name. Once saved, that name is read-only and if you ever upgrade, the version number will not reflect the truth. Instead, make a library such as jQuery.js and put the version number in the library description field.
Naming of libraries is very important. I like to use the convention used by Microsoft:
You should always add the file extension to any web resource you create. Having an extension already applied to a file will make the use of the tools we have discussed much easier for you.