I have a WCF Service that exposes a method GetCustomers(). The internals of the method uses a Data Layer along with a Business Layer to return a List of Customers. Currently I am using an SQL Server Database file saved on the server. Everything works fine on my local network but I want to move this to the web.
I thought the best method would be to create an IIS WCF Service which makes calls to the current WCF Service's GetCustomers(). I haven't had much experience with the SQL Server Database Files but I figured I would need to move the .mdf file to the IIS WCF Service App_Data folder but I'm not sure how to change the database connectionstring and get all this to work properly. The only thing I can figure is that I will have to re-implement the GetCustomers() method in the IIS WCF Service and point it to the correct database. It seems like I shouldn't have to do this though.
I know that if I where hosting the DB in a full SQL Server implementation that this wouldn't be a problem because the connectionstring wouldn't change. That is not an option at this point.
I think I am making this more difficult than it should be.