locked
create a template for dssnewservice RRS feed

  • Question

  • hi,
    we just tried locate the template files which dssnewservice uses to create a  new service, but didnt succeed in finding them. we need to do some changes regarding the paths, which are used in the standart service templates. Does anyone know where to find them?

    thanks in advance for the help
    Thursday, November 15, 2007 2:49 PM

Answers

  • A portion of the template is embedded in one of our core assemblies, the rest is auto generated on the fly based on the data contracts and operations of the "default" service or the service you pass in with the /assemblyname parameter.

     

    What problem are you encountering which is leading you to change paths?

    Thursday, November 15, 2007 11:14 PM

All replies

  • A portion of the template is embedded in one of our core assemblies, the rest is auto generated on the fly based on the data contracts and operations of the "default" service or the service you pass in with the /assemblyname parameter.

     

    What problem are you encountering which is leading you to change paths?

    Thursday, November 15, 2007 11:14 PM
  • "A portion of the template is embedded in one of our core assemblies, the rest is auto generated on the fly based on the data contracts and operations of the "default" service or the service you pass in with the /assemblyname parameter."

    So there is no direct way? Something like "copy folder xxx, change the templates, use parameter yyy", is it? Because imho it would be great this way.


    "What problem are you encountering which is leading you to change paths?"

    We are working within a group of several people, in that almost each person installed the MSRS at another place and even the source code of the project is at very varying places... And we wanted to keep the MSRS/bin folder clean (which doesn't work anymore since the 1.5 refresh) and put our binaries to a specific place. But than we needed to show dssproxy where to go... etc. etc.
    In the end we created two environment variables, which we now use in our project files. But we had to hack our own dssnewservice to create acceptable projects.

    An example:
    <PostBuildEvent>"C:\Microsoft Robotics Studio\bin\dssproxy.exe" /dll:"$(TargetPath)" /proxyprojectpath:"$(ProjectDir)Proxy " /keyfile:"$(AssemblyOriginatorKeyFile)" $(ProxyDelaySign) $(CompactFrameworkProxyGen) /binpath:". " /referencepath:"C:\Microsoft Robotics Studio\bin\ " /referencepath:"C:\Microsoft Robotics Studio\bin\ " </PostBuildEvent>

    versus:
    <PostBuildEvent>"$(MSRS_PATH)\bin\dssproxy.exe" /dll:"$(TargetPath)" /proxyprojectpath:"$(ProjectDir)Proxy " /keyfile:"$(AssemblyOriginatorKeyFile)" $(ProxyDelaySign) $(CompactFrameworkProxyGen) /binpath:". " /referencepath:"$(MSRS_PATH)\bin\ " /referencepath:"$(MSRS_PATH)\bin\ "</PostBuildEvent>

    And at some places (e.g. linking to our own *.snk-file) we needed to change the project files. And we wanted to have the possibility to say directly that we want a subscribeable service, add the service to a solution...

    If you want, see this as a feature request.


    Greetings
    Monday, January 7, 2008 3:10 AM