<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom"><title type="text">Blog posts by Adam Najmanowicz</title><link href="https://world.optimizely.com/blogs/Adam-Najmanowicz/" /><updated>2016-10-25T18:58:32.3800000Z</updated><id>https://world.optimizely.com/blogs/Adam-Najmanowicz/</id><generator uri="https://world.optimizely.com/blogs/Adam-Najmanowicz/" version="2.0">Optimizely World</generator><entry><title>Copying files between path providers with PowerShell in EPiServer</title><link href="http://blog.najmanowicz.com/?p=355" /><id>http://blog.najmanowicz.com/?p=355</id><published>2011-08-18T18:07:04.0000000Z</published><updated>2016-10-25T18:58:28.3100000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2011/08/18/copying-files-between-path-providers-with-powershell-in-episerver/"&gt;&lt;img title="Aperture_Science_thumb2.png" src="http://blog.najmanowicz.com/wp-content/uploads/2011/08/Aperture_Science_thumb2.png" alt="Copying files between path providers with PowerShell in EPiServer" width="150" height="150" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	We had a situation in the company this week which required us to deliver the whole EPiServer virtual path provider file structure to the client – zipped. Easy enough… go to the EpiServer VPP directory and… well… ok… hmm… so the path provider is versioning and as a consequence the physical organization of files on [&amp;#8230;]</summary></entry><entry><title>PowerShell for EPiServer – cheat sheet – Part 2</title><link href="http://blog.najmanowicz.com/?p=294" /><id>http://blog.najmanowicz.com/?p=294</id><published>2011-05-10T11:08:00.0000000Z</published><updated>2016-10-25T18:58:28.7300000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2011/05/10/powershell-for-episerver-cheat-sheet-part-2/"&gt;&lt;img title="Aperture_Science.png" src="http://blog.najmanowicz.com/wp-content/uploads/2011/05/Aperture_Science.png" alt="PowerShell for EPiServer &amp;#8211; cheat sheet &amp;#8211; Part 2" width="150" height="150" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	&amp;#160; Most of this post is also based on the Microsoft’s Windows PowerShell Quick Reference however despite the sharing scripting runtimes the nature of the both shells differ considerably as described in the previous post: PowerShell for EPiServer &amp;#8211; cheat sheet &amp;#8211; Part 1. In all cases where it made sense I’ve converted the samples [&amp;#8230;]</summary></entry><entry><title>PowerShell for EPiServer – cheat sheet – Part 1</title><link href="http://blog.najmanowicz.com/?p=242" /><id>http://blog.najmanowicz.com/?p=242</id><published>2011-05-09T10:00:00.0000000Z</published><updated>2016-10-25T18:58:29.1200000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">Most of this is based on the Microsoft’s Windows PowerShell Quick Reference however despite the sharing scripting runtimes the nature of the both shells are pretty different (although the differences are not as vast as one might think). &amp;#160; Windows PowerShell PowerShell Console for EPiServer Interactive – command can ask for confirmations and can be [&amp;#8230;]</summary></entry><entry><title>EPiServer Admin Mode PowerShell scripts</title><link href="http://blog.najmanowicz.com/?p=272" /><id>http://blog.najmanowicz.com/?p=272</id><published>2011-05-07T23:23:00.0000000Z</published><updated>2016-10-25T18:58:29.3530000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2011/05/07/episerver-admin-mode-powershell-scripts/"&gt;&lt;img title="image.png" src="http://blog.najmanowicz.com/wp-content/uploads/2011/05/image-300x245.png" alt="EPiServer Admin Mode PowerShell scripts" width="200" height="163" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	The PowerShell plugin gets an update once again to support Admin mode script collections in addition to the context scripts. How to write an Admin mode script collections? &amp;#60;ContextScriptCollection&amp;#62; &amp;#60;Title&amp;#62;Statistics Scripts&amp;#60;/Title&amp;#62; &amp;#60;Description&amp;#62;This script collection ... &amp;#60;/Description&amp;#62; &amp;#60;Area&amp;#62;Administration&amp;#60;/Area&amp;#62; &amp;#60;Scripts&amp;#62; &amp;#60;ContextScript&amp;#62; &amp;#60;Title&amp;#62;Restart Application&amp;#60;/Title&amp;#62; &amp;#60;Description&amp;#62;The script restarts this instance of EPiServer...&amp;#60;/Warning&amp;#62; &amp;#60;Script&amp;#62;Restart-Application&amp;#60;/Script&amp;#62; &amp;#60;Icon&amp;#62;/App_Themes/Default/Images/Tools/Refresh.gif&amp;#60;/Icon&amp;#62; &amp;#60;Groups&amp;#62; &amp;#60;/Groups&amp;#62; &amp;#60;/ContextScript&amp;#62; &amp;#60;/Scripts&amp;#62; &amp;#60;/ContextScriptCollection&amp;#62; [&amp;#8230;]</summary></entry><entry><title>Context PowerShell Scripts in EPiServer</title><link href="http://blog.najmanowicz.com/?p=225" /><id>http://blog.najmanowicz.com/?p=225</id><published>2011-05-04T08:00:00.0000000Z</published><updated>2016-10-25T18:58:29.5100000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2011/05/04/context-powershell-scripts-in-episerver/"&gt;&lt;img title="wlEmoticon-smile.png" src="http://blog.najmanowicz.com/wp-content/uploads/2011/05/wlEmoticon-smile.png" alt="Context PowerShell Scripts in EPiServer" width="19" height="19" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	Ok, so I’ve got my shot of endorphins writing about PowerShell last week (damn, it’s nice to be able to code again!), and I got pretty determined on making it usable and achieving all the goals I’ve initially envisioned. and in the process build a usable tool and a library of scripts that people can [&amp;#8230;]</summary></entry><entry><title>PowerShell console – now compatible with EPiServer CMS 6 R2</title><link href="http://blog.najmanowicz.com/?p=213" /><id>http://blog.najmanowicz.com/?p=213</id><published>2011-04-29T14:00:00.0000000Z</published><updated>2016-10-25T18:58:29.7270000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2011/04/29/powershell-console-now-compatible-with-episerver-cms-6-r2/"&gt;&lt;img title="wlEmoticon-winkingsmile.png" src="http://blog.najmanowicz.com/wp-content/uploads/2011/04/wlEmoticon-winkingsmile.png" alt="PowerShell console &amp;ndash; now compatible with EPiServer CMS 6 R2" width="19" height="19" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	It’s been a while since I had a chance to do any coding&amp;#8230; turns out leading a development division tends to not have much to do with development… who knew?! But I’ve finally got a moment to sit down and refresh the EPiServer PowerShell console and make it compatible with both CMS versions 5 &amp;#38; [&amp;#8230;]</summary></entry><entry><title>A story of a saved EPiServer site</title><link href="http://blog.najmanowicz.com/?p=169" /><id>http://blog.najmanowicz.com/?p=169</id><published>2010-11-05T14:21:00.0000000Z</published><updated>2016-10-25T18:58:29.8700000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">I meant to write this a long time ago but somehow that never really got out of the room. Following is a narrative of an EPiServer site that was on and off the net for half a year or longer and what I’ve learned in the process. &amp;#60;day id=”1” /&amp;#62; We’ve gathered all the data [&amp;#8230;]</summary></entry><entry><title>The Console of Mass Content Management</title><link href="http://blog.najmanowicz.com/?p=179" /><id>http://blog.najmanowicz.com/?p=179</id><published>2010-09-22T01:02:06.0000000Z</published><updated>2016-10-25T18:58:30.0400000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2010/09/22/the-console-of-mass-content-management/"&gt;&lt;img title="PowerShell1.png" src="http://blog.najmanowicz.com/wp-content/uploads/2010/09/PowerShell1-300x228.png" alt="The Console of Mass Content Management" width="200" height="152" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	This one definitely took more time than I initially expected, and before I devote even more to it I would very much like to hear your opinion. Do you find it useful? Which way should the development be going? But first things first… Have you ever found yourself: having to make a mundane change to [&amp;#8230;]</summary></entry><entry><title>CMS UX – give the content some thought!</title><link href="http://blog.najmanowicz.com/2010/02/08/cms-ux-give-the-content-some-thought/" /><id>http://blog.najmanowicz.com/2010/02/08/cms-ux-give-the-content-some-thought/</id><published>2010-02-08T13:01:38.0000000Z</published><updated>2016-10-25T18:58:30.1630000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">One of the many things we debate constantly at Cognifide is how to improve the user experience. How to make editor’s life easier, how to simplify the common everyday tasks, what can be automated, and simply how to make our customer smile a little when they use our projects. For that to work, apart from [&amp;#8230;]</summary></entry><entry><title>Easy Enum property for EPiServer</title><link href="http://blog.najmanowicz.com/?p=160" /><id>http://blog.najmanowicz.com/?p=160</id><published>2009-12-26T20:29:55.0000000Z</published><updated>2016-10-25T18:58:30.4130000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2009/12/26/easy-enum-property-for-episerver/"&gt;&lt;img title="Easy Enum property for EPiServer" src="http://blog.najmanowicz.com/wp-content/uploads/2009/12/SampleEnumPropertyFlags_thumb-300x207.png" alt="Easy Enum property for EPiServer" width="200" height="138" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	One of the most frequently and eagerly used programming constructs of the Microsoft.Net Framework is Enum. There are several interesting features that make it very compelling to use to for all kinds of dropdowns and checklists: The bounds factor – proper use of Enum type guarantee that the selected value will fall within the constraints [&amp;#8230;]</summary></entry><entry><title>Database-based paged EPiServer searches for CMS 5 R2 SP2</title><link href="http://blog.najmanowicz.com/2009/07/07/database-based-paged-episerver-searches-for-cms-5-r2-sp2/" /><id>http://blog.najmanowicz.com/2009/07/07/database-based-paged-episerver-searches-for-cms-5-r2-sp2/</id><published>2009-07-07T13:15:25.0000000Z</published><updated>2016-10-25T18:58:30.6500000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">Aparently I have written something on that note before for CMS 4 and it looks like someone still needs it as I got a request for an updated version for it a couple of days ago. So here we go: for the most part the syntax for the call is equivalent to what is was [&amp;#8230;]</summary></entry><entry><title>SoakIE – a Web Server Stress Tool with a twist</title><link href="http://blog.najmanowicz.com/2009/05/10/soakie-a-web-server-stress-tool-with-a-twist/" /><id>http://blog.najmanowicz.com/2009/05/10/soakie-a-web-server-stress-tool-with-a-twist/</id><published>2009-05-10T16:27:06.0000000Z</published><updated>2016-10-25T18:58:30.8200000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2009/05/10/soakie-a-web-server-stress-tool-with-a-twist/"&gt;&lt;img title="soakietest.png" src="http://blog.najmanowicz.com/wp-content/uploads/2009/05/soakietest-300x270.png" alt="SoakIE &amp;ndash; a Web Server Stress Tool with a twist" width="200" height="180" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	Last week or so ago a couple of friends in another project in Cognifide has run into a wall while trying to load test their website. the problem was as follows: The website is highly AJAX based – the page merely loads a stub in the initial request but then loads the rest of its [&amp;#8230;]</summary></entry><entry><title>Advanced Language Manipulation Tool for EPiServer</title><link href="http://blog.najmanowicz.com/2009/04/06/advanced-language-manipulation-tool-for-episerver/" /><id>http://blog.najmanowicz.com/2009/04/06/advanced-language-manipulation-tool-for-episerver/</id><published>2009-04-06T17:49:11.0000000Z</published><updated>2016-10-25T18:58:31.1000000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2009/04/06/advanced-language-manipulation-tool-for-episerver/"&gt;&lt;img title="andvancedlanguagetool.png" src="http://blog.najmanowicz.com/wp-content/uploads/2009/04/andvancedlanguagetool-297x300.png" alt="Advanced Language Manipulation Tool for EPiServer" width="198" height="200" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	Have you ever (or have your customers) created and edited a page in one language only to realize that their selected locale was wrong? Have you ever wished you could delete a master language branch of a page&amp;#160; after creating its localized counterpart but you could only delete the newly created slave language instead? Have [&amp;#8230;]</summary></entry><entry><title>Get out of my way! … or the story of file metadata for VirtualPathProvider in EPiServer</title><link href="http://blog.najmanowicz.com/2009/03/17/get-out-of-my-way-or-the-story-of-file-metadata-for-virtualpathprovider-in-episerver/" /><id>http://blog.najmanowicz.com/2009/03/17/get-out-of-my-way-or-the-story-of-file-metadata-for-virtualpathprovider-in-episerver/</id><published>2009-03-17T01:18:00.0000000Z</published><updated>2016-10-25T18:58:31.4130000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2009/03/17/get-out-of-my-way-or-the-story-of-file-metadata-for-virtualpathprovider-in-episerver/"&gt;&lt;img title="metadataeditor.png" src="http://blog.najmanowicz.com/wp-content/uploads/2009/03/metadataeditor-300x204.png" alt="Get out of my way! &amp;#8230; or the story of file metadata for VirtualPathProvider in EPiServer" width="200" height="137" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	Immediately after you implement the VirtualPathProvider proxy from my previous post you will notice a one fairly serious lack in it. Namely all the files within that provider will be hiding behind the registration form. That is not cool for a couple of reasons… You may want to keep all of the files in one [&amp;#8230;]</summary></entry><entry><title>Simple registration for files served by EPiServer</title><link href="http://blog.najmanowicz.com/2009/03/12/simple-registration-for-files-served-by-episerver/" /><id>http://blog.najmanowicz.com/2009/03/12/simple-registration-for-files-served-by-episerver/</id><published>2009-03-12T22:01:00.0000000Z</published><updated>2016-10-25T18:58:31.5370000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">With the culture of knowledge sharing and open source spreading, everyone races to show they have something valuable that you may want. And while you may not ask for money for your content you may still want to get something in return, say a contact, an email address that’s verified (or not), to keep in [&amp;#8230;]</summary></entry><entry><title>WebParts based Sidebar for EPiServer – how to use it?</title><link href="http://blog.najmanowicz.com/2009/01/08/webparts-based-sidebar-for-episerver-how-to-use-it/" /><id>http://blog.najmanowicz.com/2009/01/08/webparts-based-sidebar-for-episerver-how-to-use-it/</id><published>2009-01-08T18:06:47.0000000Z</published><updated>2016-10-25T18:58:31.7230000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2009/01/08/webparts-based-sidebar-for-episerver-how-to-use-it/"&gt;&lt;img title="webpartframeworkpluginsettings1.png" src="http://blog.najmanowicz.com/wp-content/uploads/2009/01/webpartframeworkpluginsettings1-300x200.png" alt="WebParts based Sidebar for EPiServer &amp;ndash; how to use it?" width="200" height="133" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	Once you’ll update the framework to the extended one, you will immediately notice that… nothing has changed. Hmm… did something go wrong? Well, not really. By default the framework will be run in the “legacy mode”. Thanks to an old article by our own Marek Blotny, I’ve learned how to build Plugin settings which are [&amp;#8230;]</summary></entry><entry><title>WebParts based Sidebar for EPiServer – the motivation and specification</title><link href="http://blog.najmanowicz.com/2009/01/08/webparts-based-sidebar-for-episerver-the-motivation-and-specification/" /><id>http://blog.najmanowicz.com/2009/01/08/webparts-based-sidebar-for-episerver-the-motivation-and-specification/</id><published>2009-01-08T15:04:12.0000000Z</published><updated>2016-10-25T18:58:31.8670000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2009/01/08/webparts-based-sidebar-for-episerver-the-motivation-and-specification/"&gt;&lt;img title="WebParts based Sidebar for EPiServer &amp;ndash; the motivation and specification" src="http://www.najmanowicz.com/blog_images/DragDropWebPartsmaller.gif" alt="WebParts based Sidebar for EPiServer &amp;ndash; the motivation and specification" width="200" height="150" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	Back in the day when we started designing our last project we’ve been presented with a following problem – a big number of templates with slightly different sidebars. Hmm… Is sidebar a part of content? No, rather not. We don’t want the editors to have to setup the sidebar for every article they write (and [&amp;#8230;]</summary></entry><entry><title>Fix for EPiServer CMS5 interfering with your EPiServer 4</title><link href="http://blog.najmanowicz.com/2008/06/27/fix-for-episerver-cms5-interfering-with-your-episerver-4/" /><id>http://blog.najmanowicz.com/2008/06/27/fix-for-episerver-cms5-interfering-with-your-episerver-4/</id><published>2008-06-27T16:47:11.0000000Z</published><updated>2016-10-25T18:58:32.0530000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">The problem that can make a grown up man cry… You’re editing your EPiServer 4 project and suddenly the edit mode stops working. the server reports compilation errors. something along the lines: Compiler error: CS0433: Type „EPiServer.Global” exists in „c:\WINDOWS\assembly\GAC_MSIL\EPiServer\5.1.422.122__8fe83dea738b45b7\EPiServer.dll” and „c:\WINDOWS\assembly\GAC\EPiServer\4.61.5.83__8fe83dea738b45b7\EPiServer.dll” The solution is to go to your web.config and edit the compilation section. [&amp;#8230;]</summary></entry><entry><title>Text-Image generation – VirtualPathProvider for EPiServer (and ASP.NET in general) – Part 2 (configuration)</title><link href="http://blog.najmanowicz.com/2008/06/24/text-image-generation-virtualpathprovider-for-episerver-and-aspnet-in-general-part-2-configuration/" /><id>http://blog.najmanowicz.com/2008/06/24/text-image-generation-virtualpathprovider-for-episerver-and-aspnet-in-general-part-2-configuration/</id><published>2008-06-24T20:36:00.0000000Z</published><updated>2016-10-25T18:58:32.2870000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">The configuration of the module is a descendant of any EPiServer Virtual Path Provider configuration. This aspect is fairly well described on EPiServer pages. A sample configuration for the TextImageVirtualPathProvider can look as follows &amp;#60;configuration&amp;#62; &amp;#60;episerver&amp;#62; &amp;#60;virtualPath &amp;#60;providers&amp;#62; &amp;#60;add showInFileManager="false" virtualName="Text Images" virtualPath="~/TextImages/" bypassAccessCheck="false" name="TextImages" type="Cognifide.ImageVirtualPathProvider.TextImageVirtualPathProvider,Cognifide.ImageVirtualPathProvider" physicalPath="C:\temp\TextImages" allowedReferers="(localhost)" allowNullReferrer="false" replacementStrings="$colon$,:,$gt$,&amp;#62;,$dot$,.,$quot$,&amp;#38;quot;,$amp$,&amp;#38;amp;,$star$,*,$eol$,&amp;#38;#10;,"/&amp;#62; &amp;#60;/providers&amp;#62; &amp;#60;/virtualPath&amp;#62; &amp;#60;/episerver&amp;#62; &amp;#60;/configuration&amp;#62; &amp;#160; [&amp;#8230;]</summary></entry><entry><title>Text-Image generation – VirtualPathProvider for EPiServer (and ASP.NET in general) – Part 1</title><link href="http://blog.najmanowicz.com/2008/06/23/text-image-generation-virtualpathprovider-for-episerver-and-aspnet-in-general-part-1/" /><id>http://blog.najmanowicz.com/2008/06/23/text-image-generation-virtualpathprovider-for-episerver-and-aspnet-in-general-part-1/</id><published>2008-06-23T20:00:00.0000000Z</published><updated>2016-10-25T18:58:32.3800000Z</updated><author><name>adam.najmanowicz@cognifide.com</name></author><category term="Blog post" /><summary type="html">
	&lt;div&gt;
	&lt;a href="http://blog.najmanowicz.com/2008/06/23/text-image-generation-virtualpathprovider-for-episerver-and-aspnet-in-general-part-1/"&gt;&lt;img title="helloeolfromeolcognifide.png" src="http://blog.najmanowicz.com/wp-content/uploads/2008/06/helloeolfromeolcognifide.png" alt="Text-Image generation &amp;#8211; VirtualPathProvider for EPiServer (and ASP.NET in general) &amp;ndash; Part 1" width="104" height="200" /&gt;&lt;/a&gt;
	&lt;/div&gt;
	The module code is already available on Epicode SVN, the relevant wiki pages will be following as soon as documentation is complete. The use case is as follows: The client wants the site to look exactly as in a template provided as a image, the text is using a non standard font that is not [&amp;#8230;]</summary></entry></feed>