Does this cmdlet not do what I think it does (I don't get a man page
for it)?

I was hoping it would re-load the profile, so I could start a session,
decide I need a function adding to the profile, edit the profile, type
'up' and be able to make use of the new function without having re-
start the powershell...

Thanks,

Duncan.

On Mar 29, 5:56 am, "Duncan Smith" <DSmith1...@googlemail.com> wrote:
> Does this cmdlet not do what I think it does (I don't get a man page
> for it)?
>
> I was hoping it would re-load the profile, so I could start a session,
> decide I need a function adding to the profile, edit the profile, type
> 'up' and be able to make use of the new function without having re-
> start the powershell...
>
> Thanks,
>
> Duncan.

You can simply do what's called "dot sourcing" to re-load your profile
script. Just type:

.. $profile

($profile is a built-in variable pointing to your profile file)

You can do this with any script, actually. You may have to re-sign
the script if you have your execution policy set to require signed and
trusted scripts.

Aaron

On Mar 29, 2:09 pm, aaronle...@gmail.com wrote:
> On Mar 29, 5:56 am, "Duncan Smith" <DSmith1...@googlemail.com> wrote:
>
> > Does this cmdlet not do what I think it does (I don't get a man page
> > for it)?
>
> > I was hoping it would re-load the profile, so I could start a session,
> > decide I need a function adding to the profile, edit the profile, type
> > 'up' and be able to make use of the new function without having re-
> > start the powershell...
>
> > Thanks,
>
> > Duncan.
>
> You can simply do what's called "dot sourcing" to re-load your profile
> script. Just type:
>
> . $profile
>
> ($profile is a built-in variable pointing to your profile file)
>
> You can do this with any script, actually. You may have to re-sign
> the script if you have your execution policy set to require signed and
> trusted scripts.
>
> Aaron

Ah of course, I hadn't thought of dot-sourcing it back in.

Thanks,

Duncan.