On Oct 14, 12:03 pm, Andrew Badera <[email protected]> wrote: [...] > Use WCF. Remoting is going away.
Andrew, I'm still struggling with getting this to work, but I read in more than one place that even setting up a simple scenario in WCF was very complicated. All I want to do is make changes to a DGV and have them reflected in a corresponding database on another machine via a web service. I have seen many, many examples that _almost_ talk about it, but none that nail it. For example, I found one that was terrific with inserting or reading the data, but as soon as you tried to update or delete, it crashed. Even though I told the wizard to derive the right UPDATE and DELETE commands from the SELECT statement, it failed to generate them. On the other hand, I've tried to generate the stored procedures on the SQL 2005 server to do this, and while I used the wizard to do all 4 in CRUD, again it only generated 2 SPs, one for SELECT (which returned an integer) and one for INSERT. I even tried all the soapclient* methods, XMLReaders, etc. trying to find something that works. I even tried to get the SQL direct web services to work, hand-rolling web services directly from MSSQL 2005, which proved to be far more complex and didn't look like it would work well with IIS 7, as I'd lose control of managing/monitoring the output. Heck, I can't even figure out how to turn on logging in IIS 7 so it will show me each hit (and I downloaded all the optional tools). So frustration is the word of the day, unfortunately. I just want to have one template/test solution that allows me to do the INSERT, UPDATE, SELECT and DELETE, and I can clone it to all my needs. At this point I am working hard and getting nowhere, so even WCF might still be on the table, if only there were a way to do the above with it. WCF couldn't require more effort than I've already expended, could it? Exhausted... pat :)
