Comments for Codality

Comment on Sitecore PowerShell Console cheat sheet – Part 1 by Adam Najmanowicz

Adam Najmanowicz — Tue, 24 Jan 2012 02:15:17 +0000

You’ve hit the nail on the head, probably one of my favourite aspects of PowerShell – there’s many means to an end – everyone can get there at their own pace.

But you’re absolutely right, to be honest I’ve simply forgotten about the env: drive :)

Comment on Sitecore PowerShell Console cheat sheet – Part 1 by Max Trinidad

Max Trinidad — Tue, 24 Jan 2012 00:05:33 +0000

Hi Adam,

Great Cheat Sheet article! I just have one observation when listing the Environment variables. PowerShell already provide you with the simpler solution to display these values using the Environment provider (PSDrive) “Env:”. So, the equivalent to “[System.Environment]::GetEnvironmentVariables()” is doing a “dir Env:” or “Get-Item Env:”. This way is less typing, and is already sorted by name. Of course, there’s nothing wrong in what you’ve shown, and let everyone know that they can use .NET Method to get the environment values. Good Job!

Comment on Sitecore PowerShell Console cheat sheet – Part 1 by Sitecore PowerShell Console cheat sheet – Part 2 | Codality

Sitecore PowerShell Console cheat sheet – Part 2 | Codality — Mon, 23 Jan 2012 16:03:14 +0000

[...] Code and Effect – solving problem with just enough amount of code – by Adam Najmanowicz « Sitecore PowerShell Console cheat sheet – Part 1 [...]

Comment on PowerShell for EPiServer – cheat sheet – Part 1 by Sitecore PowerShell Console cheat sheet–Part 1 | Codality

Sitecore PowerShell Console cheat sheet–Part 1 | Codality — Wed, 11 Jan 2012 20:36:14 +0000

[...] great deal of this post is a port of my older post for similar console for EPiServer, but since the differences are significant enough to confuse [...]

Comment on Continuous deployment in Sitecore with PowerShell by Bartek Szafko

Bartek Szafko — Mon, 19 Dec 2011 13:15:14 +0000

Great post!

That would definitely allow us to build a deployment pipeline. Build a package once as a part of continuous integration and then push it thorught staging, tests etc to finally arrive at live environment.

Comment on Extending Sitecore ribbon with PowerShell scripts by Continuous deployment in Sitecore with PowerShell | Codality

Continuous deployment in Sitecore with PowerShell | Codality — Mon, 19 Dec 2011 11:42:26 +0000

[...] of this can be completely automated, all you need to do is create a Script item as described in one of my previous posts and call the PowerShell execution URL referencing your script from your CruiseControl server or [...]

Comment on Context PowerShell scripts for Sitecore by PowerShell driven Sitecore scheduled tasks | Codality

PowerShell driven Sitecore scheduled tasks | Codality — Tue, 29 Nov 2011 16:22:02 +0000

[...] now that you can easily create the menus and ribbons executing PowerShell scripts, it might be a good time to do some more administrative [...]

Comment on Context PowerShell scripts for Sitecore by Extending Sitecore ribbon with PowerShell scripts | Codality

Extending Sitecore ribbon with PowerShell scripts | Codality — Fri, 25 Nov 2011 13:42:33 +0000

[...] Code and Effect – solving problem with just enough amount of code – by Adam Najmanowicz « Context PowerShell scripts for Sitecore [...]

Comment on A story of a saved EPiServer site by Adam Najmanowicz

Adam Najmanowicz — Wed, 24 Aug 2011 11:40:17 +0000

The class is a standard ASP.NET class. you can read more about it on its MSDN Pages. What it tells ASP is that the file never changes. Without this ASP treats a control as different file every time.

Comment on A story of a saved EPiServer site by Eric Sims

Eric Sims — Mon, 22 Aug 2011 20:29:53 +0000

i’m having the same problem with an implementation using asp.net mvc and virtual path providers. could you tell me what CacheNoDependency does (since this looks like a episerver method and not an asp.net one)