Ensuring that the layer rule scripting engine supports more complex rules
such as (authenticated) and (url "~/notes").
Add a bunch of unit tests to ensure consistency between DLR based
engine and custom engine.
Work Item: 17186
--HG--
branch : 1.x
The nhibernate configuration stores the physical path to the SqlCe database
so we need to include the physical location as part of the hash key, so that
xcopy migrations work as expected.
Work Item: 17159
--HG--
branch : 1.x
The SpecFlow test for dynamic compilation wasn't actually trigering
dynamic compilation for all modules, because some of the were copied
to the "~/bin" assembly of the hosted ASP.NET application used for
SpecFlow testing.
This now works as expected, and we have 3 tests for this: one with
dynamic compilation enabled, one with dynamic comilation disabled,
and one with forced dynamic compilation (other loaders disabled).
--HG--
branch : dev
When setting up specflow tests, we ended up copying the full content
of the "bin" folder of every module. These folder contain not only
the module assembly, but also many other assemblies used by the
Orchard framework (the framework itself, and all dependencies).
We know skip these files, which dramatically decreases the amount of
file I/O needed to start these tests.
Also adding logging to trace what's going on during initialization.
--HG--
branch : dev
It hasn't been needed since MVC2, and it now broken with MVC3.
--HG--
branch : dev
extra : transplant_source : N%CA%B4%F6%13%9C%BE%2AL%14z_%13%A9%90cF%00%DCn
We have this in Orchard.Setup.csproj:
<Reference Include="Autofac, Version=2.1.13.813, Culture=neutral, PublicKeyToken=17863af14b0044da, processorArchitecture=MSIL">
<SpecificVersion>False</SpecificVersion>
<HintPath>..\..\..\..\lib\autofac\Autofac.dll</HintPath>
</Reference>
However, version of autoface we are using is not 2.1.13.813.
This means that, even if the full assembly name is specified in the csproj file,
we still need to lookup the assembly by short name if we can't find it.
--HG--
branch : dev
For themes, the pattern is slighty different than for modules,
Also, we need to interleave the different views engine in between
themes and base themes, so that overrides between Razor and WebForms
work as excpected.
--HG--
branch : dev
When looking for ViewPath to activate, the order should be:
1. Current active theme
2. Base themes of the current theme (in "base" order). Note that "base themes"
for "TheAdmin" theme means all enabled themes
3. Modules which have at least one active feature, in feature dependency order
Work Item: 16654
--HG--
branch : dev
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
Orchard used to write to the "~/web.config" file to force an AppDomain
restart needed in some case of dynamic compilation.
Revised the policy to be like this:
1. If full trust, use HttpRuntime.UnloadAppDomain()
2. If Medium Trust, write to "~/bin/HostRestart/marker.txt"
3. If Medium Trust and 2. failed, write to "~/web.config"
4. If Medium Trust and 2.+3. failed, give an error message to
the user with appropriate measures to take on the web server.
Also removed a now unused "ResetSiteCompilation" method
--HG--
branch : dev
Don't try to load references that have been already loaded by
extension loaders. This bug was affecting compiling of modules
depending on other modules (e.g. Orchard.Widgets depends on
Orchard.Scripting). If Orchard.Scripting has been loaded by the
dynamic compilation loader, don't try to load the "Orchard.Scripting"
assembly.
--HG--
branch : dev
We were only monitoring existing directories only (not files).
Since asp.net supports monitoring missing files, but not missing
directories, we have to catch the HttpException and fallback
adequatly.
--HG--
branch : dev
Ensure batch compilation is on and that the number of recompilation
before appdomain restart is greater than the default (15), because
Orchard being a composable application where new modules can be installed
at any time, views can be re-compiled more often than for a typical
application.
--HG--
branch : dev
* Remove un-used machine key
* Increase "numRecompilesBeforeAppRestart" default value (15) to (1000) so
that the AppDomain used for hosting the ASP.NET domain doesn't get unloaded
during the test.
--HG--
branch : dev
Instead of processing tasks asynchronously at the end of a request,
we process them synchronously, so that the behavior is more
deterministic.
--HG--
branch : dev
Renaud Paquay