Re: Random psh stuff.
- From: "Lee Holmes [MSFT]" <lee.holmes@xxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 26 Apr 2006 11:11:46 -0700
2/3) Sure! Other considerations were:
[C:\temp]
PS:55 > $random = new-object Random
[C:\temp]
PS:56 > $output = $null; 1..100 | % { $output += [char]$random.Next(97,
122) }; "$output.ps1"
wvrybyxwmtcftvhnsvbednocjrdkcyysjtwnhbkkfrgtamxxdbeckjjjgopivnumtjuaxsgrlpylhucvtegauwhajnhrlbnqwsyp.ps1
[C:\temp]
PS:57 > $output = $null; 1..100 | % { $output += [char]$random.Next(97,
122) }; "$output.ps1"
rwyjumqtjxbklsorgtrwbuqklnfjbhonulevewfhfnpllvgslvkcacowgowgggrbinpynsminjqneeypglwewlmswhopaxbxuocx.ps1
[C:\temp]
PS:58 > $output = $null; 1..100 | % { $output += [char]$random.Next(97,
122) }; "$output.ps1"
ggfsjbnqlbrbogytjmdvavcfevioirsocbjageuvwvhuomasxgohkfwjeynnryhsidynwynerhxdogpqupqcclevdavgpgexonml.ps1
[C:\temp]
PS:59 > $output = $null; 1..100 | % { $output += [char]$random.Next(97,
122) }; "$output.ps1"
mmuyrkodgttwjwschfqvxckwdgnlcynbtdditrjrvboifywsnbqjwpnkbxulvcahfscfskhpuxawnbqeiuxbieddpsgvvxutahdm.ps1
:)
Actually, the reason we have the $profile variable is to make this as short
as possible, while still serving our extensibility needs.
The PowerShell model supports the concept of multiple shells. For example,
the PowerShell.exe console application is the main shell. It has a certain
Shell ID. Karl Prosser's MshAnalyzer is another shell. It has its own
Shell ID. In the future, we will have a GUI host that also has its own Shell
ID. You may want code that runs in one of those shells, but not the others.
Access to $host.UI.RawUI is something that you would probably want to be
specific to a shell, for example.
In those situations, you would use the $profile variable. That variable
refers to the profile specific to the current shell. Its name derives
primarily from the Shell ID of the current shell. In contrast, the plain
"profile.ps1" file is loaded for every shell.
Technically, the PowerShell engine loads profiles in the following order:
1) "All users" profile is loaded from "\Documents and settings\All
users\PsConfiguration\profile.ps1"
2) "All users," host-specific profile is loaded from "\Documents and
settings\All users\PsConfiguration\Microsoft.PowerShell_profile.ps1"
3) Current user profile is loaded from "<My
Documents>\PsConfiguration\profile.ps1"
4) Current User, host-specific profile is loaded from "<My
Documents>\PsConfiguration\Microsoft.PowerShell_profile.ps1"
At this stage of the game, it doesn't really matter which you use if you use
only PowerShell.exe. I personally use the zenfully correct $profile to hold
my modifications, though.
4) This is not something that we would want to support broadly. If things
like "cd.." and "cd\" are important to you, it's best to add them as
functions to your profile.
--
Lee Holmes [MSFT]
Windows PowerShell Development
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
"William Stacey [MVP]" <william.stacey@xxxxxxxxx> wrote in message
news:utqphKVaGHA.1020@xxxxxxxxxxxxxxxxxxxxxxx
1) Powersh.exe used in places in the docs. Should be Powershell.exe I
guess.
2) Microsoft.PowerShell_Profile.ps1 - Could that be any longer?
3) "The profile Microsoft.PowerShell_profile.ps1 will only be run for the
shell with the matching ShellID..."
What does this mean in practice? What is the actual difference between
profile.ps1 and MS.powershell_profile.ps1?
4) In cmd.exe I can "cd\" or "cd\temp", but in ps I need a space like "cd
\"
or "cd \temp". Would this break too much to allow no space?
tia
--
William Stacey [MVP]
.
- Follow-Ups:
- Re: Random psh stuff.
- From: William Stacey [MVP]
- Re: Random psh stuff.
- From: klumsy
- Re: Random psh stuff.
- References:
- Random psh stuff.
- From: William Stacey [MVP]
- Random psh stuff.
- Prev by Date: Re: Change password for specific users in AD every 30 days
- Next by Date: Re: [MSH] How do I get rid of the MonadLog in eventvwr
- Previous by thread: Re: Random psh stuff.
- Next by thread: Re: Random psh stuff.
- Index(es):
Relevant Pages
|
