Skip to content

Support VSHPROPID_SupportedMyApplicationTypes instead of VSHPROPID_SupportedOutputTypes for VB #4709

Open
@davidwengier

Description

@davidwengier

Part of #4249

For VB projects the MyApplication model means that we need to return a value for VSHPROPID_SupportedMyApplicationTypes, and we need to not return VSHPROPID_SupportedOutputTypes to override them. Alternatively we could take a different approach here, like perhaps using capabilities to enable specific MyApplicationTypes, and allowing them to override OutputTypes.

This will unblock more work to ensure these new application types are correctly supported, and we only show the right options.

Metadata

Metadata

Assignees

No one assigned

    Labels

    BlockedThis issue is blocked from making progress due to another issue.Feature-Legacy-Application-DesignerThe "Application Designer" otherwise known as the legacy project propertiesFeature-WinFormsFeatures related to bringing up the Windows Forms designer and related features.Feature-XAMLFeatures related to the XAML designer and display and manipulation of XAML files.Parity-Legacy-FeatureMissing features from the legacy project system.Triage-ApprovedReviewed and prioritized

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions