Please find attached, a sketch of the Input Window (dont worry about the Design for now, this can be adjusted later). The user thereby manually enters the location of an image file on a remote server. This location will be saved in a database and the input box reads the location from the database in subsequent uses, so the client doesn't need to enter the location of the file over again. If the location changes, he will simply change the folder and the database entry will change. The risk that I see with this approach, however, is that it might have a few user case scenarios. An alternative method will be described further below.
The text box with the caption "Crawl Text" is then used to enter any text and the "*" symbol is intended to be replaced by following code : <BITMAP>Filelocation</BITMAP>. So the content of the "Crawl Text" box is supposed to be written into a text (.txt) file while replacing the "*" symbol with the above mentioned code. For example the text: Test * Hello World would have an output format of Test <BITMAP>C:\....\logo.png</BITMAP> Hello World.
Since the output file is located on a remote location, i.e. the input window is on the web server and the output file should be saved to a predefined location on a different (remote) server, the following approach is suggested: Instead of writing the content directly to a text file, the content of the "Crawl Text" box is written into the database first.
A windows service needs to be implemented which will be installed on the remote server. This windows server will be connected to the database on the web. You could use .NET remoting to communicate between the Windows service and the web site.
When the user clicks the "Update" button, the database entry is overwritten and a signal sent to the windows service. When the windows service receives that signal, it will read the database, copy the new entry and save it to the text file (i.e. overwrites the file).
It does not matter, whether the "*" symbol is replaced directly before it is written into the database, or if it is replaced by the windows service before overwriting the file. Which ever is most convenient to you. This is the whole extent of this application that I need developed.
An alternative approach to the "File location" input box is to save a fixed file into the same folder as the windows service. For example a specific file (which will not be changed) will be copied into the same folder as the windows service. This file will be named logo.png. The "File location" box will thus be not needed any longer. The File location will always be same file path as windows service/logo.png. This case would, I believe, only allow one user case scenario, as the user is limited to only editing his text and delimiting this by "*", thus decreasing he error potential.
The solution needs to be implemented in .Net 4.0 MVC2 (MVC3 is supported with some adjustments) and MSSQL 2008. Our Webserver runs on IIS 7 integrated.