Blog posts by Marthin Freij2011-01-30T22:11:35.0000000Zhttps://world.optimizely.com/blogs/Marthin-Freij/Optimizely WorldProfiling NHibernate or Linq to SQL in an EPiServer CMS solutionHibernating Rhinos has two really good products for profiling applications that are using NHibernate or Linq to SQL, NHibernate Profiler and Linq to Sql Profiler. To profile your application you need to reference an appender and initialize it upon startup. This can easily be done in several ways in EPiServer CMS, using HTTP modules, the [...]2011-01-30T22:11:35.0000000ZBlog postEPiServer – ReflectionTypeLoadException: Unable to load one or more of the requested typesToday I installed Page Type Builder 1.2 Beta 2 on my ongoing EPiServer CMS 6 project. I dropped the Page Type Builder assemblies in the bin folder, recreated the references, did an iisreset and then tried to start the site. I got the following exception: Unable to load one or more of the requested types. [...]2010-04-30T12:29:31.0000000ZBlog postEPiServer - ReflectionTypeLoadException: Unable to load one or more of the requested types<p>Today I installed Page Type Builder 1.2 Beta 2 on my ongoing EPiServer CMS 6 project. I dropped the Page Type Builder assemblies in the bin folder, recreated the references, did an iisreset and then tried to start the site. I got the following exception:</p> <p><strong>Unable to load one or more of the requested types. The following information may be a subset of the Type/LoaderException information present - inspect with debugger for complete view. <br />Check assemblies [PageTypeBuilder, Version=1.1.9.1, Culture=neutral, PublicKeyToken=6fb8762af0e6dbed] and/or types [PageTypeBuilder.Reflection.MethodInfoExtensions, <br />PageTypeBuilder.Abstractions.PageTypeFactory, <br />PageTypeBuilder.Activation.PageTypePropertyInterceptor, <br />PageTypeBuilder.Discovery.PageTypeDefinition, <br />PageTypeBuilder.Synchronization.PageTypePropertyUpdater, <br />PageTypeBuilder.Discovery.PageTypePropertyDefinitionLocator, <br />PageTypeBuilder.Initializer, <br />PageTypeBuilder.Synchronization.PageTypeUpdater, <br />PageTypeBuilder.PageTypeBuilderException, <br />PageTypeBuilder.UI.PageDataValidationExtensions, <br />PageTypeBuilder.Synchronization.Validation.UnmappablePropertyTypeException, <br />PageTypeBuilder.Discovery.PageTypeDefinitionLocator, <br />PageTypeBuilder.PageDataExtensionMethods, <br />PageTypeBuilder.Activation.PageTypePropertiesProxyGenerationHook, <br />PageTypeBuilder.Synchronization.TabDefinitionUpdater, <br />PageTypeBuilder.Reflection.AttributedTypesUtility, <br />PageTypeBuilder.Discovery.PageTypePropertyDefinition, <br />PageTypeBuilder.Synchronization.TabDefinitionExtensions, <br />PageTypeBuilder.Synchronization.PageTypeSynchronizer, <br />PageTypeBuilder.Synchronization.PageTypePropertyDefinitionExtensions]. Information from LoaderExceptions property [Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed., <br />Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed., <br />Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed., <br />Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed., <br />Request for the permission of type 'System.Web.AspNetHostingPermission, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.].</strong></p> <p>The reason for this exception is Windows 7 security features. When you download assemblies from Internet they might be marked as unsafe. To solve this, right click each assembly, select Properties and click the Unblock button on the General tab.</p>2010-04-30T11:05:07.0000000ZBlog postConfiguring page provider capabilities<p>Page providers requires some configuration. In addition to the obvious ones like name, type and entryPoint you should also define what capabilities your page provider supports, such as Create, Edit, Delete and Search. If you, for example, specify that your provider does not support delete, all delete related ui in edit mode will be disabled for your providers pages. More details on capabilities can be found in the Configuration section of the <a href="http://world.episerver.com/Documentation/Items/Tech-Notes/EPiServer-CMS-5/EPiServer-CMS-5-R2/Page-Providers/">Page Provider Tech Note</a>.</p> <p>In almost all examples I have seen for page provider configuration, capabilities are specified in web.config. In my opinion, capabilities should not be defined in configuration. This could lead to, by accident, specifying more capabilities than what is actually implemented in code. I think the best place for this kind of configuration is code. Fortunately, the Capabilities property in PageProviderBase is virtual, which means you can override it and configure it there.</p> <pre><span style="color: #0000ff">public</span> <span style="color: #0000ff">override</span> PageProviderCapabilities Capabilities
{
<span style="color: #0000ff">get</span>
{
<span style="color: #0000ff">return</span> PageProviderCapabilities.Create |
PageProviderCapabilities.Edit |
PageProviderCapabilities.Search;
}
}</pre>2010-02-11T22:02:00.0000000ZBlog postProblem with constructing PageReferences in Page Providers<p>Recently I have spent some time implementing page providers for a customer. A couple of days ago I noticed that one of the page providers started to behave strange for one particular PageId. The PageReference for that page had RemoteSite set to null instead of the page providers ProviderKey. This means that the PageReference will point on a page in the LocalPageProvider rather than on my page in my custom page provider. After some investigation it was clear that this particular PageReference was equal to the PageReference of the page providers EntryPoint.</p> <p>The problem seemed to be related to constructing the PageReference which was handled by the PageProviderBase.ConstructPageReference methods. Reflecting these methods with Reflector made it clear that PageReferences are constructed with RemoteSite set to ProviderKey only if PageId is not equal to EntryPoint.ID. The workaround is to construct the PageReference yourself and always set the ProviderKey part. Be careful though when you are constructing ParentLink for top-level pages because it in these cases is located on the LocalPageProvider.</p>2010-02-08T11:30:49.0000000ZBlog post