Cannot convert value "ignore" to type "System.Management.Automation.ActionPreference"

Cannot bind parameter 'ErrorAction'. Cannot convert value "ignore" to type "System.Management.Automation.ActionPreference" due to invalid enumeration values. Specify one of the following enumeration values and try again. The possible
enumeration values are "SilentlyContinue, Stop, Continue, Inquire".
    + CategoryInfo          : InvalidArgument: (:) [Stop-Service], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.StopServiceCommand
    + PSComputerName        : asnav-devweb-02
September 2 2013

Empty post links in BlogEngine.NET 2.8

After upgrading to the latest blogengine.net we noticed that the links for posts published after the upgrade were incorrect.

http://sharpfellows.com/post/.aspx

If you too notice this you will also be pleased to know that there is a patch available.

Passing just an array to ArgumentList in Powershell

What is the expected output from this command?

invoke-command -ScriptBlock { param($list) $list | %{ write-host $_ } } -ArgumentList @(@(1,2,3))

I would have expected:

> 1
> 2
> 3

But it seems to be:

> 1

After some experimenting and trying various ways to get this working as expected, I finally resorted to google and found a post on StackOverflow. So the way to do this is by putting a comma in the array to satisfy the parser:

invoke-command -ScriptBlock { param($list) $list | %{ write-host $_ } } -ArgumentList @(,@(1,2,3))

And now I get the output:

> 1
> 2
> 3

I don't think this is intuitive and I hope this will be addressed in the future. At least for now there is a way to do it.

Accessing older versions of SQL Server Data Tools (SSDT)

We are currently using SSDT to manage our database solutions and handle deployments. Sadly our databases are not compatible with the newer versions of SSDT so while we make the necessary changes to bring them in line we need to use an older version.

Our developer software isn’t well managed and we lost the installers to the supported version. Microsoft unfortunately only have the latest version available for public download. However if you have access to MSDN you can get to the previous versions which might get you out of a bind.

 

image

 

Hopefully this will save you the trouble of looking all over the web as I only stumbled upon it by chance.

Newer Posts Older Posts