/p command line parameter equivalent in SGen task

Hot Topic

placing service processing (Bus. Domain Layer) on app server
Excel OLE Link Using VSTO
SOLVED!!! but "Chapuza"
Localizing RDL and ReportViewer
Access parent doc in VSTO
HOWTO: AddIn Deployment with Shim for Framework1.1 & Framework2.0
login Failed
Problem with Class Designer and Pages and Controls
Can't install Office 2003's SP2 on machines with Visual Studio 2005 installed
API request: Chart drawing in Excel

Visual Studio

Need advice on how to structure a project in source safe
XamlReader and {StaticResource }
Debug breakpoints don't attach in managed code .h file
Applying a stylesheet to a report
Email on failure
How can I put one canvas on top of another? or How can I draw multiple layers in the same area?
VS2005 Registration Benefits - not allowed access to Registration Benefit Portal
VS .NET 2003 Prereq problem
Name of EventHandler called when Compartment item is selected?
Fu: Can not find keycodev2.dll, or invalid keycode - Developing across network

/p command line parameter equivalent in SGen task

Hi,

Is there a way to specify in the SGen task that it should call sgen.exe with the /p parameter I did not see anything in the help file. There is an AddCommandLineCommands function in the SGen task, but how do I envoke that from the build profile

It makes a huge difference timewise.

Thanks.

Answer this question

/p command line parameter equivalent in SGen task

  • Sasha

    Thanks. I already went down the path you suggested and pasted the task into my project and then replaced with with a call to sgen.exe. The SGen task must be doing extra work, however. The project references other assemblies. When you look at the assemblies in the Reference path and pass those in to the exec call as a parameter, the path is not correct. The path is relative and in relation to original project file. If you continue to use the InterMediate output path, sgen can't find the references.  I'd have to copy them or generate the assembly later on which seemed like a lot of extra trouble. I think I'll wait until it is fixed.

  • sumana

    Hi Gerhardo,
    In Beta 2 the task did not have support for this parameter. Since then, it has been added, with the property name "UseProxyTypes". Looking at the current internal microsoft.common.targets file, it's hard coded to "true":

            <SGen
                BuildAssemblyName="$(TargetFileName)"
                BuildAssemblyPath="$(IntermediateOutputPath)"
                References="@(ReferencePath)"
                ShouldGenerateSerializer="true"
                UseProxyTypes="true"
                KeyContainer="$(KeyContainerName)"
                KeyFile="$(KeyOriginatorFile)"
                DelaySign="$(DelaySign)"
                ToolPath="$(SGenToolPath)">

                <Output TaskParameter="SerializationAssembly" ItemName="SerializationAssembly"/>

            </SGen>

    If you need to get this to work for Beta 2, I don't see a workaround off the top of my head, except for using the <Exec> task to invoke Sgen directly. You would paste in the GenerateSerializationAssemblies target from Microsoft.Common.targets into your own project below where Microsoft.common.targets is imported by the project. This will override that target with your copy. Then you can remove the call to the <SGen> task and replace it with the equivalent use of the <Exec> task including the /p switch.

    Let us know if you get stuck.
    Dan (msbuild@microsoft.com)



  • /p command line parameter equivalent in SGen task
Answer this question