Support Forums

I apologize if you took my attempt to be brief for any kind of emotional reaction. I was simply trying to be brief and efficient. Having said that, I will try to be more verbose. 1. I verified this and filed a bug report. As far as I know it is supposed to be black on white, but the installer vendor...

Hmm, I would go with that the event handlers should ALWAYS be with the form and all other functions and handlers associated with the particular form. But there is nothing that keeps you from calling the same validating function from the different event handlers. That also makes it easier to add spec...

Yeah, I know. I just filed an internal bug report to change that. We added the button because folks couldn't find their subscription numbers

No, mixing assemblies is something you need to talk to Microsoft to, specifically the SQL Server team. They should have released versions of their stuff compatible with later .NET versions.

Please provide the exact version number of your PowerShell Studio installation. PLEASE do not post the subscription number again

I will confer with the team, but I am guessing that they check for the specific Powershell versions supported by this version and when they are not found, it is disabled.

There is an option on the packager dialog to generate a config file. Did you check that?

Please do NOT post subscription information in this forum!

PowerShell Studio 2014 was release before PowerShell 5.0, so I guess that should be expected. You should still be able to run V2 mode. Can you verify that?

[Moved by moderator]
That is not a product problem. A standard text box does not cut text like that. You should check the properties you have set.

"The license information is black text on dark grey. Its nearly unreadable and probably not even allowed even by US laws, let alone EU. " Can you provide a screen shot? I am not sure what you mean by "license information". You mean the EULA? "There was no notification that e...