- ILockFileManager to create and check lock files
- ILockFile represent an acquired lock file
- Lock files expire after 10 minutes by default
- Lock files are created in ~/App_Data
- Default implementation provided (as it is in Orchard.Framework)
--HG--
branch : indexing
For dynamic compilation, there is a limited set of thing Orchard can
do to load assemblies referenced in .csproj files. With this checkin,
there are now 4 policies for resolving short assembly names to full
assembly names:
1. Try to load the assembly with its short name
2. Try to find the assembly in the list of assemblies in the AppDomain
3. Try to find the assembly in the list of assemblies referenced
by Orchard.Framework
4. Try to find the assembly in the list of assemblies commonly
installed in the GAC with .NET 4.0.
Work Items: 16940, 16946
--HG--
branch : dev
A few common .net framework assemblies are referenced by the Orchard.Framework
assembly. Look into those to see if we can find the assembly we are looking for.
This is useful for orchard modules project files, where commonly used assemblies
don't need to be specified with a strong name.
--HG--
branch : dev
When a new set of assemblies is enabled, we need to invalidate the
nhibernate serialized configuration (since it contains not only types
names for records, but also assembly names)
--HG--
branch : dev
