Votes from Connect: 3

Original Date Submitted: 10/27/2015 6:11:19 PM

Description:
Contact Information
Handle: jwirl
Site Name: PowerShell
Feedback ID: 1950051

Frequency: PowerShell ISE
Regression: 1. Open a script file in PowerShell ISE.
2. Open up the same script file in another editor i.e. notepad++ or Microsoft Visual Studio
3. Make a change to the script file in the other editor and save it.
4. Return to PowerShell ISE, it does not warn you that the script file has been changed else where and it does not re-load the script file into the ISE window.
5. Make a change to the script file in PowerShell ISE and save it.
6. Switch back to the other editor, it warns you that the file has been modified and asks you do you want to reload.
7. When you click 'Yes' to reload it loads the file and you loose the changes you made in the alternative editor.

Problem Description:
PowerShell ISE does not detect changes to a file open in PowerShell ISE when that file is modified outside of PowerShell ISE.

When a file that you have opened in PowerShell ISE is modified outside of ISE, when you return to the PowerShell ISE window it does not detect this and then you can go ahead and make a change in PowerShell ISE and loose the changes that were made outside of PowerShell ISE.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 1950051 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=1950051).

Repro Steps:
1. Open a script file in PowerShell ISE.
2. Open up the same script file in another editor i.e. notepad++ or Microsoft Visual Studio
3. Make a change to the script file in the other editor and save it.
4. Return to PowerShell ISE, it does not warn you that the script file has been changed else where and it does not re-load the script file into the ISE window.
5. Make a change to the script file in PowerShell ISE and save it.
6. Switch back to the other editor, it warns you that the file has been modified and asks you do you want to reload.
7. When you click 'Yes' to reload it loads the file and you loose the changes you made in the alternative editor.

Expected Results:
If the file you are editing in PowerShell ISE is modified outside of that environment then PowerShell ISE should detect this when you return to the PowerShell ISE window and ask if you want to reload the file. This process is especially common when you are saving script file versions to a source code repository such as git, subversion etc.

Internal BugId: 15926

Votes from Connect: 39

Original Date Submitted: 5/6/2013 2:09:18 PM

Description:
Contact Information
Handle: Real McCoy
Site Name: PowerShell
Feedback ID: 786397

Frequency: Always Happens
Regression: Yes, this happens in all previous versions

Problem Description:
[Redirected from http://social.technet.microsoft.com/Forums/en-US/winserverpowershell/thread/f70168bf-f575-47c7-b889-3c38dd6a776a]
I guess the lack of out-of-the-box support for the open protocol, such as SSH and SFTP in Windows shells is one the main reason the PHP, Ruby and Python developers don't feel nativity in Windows ecosystem.

Windows Azure supports SSH, so what's stopping Windows PowerShell and Command Prompt teams to implement these proven and massively adopted protocols in their commands bucket? Is it due to any legal (open source licensing) issue?

Since TFS team is pushing git support in upcoming release of Visual Studio, it would be nice if Windows guys implement SSH and SFTP in Windows vNext.

Product Studio item created by Connect Synchronizer due to creation of feedback ID 786397 (http://connect.microsoft.com/PowerShell/feedback/ViewFeedback.aspx?FeedbackID=786397).

Repro Steps:
SSH, SFTP and SCP are widely adopted protocols and their absence in Windows ecosystem is fending away the developers.

Expected Results:

Implement SSH, SFTP and SCP in Windows Shell and PowerShell to address the need of developers all around the globe.

Internal BugId: 4199