Silverlight 4 and RIA services still a dead end.
I've moved on from the DevTracker project, but while I'm not doing any more development on it, I'm still trying to get the damn thing to work properly in IIS. Reason is because if I want to redo Veronica's application in Silverlight 4, I will eventually need to do the same thing. I've gotten further, though through another stream of events thoroughly unlike Microsoft. Even the Microsoft Dev's who noted having issues with this and finding much of the deployment process counter intuitive recommended using an application called Fiddler to intercept the packets to get the stacktrace of the errors being thrown. In other words, MS has no official solution to this problem and their unofficial solution is to use a 3rd party application. I think .Net based development is sliding quickly down the tubes... they have no solution or exceptions thrown for issues with data binding, and now they have no debugging for web services combined with a faulty deployment system. Perhaps all of my years in university spent on Java weren't so wasted after all.
Since the database is in nHibernate and I did the mapping files for this project I should be able to drop them into regular old Hibernate. Which means I'm slowly feeling the temptation to create a rival project in Java and see which one in the long run was more difficult to get up and running. If things ever go south in my current job, Java web apps seem to make a very large portion of the programming market, so this would be no wasted effort. And it would be educational!
Anyway... long story short. Now I'm catching the exceptions and they aren't any more informative than the one general exception I was receiving before. Basically, the web application is supposed to create a service, however the default configuration creates a virtual one so there is no physical file, and I'm getting an exception that it cannot find the service. This is a VERY common issue people are writing about, however, most of the complaints are on beta versions or slightly different configurations, and they all state that if they browse to the correct path where the virtual service should be it loads and they simply need to point the web.config to the correct path. In my unhappy state of affairs, I can't even locate the service where it should be... so either the application isn't trying to create the service or it is failing to do so.
Well the upside, I have some clue about what aspect isn't working. The downside is that no one seems to have any insight. Worse than that... it isn't as though it is only the service I created which is blowing up, it is also the one that came inside the Business Application template that drives the user logins, etc... which isn't working.
Maybe it is time to work on something else in the hopes that Microsoft eventually comes up with something. I'm in no hurry here at the moment.
Since the database is in nHibernate and I did the mapping files for this project I should be able to drop them into regular old Hibernate. Which means I'm slowly feeling the temptation to create a rival project in Java and see which one in the long run was more difficult to get up and running. If things ever go south in my current job, Java web apps seem to make a very large portion of the programming market, so this would be no wasted effort. And it would be educational!
Anyway... long story short. Now I'm catching the exceptions and they aren't any more informative than the one general exception I was receiving before. Basically, the web application is supposed to create a service, however the default configuration creates a virtual one so there is no physical file, and I'm getting an exception that it cannot find the service. This is a VERY common issue people are writing about, however, most of the complaints are on beta versions or slightly different configurations, and they all state that if they browse to the correct path where the virtual service should be it loads and they simply need to point the web.config to the correct path. In my unhappy state of affairs, I can't even locate the service where it should be... so either the application isn't trying to create the service or it is failing to do so.
Well the upside, I have some clue about what aspect isn't working. The downside is that no one seems to have any insight. Worse than that... it isn't as though it is only the service I created which is blowing up, it is also the one that came inside the Business Application template that drives the user logins, etc... which isn't working.
Maybe it is time to work on something else in the hopes that Microsoft eventually comes up with something. I'm in no hurry here at the moment.
Comments
Post a Comment