Comments on: VS2005 PowerShell Prompt http://rwandering.net/2006/05/02/vs2005-powershell-prompt/ The blogged wandering of Robert W. Anderson Sun, 11 Mar 2012 16:24:45 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Lior Elia http://rwandering.net/2006/05/02/vs2005-powershell-prompt/comment-page-1/#comment-190420 Lior Elia Thu, 15 Jan 2009 17:41:44 +0000 http://rwandering.net/2006/05/02/vs2005-powershell-prompt/#comment-190420 There's a little bug in the script. The double backslash after "ENV:" causes all new variables to be prefixed with a backslash. So you get for example "\VCINSTALLDIR=c:\..." instead of "VCINSTALLDIR=c:\..." The string in that line should be instead: <code> "ENV:\$($v[0])" </code> There’s a little bug in the script.
The double backslash after “ENV:” causes all new variables to be prefixed with a backslash.
So you get for example “\VCINSTALLDIR=c:\…” instead of “VCINSTALLDIR=c:\…”
The string in that line should be instead:

"ENV:\$($v[0])"

]]> By: dreamlusion http://rwandering.net/2006/05/02/vs2005-powershell-prompt/comment-page-1/#comment-168837 dreamlusion Sun, 06 Jul 2008 13:38:34 +0000 http://rwandering.net/2006/05/02/vs2005-powershell-prompt/#comment-168837 Hi Robert, Windows PowerShell profile locations have changed since this post was written: http://www.google.com/search?q=windows+powershell+profiles+site%3Amicrosoft.com So this "$home/My Documents/PSConfiguration/Microsoft.PowerShell_profile.ps1" should be: "$home/My Documents/WindowsPowerShell/Microsoft.PowerShell_profile.ps1" Just my two cents. Hi Robert,

Windows PowerShell profile locations have changed since this post was written:
http://www.google.com/search?q=windows+powershell+profiles+site%3Amicrosoft.com

So this “$home/My Documents/PSConfiguration/Microsoft.PowerShell_profile.ps1″ should be:
“$home/My Documents/WindowsPowerShell/Microsoft.PowerShell_profile.ps1″

Just my two cents.

]]> By: An error occurred when merging assemblies: Access to the path ‘…’ is denied. « Dreamlusion’s blog http://rwandering.net/2006/05/02/vs2005-powershell-prompt/comment-page-1/#comment-168835 An error occurred when merging assemblies: Access to the path ‘…’ is denied. « Dreamlusion’s blog Sun, 06 Jul 2008 13:32:15 +0000 http://rwandering.net/2006/05/02/vs2005-powershell-prompt/#comment-168835 [...] You may need a Visual Studio PowerShell Prompt to do [...] [...] You may need a Visual Studio PowerShell Prompt to do [...]

]]> By: Robert W. Anderson http://rwandering.net/2006/05/02/vs2005-powershell-prompt/comment-page-1/#comment-27676 Robert W. Anderson Sat, 13 May 2006 15:43:58 +0000 http://rwandering.net/2006/05/02/vs2005-powershell-prompt/#comment-27676 Lee -- thanks for the comment -- I've been reading your blog for some time, but I missed that detail. I suspect this works for the VS variables, but I'll update the post soon. Thanks, again. Lee — thanks for the comment — I’ve been reading your blog for some time, but I missed that detail. I suspect this works for the VS variables, but I’ll update the post soon.

Thanks, again.

]]> By: Lee http://rwandering.net/2006/05/02/vs2005-powershell-prompt/comment-page-1/#comment-27675 Lee Sat, 13 May 2006 06:23:17 +0000 http://rwandering.net/2006/05/02/vs2005-powershell-prompt/#comment-27675 Hi Robert; That script has a slight bug in that any environment variables with '=' in them will not be set correctly. Here's another option, at the bottom of http://www.leeholmes.com/blog/NothingSolvesEverythingPowerShellAndOtherTechnologies.aspx Lee Hi Robert;

That script has a slight bug in that any environment variables with ‘=’ in them will not be set correctly. Here’s another option, at the bottom of http://www.leeholmes.com/blog/NothingSolvesEverythingPowerShellAndOtherTechnologies.aspx

Lee

]]>