You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// Implements the IVsSingleFileGenerator.DefaultExtension method.
36
+
/// Returns the extension of the generated file
37
+
/// </summary>
38
+
/// <param name="pbstrDefaultExtension">Out parameter, will hold the extension that is to be given to the output file name. The returned extension must include a leading period</param>
39
+
/// <returns>S_OK if successful, E_FAIL if not</returns>
/// Implements the IVsSingleFileGenerator.Generate method.
57
+
/// Executes the transformation and returns the newly generated output file, whenever a custom tool is loaded, or the input file is saved
58
+
/// </summary>
59
+
/// <param name="wszInputFilePath">The full path of the input file. May be a null reference (Nothing in Visual Basic) in future releases of Visual Studio, so generators should not rely on this value</param>
60
+
/// <param name="bstrInputFileContents">The contents of the input file. This is either a UNICODE BSTR (if the input file is text) or a binary BSTR (if the input file is binary). If the input file is a text file, the project system automatically converts the BSTR to UNICODE</param>
61
+
/// <param name="wszDefaultNamespace">This parameter is meaningful only for custom tools that generate code. It represents the namespace into which the generated code will be placed. If the parameter is not a null reference (Nothing in Visual Basic) and not empty, the custom tool can use the following syntax to enclose the generated code</param>
62
+
/// <param name="rgbOutputFileContents">[out] Returns an array of bytes to be written to the generated file. You must include UNICODE or UTF-8 signature bytes in the returned byte array, as this is a raw stream. The memory for rgbOutputFileContents must be allocated using the .NET Framework call, System.Runtime.InteropServices.AllocCoTaskMem, or the equivalent Win32 system call, CoTaskMemAlloc. The project system is responsible for freeing this memory</param>
63
+
/// <param name="pcbOutput">[out] Returns the count of bytes in the rgbOutputFileContent array</param>
64
+
/// <param name="pGenerateProgress">A reference to the IVsGeneratorProgress interface through which the generator can report its progress to the project system</param>
65
+
/// <returns>If the method succeeds, it returns S_OK. If it fails, it returns E_FAIL</returns>
0 commit comments