Bulk SMS Messages: C# class library & Desktop App

I need 2 projects. In c# described below. 1. A SERVERSIDE software (In the form of a class library) 2. A desktop application to manage offline users MUST BE MODULAR. Must be able to accept updates/upgrades. Communication bw client/server must be encrypted and must have logs. Both software must have source codes and? codes hidden from the user once compiled **SERVERSIDE SOFTWARE** Should only be called by a certainID which is a code on our webpages. The web page then calls the class exe or dll. And passes the numbers to the class. FUNCTIONS a) receives text messages from calling applications, b) processes them and c) send them out in batches d) Makes a log of the success and failed messages to notepad or MS SQL ADDITIONAL FUNCTIONS 1. It should be able to handle large number formats and break them into small batches of 5,000 and send them out. Either in a loop or at once. 2. Should be able to break a large number of csv files into batches, append a value to each one and send out dynamically e.g. hello john, hello sarah etc this message originall was hello <#name#> .... and numbers where 079xxxxx/john,079xxxxxx/sarah etc 3. should be able to receive a report from the remote gateway-- **DESKTOP SOFTWARE **Users have to login to view thier accounts. Then choose to work offline. If any modifications are made offline, they have to re enter thier password FUNCTIONS A desktop app, which Basically interacts with users to simplify sending text messages to a remote server 1. Should be able to break? & work with batches 2. Schedule messages based on time/date) 3. Give a user the option to choose where to import from (excell, notepad, ms word,access and email client e.g. outlook, yahoo or hotmail etc) 4. import form outlook or any email client 5. Option to work offline/ online 6. Option when to connect and send to the remote server 7. Download delivery reports from the server & option to export to csv format 8. Each user installation should have a unique ID, and be able to give a report back to the server, who installed and what time/user did so.