Question profil powershell sur mon home network

bon déja, je vais chercher ce que signifie 'exécuté en dotsource'

même si ca reste un contournement...

Windows Powershell has the profile location hard-coded.
As a result, system administrators and end-users have no control over where the profile is stored.
Furthermore, the fixed location is in a location that is affected by other factors.
In particular, since the location is a subdirectory of the \"My Documents\" folder, it is affected by the location of My Documents,
which may be on a remote location and affected by other limitations of that location.
This causes problems when attempting to start up powershell in certain environments.
In particular, my user profiles are configured with My Documents as a remote share.
If that remote share is inaccessible, the Powershell can't be loaded.
If that share is accessible, but on a slow link, it takes a very long time for Powershell to startup.
Furthermore, it's not possible to have distinct powershell configurations per machine in this scenario.
If the user chooses to use a remote share for \"My Documents\", he is also forced to use that remote share for his Powershell Profile.
This issue has been brought up in the past.
See: connect.microsoft.com/feedback/ViewFeedb...=53055&SiteID=99 connect.microsoft.com/PowerShell/feedbac...iate-in-my-documents
There is a clear dissenting opinion, and I'm re-raising the issue, specifically because of the undesirable behavior the design creates.
In my opinion, the choice for the default location of the profile is a reasonable one, and the reasons given for the choice of the location are acceptable.
What is not acceptable, however, are the collateral faults that this design brings, especially when the location of the profile could be easily overridden
by a registry setting or (less desirable) a command-line argument to the powershell interpreter.
In #53055, Microsoft said, \"Changing the user location for PowerShell would be a breaking change at this point.\"
While it is true that changing the default location might be a breaking change,
it would be entirely reasonable to add a startup hook that checks a registry setting or similar, where end-users and administrators could define a custom location
to avoid the problems with loading a profile from a remote location. As of yet, no one has given a good reason why a user must be forced to (attempt to)
load the profile from a single, fixed location which already has other constraints placed on it.
I ran into this same problem with Remote Desktop (which stores its settings in %mydocuments%\default.rdp), but that was fixed with a hidden registry setting.
I ran into this same problem with Dropbox (which liked to place the dropbox in the %mydocuments% folder), but they fixed this by allowing the location to be
customized at installation. The only product I've ever used which consistently insists on not addressing these easily-reproducible problems is Powershell.
I find it particularly embarrassing when I'm demonstrating to another power user how great PowerShell is, but I have to apologize for the shortcomings.
These issues cause me lost productivity and consternation.
Please fix this issue.
Thanks.