In Progress

Migrate existing Web Service and client side .dll to WCF

Migrate existing Web Service and client side .dll to WCF.

This is an existing Web Service that is used to send send and receive binary files from a client’s VB6 application. The Web Service and Client .dll are written in VB.NET and the client .dll is complied for use by a COM object (a VB6 Application). I have attached the original Web Service specifications for review. I will supply the .net code and related files to reproduce the current working project.

Step 1: Re-Write the older Web Service into a WCF Web Service and test it out with a .net test application. I have no problems if the developer wants to re-write it in C# or leave it in VB.NET.

Step 2: Include the new functionality into the WCF. Here is what we need to be able to do:

1) Change the default port number used by the client to connect to the web service

2) Give the client the ability to send and receive the binary files through the clients Proxy. Must include the ability to get through the following:

a) Bluecoat

b) Gauntlet

c) Interlock

d) OPEN Command Sent

e) SITE Command Sent

3) Parameter to the call to the client side .dll to do the above. We will need the parameters below, plus whatever is needed to select the port and proxy settings.

Current calls to client side .dll. SendFile() and GetFile():

ans = [url removed, login to view](FileName, FileLocation, UserName, Password, ClientNo, CompDesc,wsLocation)

This will call to the client side .dll will send a binary file to our server through the Web Service

ans = 0 if unsuccessful, 1 if successful

Parameters:

FIleName: File that needs to be sent

FIleLocation: Location of the file at the client end

UserName: Web Service Authentication. From Web Service [url removed, login to view]

Password: Web Service Authentication. From Web Service [url removed, login to view]

ClientNo: Client Number (Pass through to Web Service)

CompDesc: Company Description (Pass through to Web Service)

wsLocation: Actual address of the web service on our server

ans = [url removed, login to view](FileName, FileLocation, UserName, Password, ClientNo, wsLocation)

This will call to the client side .dll will request a binary file to from server through the Web Service

ans = 0 if unsuccessful, 1 if successful

Parameters:

FIleName: File that needs to be got

FIleLocation: Location to put the file on the client end

UserName: Web Service Authentication. From Web Service [url removed, login to view]

Password: Web Service Authentication. From Web Service [url removed, login to view]

ClientNo: Client Number (Pass through to Web Service)

wsLocation: Actual address of the web service on our server

I have added the following to my first poster:

4) Ability for the client dll to log to a .txt file with possibility of three levels of logging (warnings, errors, debug mode)
5) An option for the client dll to communicate to a secure web server (https://) and verify its SSL certificate

Skills: .NET, C# Programming, Visual Basic

See more: migrate dll wcf, what we need for web developer, what is vb net used for, what is com in vb.net, web service developer, web application specifications, visual web developer 2013, vb6 developer, successful web developer, server supply review, original client, need net developer description, e service company, client side code, binary problems, binary code test, application site web, vb6 to vb.net, bluecoat proxy server, needs and wants, web service to receive, net wcf, i need vb net developer, client change, c# wcf

About the Employer:
( 20 reviews ) Greensboro, United States

Project ID: #4307297