PowerShell Studio 2012/ Project Behavior Strangeness
Posted: Thu Feb 14, 2013 8:06 am
I just installed PowerShell Studio 2012 & ChangeVue 2012. Although most things make sense, there are a couple of behaviors I can't seem to understand, and can't find a work around for.
Projects: Export
Almost everything I do is a project of some such and I often have several files in the project that either work together, or stand alone, but are still all part of the project.
Whenver I have a single file open from a project, and I click on the Export tab, I only have the options available under the "Project" section. Rarely would I ever want to export the entire project into one file. I frequently want to export one file from the project however. The Export to File & Export to Clipboard options are both grayed out when working with a single file in a project.
This becomes very problematic for me when I want to just export the one file to another location. I end up copying/pasting into a new document, and it's really a kludge to do, consider it's something I need to do often.
It would be great to be able to export the entire project as individual files (and sign each one).
Projects: Code Signing
Basically similiar problems to above. When I have one file open from a project that I want to sign, I can't. Again, the Sign Script functionality is grayed out, regardless of if I have it checked out, changed, anything. The only way to make use of this function is to manually copy the file out of the project, then reopen it as a single file, sign it. Again, a bit of a kludge for a process I need to do frequently.
Projects Panel overall:
It seems to become dead weight when you are truly working with a single file. If you have a folder of items (in trying to work around the above issues and use a different process) you can't really tell their status in Source Control, and the Projects Panel is empty. Is there anyway it can be used as a Folder/File browser when not a Project panel? Then it could reflect the source control context of the files as well.
Export:
Even when opening a single file not in Source Control, not in a project, the Export to File, and Export to Clipboard are again grayed out under the File section of Export.
Script Signing:
Is there anyway to get support for multiple certficates and be able to choose at the time of signing which certificate to use? I have several certificates depending on if it's going to a public resource, production, internal uat, test, dev, or client machines. With Windows PowerShell ISE, I was able to write functions to faciliate this, but haven't found a method to enable that with PowerShell Studio 2012.
To heavily leverage source control & the project functionality, these couple of items with exporting & code signing are killing me. I'm ready to buy, as I haven't found anything else I like as much. (although I am digging PowerGui). Any suggestions or possible changes/fixes to these items behavior?
Projects: Export
Almost everything I do is a project of some such and I often have several files in the project that either work together, or stand alone, but are still all part of the project.
Whenver I have a single file open from a project, and I click on the Export tab, I only have the options available under the "Project" section. Rarely would I ever want to export the entire project into one file. I frequently want to export one file from the project however. The Export to File & Export to Clipboard options are both grayed out when working with a single file in a project.
This becomes very problematic for me when I want to just export the one file to another location. I end up copying/pasting into a new document, and it's really a kludge to do, consider it's something I need to do often.
It would be great to be able to export the entire project as individual files (and sign each one).
Projects: Code Signing
Basically similiar problems to above. When I have one file open from a project that I want to sign, I can't. Again, the Sign Script functionality is grayed out, regardless of if I have it checked out, changed, anything. The only way to make use of this function is to manually copy the file out of the project, then reopen it as a single file, sign it. Again, a bit of a kludge for a process I need to do frequently.
Projects Panel overall:
It seems to become dead weight when you are truly working with a single file. If you have a folder of items (in trying to work around the above issues and use a different process) you can't really tell their status in Source Control, and the Projects Panel is empty. Is there anyway it can be used as a Folder/File browser when not a Project panel? Then it could reflect the source control context of the files as well.
Export:
Even when opening a single file not in Source Control, not in a project, the Export to File, and Export to Clipboard are again grayed out under the File section of Export.
Script Signing:
Is there anyway to get support for multiple certficates and be able to choose at the time of signing which certificate to use? I have several certificates depending on if it's going to a public resource, production, internal uat, test, dev, or client machines. With Windows PowerShell ISE, I was able to write functions to faciliate this, but haven't found a method to enable that with PowerShell Studio 2012.
To heavily leverage source control & the project functionality, these couple of items with exporting & code signing are killing me. I'm ready to buy, as I haven't found anything else I like as much. (although I am digging PowerGui). Any suggestions or possible changes/fixes to these items behavior?