Blog posts by Sebastian Lundh

Blog posts by Sebastian Lundh2011-07-01T10:39:08.0000000Zhttps://world.optimizely.com/blogs/Sebastian-Lundh/ Optimizely World Multicast configuration with multiple NIC’s.nicToUseName gives the possibility to name the Network you want to send EPiServer remote events over. UDP multicast is so <a href="http://www.youtube.com/watch?v=4Z2Z23SAFVA">esey</a>, no need to add a section for each site in an enterprise configuration.  No need to setup special ports for listening and sending events. Just uncomment from standard configuration and it works. Very often servers have double NIC's in use and when sending out udp multicast packets it will by standard choose the NIC with lowest index. So you startup <a href="http://www.wireshark.org/">Wireshark</a> and don’t see any packets at all when listening on one of the NIC’s and filtering out UDP packets. So you listen on the other NIC and see that it’s actually trying sending out events over the wrong network. Solution: Control Panel\Network and Internet\Network Connections Check the name of the connection. Set this value as nicToUseName="nameofthenetwork" Add this to web.config like: <customBinding>         <binding name="RemoteEventsBinding">           <binaryMessageEncoding />           <udpTransport multicast="True" nicToUseName="Local Area Connection"  />         </binding> </customBinding> Now it will send and listen on this network.2011-07-01T10:39:08.0000000Z

Blog post

Request Monitor GadgetThe idea behind this gadget is to be able to pinpoint slow pages and see activity on the site. Then analyze why these pages takes long time to load. You can also on specific pages see all requests to compare performance of the site to earlier. The gadget will show activity for the day with updates every 20min.   <a href="/link/e02d8e43a3af4807ae732eac26621899.png"><img title="latest" style="border-top-width: 0px; display: inline; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="101" alt="latest" src="/link/1979a83498354fd782d9df7f1ba335f3.png" width="244" border="0" /></a> Shows 50 latest requests to the site with page id, request time, ip, date and username if logged in. You can filter on Pageid, if thextbox is empty it will just refresh table.    <a href="/link/8fa5957e283248909416f234c7bd5bb3.png"><img title="slowest" style="border-top-width: 0px; display: inline; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="92" alt="slowest" src="/link/86adb9a411864768998d200753ed2232.png" width="244" border="0" /></a> Shows the 50 slowest pages with page id and average request time for it. Here you can also search by page id to get data for specific pages.    <a href="/link/23038de7fda54ea5b66a6ce485448039.png"><img title="Activity" style="border-top-width: 0px; display: inline; border-left-width: 0px; border-bottom-width: 0px; border-right-width: 0px" height="244" alt="Activity" src="/link/fafecf9d8e7b48dfb859f6061cd3f956.png" width="204" border="0" /></a> Shows activity for today over 24h. With all requests grouped within 20min. Google chart is used. Configuration will let you empty all data. Installation Download the install package and install it with EPiServer Deployment Center. You will also have to update web.config also with the http module that listens to PreRequestHandlerExecute and PostRequestHandlerExecute to capture request times. Add to <httpModules> (IIS6) and <Modules> (IIS7): <add name="RequestModule" type="RequestMonitorGadget.Modules.RequestModule, RequestMonitorGadget"/>   Download <div class="wlWriterEditableSmartContent" id="scid:fb3a1972-4489-4e52-abe7-25a00bb07fdf:50d506c4-3b2f-4c72-ac09-78bfc45e14e6" style="padding-right: 0px; display: inline; padding-left: 0px; float: none; padding-bottom: 0px; margin: 0px; padding-top: 0px"> <a href="/link/f6ebf323843444ae9dcfeb2c4d9944e7.epimodule" target="_blank">Install package</a></div> <div class="wlWriterEditableSmartContent" id="scid:fb3a1972-4489-4e52-abe7-25a00bb07fdf:7205aae0-2b48-48b3-afd0-d406a152794f" style="padding-right: 0px; display: inline; padding-left: 0px; float: none; padding-bottom: 0px; margin: 0px; padding-top: 0px"> <a href="/link/c67c200aa96342e9a1a0895afa5981e8.zip" target="_blank">Source</a></div>2009-11-30T10:22:38.0000000Z

