I am trying to generate the proxy file from wcf service using svcutil.exe, but I didn't understand how to pass the parameters to svcutil to collection type as system.Collections.Generic.List
I tried the below command in visual studio command prompt.
svcutil http://localhost:19021/InterviewManagementService/InterviewManagementService.svc /l:C# /out:Reference.cs /config /s /ct:System.Collections.Generic.List`1 /t:code /n:*,newnamespace
Please correct me with the above command.
I think you need to specify the assembly for the referenced collection types (more info here).
When using the Svcutil.exe tool, this reference can be accomplished by using the /collectionType command-line switch (short form: /ct). Keep in mind that you must also specify the assembly for the referenced collection types using the /reference switch (short form: /r). If the type is generic, it must be followed by a back quote and the number of generic parameters. The back quote (`) is not to be confused with the single quote (‘) character. You can specify multiple referenced collection types by using the /collectionType switch more than once.
So you need to add /r:C:\full_path_to_system_dll\System.dll to your command right before /ct:System.Collections.Generic.List
Related
I have source and target in an informatica powercenter developer. I heed some other header name to be imported in the target file automatically without any manual entry. How can I import customized headers to informatica target.
What have you tried?
You can use a header command in the session configuration for the target, I haven't used it, and couldn't find any documentation on it (i.e. what is possible and how, whether parameters can be used or not, etc.). I did test using (on Windows) an ECHO command to output its text to the header row, but it didn't seem to recognize parameters.
Or you can try to include the header as the first data output row. That means your output will have to be all string types and length restrictions may compound the issue.
Or you can try using two mappings, one that truncates the files and writes the header and one which outputs the data specifying append in the session. You may need two target definitions pointing to the same files. I don't know if the second mapping would attempt to load the existing data (i.e. typecheck), in which case it might throw an error if it didn't match.
Other options may be possible, we don't do much with flat files.
The logic is,
In session command, there is an option called user defined headers. Type echo followed by column name separated by comma delimited
echo A, B, C
I'm using JSCS (google) for javascript and also JSHint, However if I autoformat my code with cmd+L it creates a space between function and an opening (. Is there anyway to tell the auto format function to obey to the coding guydes from JSCS?
You can't just tell it to obey this or that standard code style. But you can configure formatting options in Settings/Code Style/javascript. Try Spaces/Before Parentheses options: 'in function declaration', 'in function expression', 'function call parentheses'
Editor > Code Style > JavaScript
You can select Manage and import your JSCS file. This should cover the majority of your needs. Note that if you're just selecting Google from the drop down for your guide, you will need to download Googles JSCS file.
In Doxygen you use reference links: define them separately and then refer to them from within the text.
/**
* This is a documentation. Here I link [std::string] to an external web page.
*
* The next line is the link definition:
*
* [std::string]: http://en.cppreference.com/w/cpp/string/basic_string "std::string documentation"
*/
However it seems that the link definition is seen only within the documentation block. It is not seen even on other documentation blocks on the same page.
I want to define some links once, and then use them everywhere (on different pages).
Is that possible?
Edit (follow-up question)
In order to achieve your aim I think your best bet is to make use of the ALIAS facility.
I have managed to set it up with alias like this:
ALIASES += std_string="std::string "
ALIASES += std_vector="std::vector "
And using it:
#std_string
#std_vector
Basically I have one alias for each link.
Can it be achieved with one alias with parameters? The use would be:
#std_ref std::string
#std_ref std::vector
The problem is that some sort of map is needed between the name (the parameter) and the link:
std::string -> http://en.cppreference.com/w/cpp/string/basic_string
std::vector -> http://en.cppreference.com/w/cpp/container/vector
I know it can be done if one parameter would be the different part of the link, like :
#std_ref std::string string/basic_string
#std_ref std::vector container/vector
But this is ugly, error prone and would require to check each time what the link should be.
It's worth noting that what you are currently using is the notation that comes only with Doxygen's support for Markdown - it's not the doxygen method for external links. The original Doxygen method is to insert an HTML link inline...
link text
... but that makes no difference to your original problem.
In order to achieve your aim I think your best bet is to make use of the ALIAS facility. The relevant manual page is here. Using them, you should be able to define an alias like std-string and have it insert the HTML link everywhere you use the alias.
ALIASES are set up in the doxyfile config file (in this section of the manual)
You could set up aliases manually for every C++ keyword, that you want to link to, but the better way to do this is to use the doxygen TAGFILES feature.
A tag file is basically a compact representation of the entities found in the external sources. Doxygen can both generate and read tag files.
To generate a tag file for your project, simply put the name of the tag file after the GENERATE_TAGFILE option in the configuration file.
To combine the output of one or more external projects with your own project you should specify the name of the tag files after the TAGFILES option in the configuration file.
Doxygen has a whole page dedicated to explaining how to link to external documentation
And cppreference.com has already setup a tag file for you with some basic instructions.
For the impatient:
Download File:cppreference-doxygen-web.tag.xml for linking directly to cppreference.com website.
Add this line to your Doxyfile:
TAGFILES += "location/of/cppreference-doxygen-web.tag.xml=http://en.cppreference.com/w/"
It's a question about C/C++ command line parser.
I used the command line parsers provided in glib and Boost, but I found them not satisfying. I have two special requirements:
multiple values following one key, so that I can use file glob on command line like this:
my_program --input dir/*.txt
customized value type, like this:
typedef enum { FORMAT_A, FORMAT_B, FORMAT_C } InputFormat;
InputFormat option_format;
I want my user can specify the format in command line --format format_a. The parser need to allow customized callback function to recognize the string value and set the enum value.
It seems boost supports 1 but not 2. It only allow you define an additional parser that traverse the tokens one by one, but not by KV pairs. And glib supports 2 but not 1. It only allows multiple calling like --input foo --input bar.
Any more libs that support both 1 and 2? Or any suggestions on advanced use of glib or boost to achieve both 1 and 2?
Boost can in fact handle requirement 2. You'll need to create your own child of value_semantic with an appropriate parser and pass an instance of that into add_options rather than using the typical value<int>() mechanism.
I am trying to write/modify a jelly script in Jenkins Email-Ext that returns the build log. I am trying to filter the log with BUILD_LOG_REGEX for regular expressions. Can someone give me a sample script or format for doing build_log_regex using jelly script template? Thanks in advance.
The default template that you can use as your starting point is located in
$JENKINS_HOME/plugins/email-ext/WEB-INF/classes/hudson/plugins/emailext/templates/html.jelly
The ${BUILD_LOG_REGEX} token is used in the Default Content section of email-ext and typically not inside of the Jelly script. To use it, just change your Default Content to reference this token:
The developer of email-ext recommended switching from Jelly to Groovy since they have "more power, its easier to use and you can prototype stuff in the script console to some degree".
See https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin#Email-extplugin-Scriptcontent
You can then look at the source code for BuildLogRegexContent class on how this token is implemented and write code to produce exactly what you want.