Project Detail

Description

This is a really simple exercise that has had me banging my head on the wall for a week. I have all the systems/sw listed at the end already. The solution must work within that environment.

-------------------------
NOTE: Because this is so simple, I will chose the developer based on their written approach to the problem IN THEIR BID. Please give me a few sentences IN YOUR BID describing your approach to marshaling these objects. Thank you! :)
-------------------------

Deliverables:
1. A VS2008 solution that has a project for a windows client and another for the IIS server web service.
2. The win client is nothing but a simple test client that sends a test class (can be anything) to the web service, and receives a zip file in return.
3. The web service is just a test service to receive the test class and send a file to the client.
4. Yes, it is that simple.

Process:
1. The client has a button that the user will click.
2. The client then converts an instance of a simple test class into XML in memory.
3. The client then invokes the test web service (WCF), giving this test class (as an XML "file") as a parameter.
4. The service receives the XML and converts it back to an instance of the test object.
5. The service then loads a file on the local file system (any file-doesn't matter) into memory.
6. The service then takes an instance of another test class and converts it to XML in memory.
7. The service then zips the 2 "files" together in memory to form a single file in memory.
8. The service then sends this file as it's response to the call to the web service.
9. The client takes this file/stream from the web service.
10. The client then unzips this single "file" into it's 2 components (XML and file).
11. The client writes the file to the local disk, giving it an arbitrary name (test.file).
12. Finally, the client converts the XML received into an instance of the class it started out as on the server.

Components:
(Server)
WCF
IIS7
WinSvr2008
(Client)
VS2008
VB.NET

Notes:
-All class types can be made up, and have just one attribute, if you like.
-The web service can be called anything you like.
-This is just a reference project to demonstrate how to do it. I will use this reference job to make more practical applications.
-I don't care if the solution is a straight service, or a WCF service library (DLL) is utilized. Your call.