Powershell script call functions

Question

trying to do something insanely simple in PS but for some odd reason it is just not playing ball. My PS script looks like:

For some reason its complaining about the fact that:

enableMSDTC : The term 'enableMSDTC' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Am I not allowed to do this? I have to have a separate script file for each function?

Thanks in advance, DS.

    param
    (
        [string]$folder = $(throw 'Local folder to map to is required.')
    )

    begin
    {
        [void][System.Reflection.Assembly]::LoadWithPartialName("Microsoft.TeamFoundation.Client")
    }
    process
    {
$hasDrive = Test-Path -Path "D:\"

    if ($hasDrive -eq $true) {
        echo "Enabling MSDTC settings..."
        enableMSDTC    
    }

    Function enableMSDTC() {
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "LuTransactions" -Value "1"
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "NetworkDtcAccess" -Value "1"
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "NetworkDtcAccessAdmin" -Value "1"
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "NetworkDtcAccessClients" -Value "1"
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "NetworkDtcAccessInbound" -Value "1"
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "NetworkDtcAccessOutbound" -Value "1"
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "NetworkDtcAccessTransactions" -Value "1"
        Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\MSDTC\Security" -Name "NetworkDtcAccessXaTransactions" -Value "1"        
    }
}

EBGreen · Accepted Answer · 2014-03-12 17:02:17Z

1

Define the function before you try to call it.

answered Mar 12, 2014 at 17:02

EBGreen

38k12 gold badges69 silver badges86 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Dr Schizo Over a year ago

Dear god didn't realise it was procedural! Thank you.

EBGreen Over a year ago

Bit me in the butt all the time when I started. :)

JNK · Accepted Answer · 2014-03-12 17:04:20Z

0

Powershell is an interpreted language, which means commands are parsed in order (top down) at run time.

You can't call a function or refer to a variable before you define it.

answered Mar 12, 2014 at 17:04

JNK

65.5k15 gold badges127 silver badges138 bronze badges

1 Comment

EBGreen Over a year ago

Well, just to be pedantic, Interpreted vs. Compiled language doesn't determine this. For example, VBScript is an interpreted language and you can put functions at the end of a file with no problem at all. It simply depends on the way that the interpreter behaves.

Collectives™ on Stack Overflow

Powershell script call functions

2 Answers 2

2 Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related