Epson TM-U220 ePOS-Print XML Users Manual - Page 61

How to Use WSDL, .NET Framework

Page 61 highlights

Chapter 3 Programming Guide How to Use WSDL This section describes how to generate client codes (proxy class) from WSDL by using the tool provided in the development environment. This section uses the following cases as examples:  .NET Framework (p.61)  Java (p.63) .NET Framework Tool Command Item Description ServiceModel Metadata Utility Tool (Svcutil.exe) svcutil.exe epos-print-x.x.x.wsdl epos-print-x.x.x.xsd For details about the Svcutil.exe tool, refer to the following Web site (as of September, 2015): https://msdn.microsoft.com/en-us/library/aa347733.aspx Procedure 1 From the command prompt, execute Svcutil.exe and create the following files: ❏ ePOSPrint.cs (WCF contract) ❏ output.config (application configuration file) 2 Start Visual Studio and create a new project. (Project example: console application) 3 Add a class file to the project. (File to be added: ePOSPrint.cs) 4 Add a reference to the project. (Assembly to be added: System.ServiceModel) 5 Edit the application configuration file. (File to be edited: App.config) ❏ Open output.config and copy the element. ❏ Change the end point address in accordance with the printer. 61

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236

61
Chapter 3
Programming Guide
How to Use WSDL
This section describes how to generate client codes (proxy class) from WSDL by using the tool provided in the
development environment.
.NET Framework
Procedure
1
From the command prompt, execute Svcutil.exe and create the following files:
ePOSPrint.cs (WCF contract)
output.config (application configuration file)
2
Start Visual Studio and create a new project.
(Project example: console application)
3
Add a class file to the project.
(File to be added: ePOSPrint.cs)
4
Add a reference to the project.
(Assembly to be added: System.ServiceModel)
5
Edit the application configuration file.
(File to be edited: App.config)
Open output.config and copy the <system.serviceModel> element.
Change the end point address in accordance with the printer.
This section uses the following cases as examples:
.NET Framework (p.61)
Java (p.63)
Item
Description
Tool
ServiceModel Metadata Utility Tool (Svcutil.exe)
Command
svcutil.exe epos-print-x.x.x.wsdl epos-print-x.x.x.xsd
For details about the Svcutil.exe tool, refer to the following Web site (as of September, 2015):