Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

Why are the SilkPerformer menu options unavailable in Visual Studio.Net if the SilkPerformer Project Wizard is not used?

Why are the SilkPerformer menu options unavailable in Visual Studio.Net if the SilkPerformer Project Wizard is not used?

This behavior is by design; if a user chooses to create, or open, any Project other than a SilkPerformer Project in Visual Studio.NET then features of the SilkPerformer menu like Try-Script will be unavailable/grayed out. The reason for this behavior is that the .NET Add On which ships with SilkPerformer is designed to allow integration between Visual Studio.NET and SilkPerformer, it does this by installing SilkPerformer integration capabilities onto Visual Studio which can only be used by selecting the "SilkPerformer Project Wizard" when creating a New Project in Visual Studio.

 



The Menu will appear as above if you do not use "SilkPerformer Project Wizard" when creating a New Project in Visual Studio.

 

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:52
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.