Blog post

Hints on how to speed up initializationHere’s some hints on how you can speed up initialization of your EPiServer sites. In the “lang” directory you have all the system languages. These are parsed and loaded into the memory. It might be the case that you don’t really need all of these. If you have a load balanced or mirroring setup with front servers and servers for editors maybe you just need one system language on front servers. With the site setting stringDelayedLoadThreshold in web.config it’s possible to set a string length limit for what’s being loaded during initialization. So a value of 50 means that all strings shorter than 50 will be loaded directly and all strings longer than 50 will be loaded on demand. In R2 SP1 this was standard that all requests goes to a page showing “Application is initializing. Please retry shortly.” in R2 SP2 this was changed to that you could choose yourself what behavior you want with having or removing ApplicationInitializing.txt. Basically if you have this text file all requests will not be queued up. So the application will start up faster. See Magnus blog for more information: <a href="http://labs.episerver.com/en/Blogs/Magnus-Strale/Dates/2009/4/EPiServer-Initialization-and-quotApplication-is-busy-under-initialization-phasequot/">http://labs.episerver.com/en/Blogs/Magnus-Strale/Dates/2009/4/EPiServer-Initialization-and-quotApplication-is-busy-under-initialization-phasequot/</a> EPiServer goes through dll’s in bin folder to check for different attributes like plugins: [GuiPlugIn(DisplayName = "MyPlugIn", Description = "Just a sample", Url = "~/myplugin/Sample.ascx", Area = PlugInArea.EditPanel)] If you have assemblies that doesn’t use any of these attributes, like referenced assemblies for instance it might be a good idea to setup probing of assemblies to another folder then bin. Something like:   <runtime>       <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">           <probing privatePath="bin\subbin" /> For more information see Scotts blog: <a href="http://www.hanselman.com/blog/PermaLink.aspx?guid=4d0ef4fb-f8ae-4355-a658-3c0432c98dbe">http://www.hanselman.com/blog/PermaLink.aspx?guid=4d0ef4fb-f8ae-4355-a658-3c0432c98dbe</a> Please post any other ideas.2009-11-19T16:09:56.0000000Z

Blog post

EPiServer Mail 4.3 to work with R2While the development team is working on installer packages for EPiServer Community and EPiServer Mail for the new EPiServer Installation manager there are some workarounds that can be performed to run EPiServer Mail on R2. Other than the normal instructions at: <a href="http://world.episerver.com/en/Documentation/Items/Installation-Instructions/Create/Installation-Instructions---Create/">http://world.episerver.com/en/Documentation/Items/Installation-Instructions/Create/Installation-Instructions---Create/</a> There’s a problem with the EPiServer Mail installer and that in R2 the UI folder is moved to: C:\Program Files\EPiServer\CMS\5.2.375.7\Application <add virtualPath="~/SUI/" physicalPath="C:\Program Files\EPiServer\CMS\5.2.375.7\application\UI" name="UI" type="EPiServer.Web.Hosting.VirtualPathNonUnifiedProvider,EPiServer" /> You can copy that  folder back to your sites root and name it correctly and remove the Virtual path entry for the UI folder. If you want, after installation you can just copy the UI/Mail folder to the UI folder located in program files and add the virtual path again. Also you will have to remove all entries to System.Web.Extensions 1.0 if you have that installed already, like: <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /><?xml:namespace prefix = o /?><o:p></o:p> <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /><o:p></o:p> <add assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> Then add assembly redirect for 1.0 to 3.5:<o:p></o:p> <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" /> </dependentAssembly><o:p></o:p> <dependentAssembly xmlns="urn:schemas-microsoft-com:asm.v1"> <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" /> <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" /> </dependentAssembly> Edit: You also need to make sure that you use full path to UI folder in site settings: uiUrl="http://site/SUI/" 2008-12-12T09:00:55.2300000Z

Blog post