Regarding
In your CutomProjectConfig class you can override:
__<OutputType>custom_application</OutputType>__
you could use any string to identify what kind of output you wish. Or.. just handle EXE as shown below in switch.In your CutomProjectConfig class you can override:
public override int DebugLaunch(uint flags)
{
// This is actually should be used for debugging purposes in the future
try
{
string outputType = GetConfigurationProperty("OutputType", true);
switch(outputType)
{
case "custom_library":
ShowRunWarning();
break;
case "custom_application":
RunApplication();
break;
default:
Debug.Assert(false, "This should not be called.");
break;
}
}
catch(Exception e)
{
_logger.Error("Error in DebugLaunch.", e);
return Marshal.GetHRForException(e);
}
return VSConstants.S_OK;
}
VSX/MPF has a lot of places where you can adjust the standard flow. My advice would be to reuse as much as possible the standard scenario as it will cause less efforts to adjust. Most of the things you might want to adjust are provided as virtual methods in MPF base classes. So check them first for suitable methods to override. Override and set a breakpoint to ensure you are getting the expected data to handle.