Why can't I run a powershell file I created from a powershell function

Question

Ok so admittedly I am still learning a lot about powershell so this may have a very easy explanation/solution
So I have this script file and this is it in its entirety 
function Add-DriveFunctions($Provider, $Path)
foreach ($Drive in $Provider.Drives)
if ((Get-Command | where Name -eq "$($Drive.Name):") -eq $null)
[String]"function $($Drive.Name):() {Set-Location $($Drive.Name):}" | Out-File $Path -Append
$Path = C:\Temp\test.ps1
"""Adding Drives""" | Out-File $Path
foreach ($Provider in Get-PSProvider)
Add-DriveFunctions -Provider $Provider -Path $Path
C:\Temp\test.ps1
When I run it it happily creates the ps1 file whose content looks like this
 "Adding drives"
function Alias:() {Set-Location Alias:}
function Env:() {Set-Location Env:}
function Function:() {Set-Location Function:}
function HKLM:() {Set-Location HKLM:}
function HKCU:() {Set-Location HKCU:}
function Variable:() {Set-Location Variable:}
But the last line to actually load and run the ps1 file does nothing
even calling C:\Temp\test.ps1 does nothing
but if I load the file into ISE and run it from there
it works.
Unless I'm completely missing something I would think being able to call other ps1 files from other ps1 files or the command line would be a pretty important part of powershells flexibility.
So if anyone could tell me why in this case it does not work I would greatly appreciate that
Cheers,
Quidquid latine dictum sit, altum videtur

Answer 1

Ok i'm a little confused 
in ISE if I write a ps1 file and i have just a function in it not anything calling that function when i run or debug it loads that functions definition into the current session and then from my console i can access my function. so Is that what the . is supposed
to do?
When i tried the . I get this
The term '.C:\Temp\test.ps1' 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.At C:\Users\rjs012978\Downloads\FunctionTest.ps1:20 char:1
+ .C:\Temp\test.ps1
+ ~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (.C:\Temp\test.ps1:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
Also I know i can do that with the mono letter drive but working on a network over half the alphabet is taken up by my actual network mapped drives.
And the provider i'm writing is connecting to multiple Space IDs that i'm making into my drives so I would quickly run out of letters.
proof of concept i know what i'm doing works if I do it manually
I know it's kind of silly but for me the amount of time i spend in powershell especially administering SCCM, the registry and AD being able to just type hklm: and hitting enter is a huge time save over the long haul than typing cd hklm: even though it's
just 3 more characters
Quidquid latine dictum sit, altum videtur