Success!!!
Damn that was annoying... anyway, some helpful stuff here. The guy from the tutorials went over manually binding the RIA Service to the Silverlight elements. By no means does this mean I could fix my old application, since I don't know if I could ever get a hold of the correct context (in fact I believe I tried something similar in the old code that didn't end up working). Doesn't matter, I deleted the old demo application long ago.
So I followed the tutorial almost exactly, and everything blew up. First was a stupid error on my behalf trying to interact with an object that wasn't instantiated, but then things continued to blow up. Silverlight hid the stacktrace from me, and then by fluke one time I run the application and miraculously I get a slightly different error (guessing that with async calls, this time I just got lucky that the useful one was returned). Find out that when I built my Entity Framework Models, even though it was using an existing database, I somehow ended up with entities mapped to non-existant tables? I'm baffled, but it is in the past now.
Anyway, once I conquered that demon, I finished the remainder of the application in no time. I can now interact with my database rather on the fly. Only one table at the moment, but with this demo in place now, I can start moving forward.
Now just hoping I don't hit another one of those instance where the road diverges on me. I know I am communicating with my database using slightly different technologies than in the office, but from what I've learned in the past couple of days, short of using the same framework tools as we're using in the office I'm going to have a different experience. At least some of the concepts and design methodologies are helping, and I'm starting to like the tools despite the terrible error reporting.
So I followed the tutorial almost exactly, and everything blew up. First was a stupid error on my behalf trying to interact with an object that wasn't instantiated, but then things continued to blow up. Silverlight hid the stacktrace from me, and then by fluke one time I run the application and miraculously I get a slightly different error (guessing that with async calls, this time I just got lucky that the useful one was returned). Find out that when I built my Entity Framework Models, even though it was using an existing database, I somehow ended up with entities mapped to non-existant tables? I'm baffled, but it is in the past now.
Anyway, once I conquered that demon, I finished the remainder of the application in no time. I can now interact with my database rather on the fly. Only one table at the moment, but with this demo in place now, I can start moving forward.
Now just hoping I don't hit another one of those instance where the road diverges on me. I know I am communicating with my database using slightly different technologies than in the office, but from what I've learned in the past couple of days, short of using the same framework tools as we're using in the office I'm going to have a different experience. At least some of the concepts and design methodologies are helping, and I'm starting to like the tools despite the terrible error reporting.
Comments
Post a Comment