It it just me or is SL/WCF development really flaky
-
I am having serious problems with the inconsistency of the development environment and want to know if it is just me. Some of the symptoms during development are; An async call will work perfectly and then return server not found. A method that worked 5 minutes ago fails with a spurious message then works when I restart the app again. This is a waste of endless hours as I cannot trust the IDE to be consistent. An Async/completed pair will work if I follow through the structure of the app, then the completed method does not get hit when I shortcut the path. This one is really weird! The WCF service will not update the reference, occasionally I have to delete the service from the SL app just to get a new method to reflect into the reference Debugging is just insane - I either need a third party app or a winforms client to debug an asynch service. Combo boxes are a complete PITA, I am astonished we have reached release 4 and these are such a disaster. The combination of the above means that productivity is about 10% of what I can do with winforms, even with a WCF service. I have the feeling I may have made a complete blunder recommending Silverlight.
Never underestimate the power of human stupidity RAH
-
I am having serious problems with the inconsistency of the development environment and want to know if it is just me. Some of the symptoms during development are; An async call will work perfectly and then return server not found. A method that worked 5 minutes ago fails with a spurious message then works when I restart the app again. This is a waste of endless hours as I cannot trust the IDE to be consistent. An Async/completed pair will work if I follow through the structure of the app, then the completed method does not get hit when I shortcut the path. This one is really weird! The WCF service will not update the reference, occasionally I have to delete the service from the SL app just to get a new method to reflect into the reference Debugging is just insane - I either need a third party app or a winforms client to debug an asynch service. Combo boxes are a complete PITA, I am astonished we have reached release 4 and these are such a disaster. The combination of the above means that productivity is about 10% of what I can do with winforms, even with a WCF service. I have the feeling I may have made a complete blunder recommending Silverlight.
Never underestimate the power of human stupidity RAH
Yes, it's just you... ;P No, seriously, I have exactly the opposite problem - working with winforms is a torture for me, while SL and WPF seems to go smoothly. I guess it's just the matter of personal preference - everybody has to find at least 1 technology to hate.
-
I am having serious problems with the inconsistency of the development environment and want to know if it is just me. Some of the symptoms during development are; An async call will work perfectly and then return server not found. A method that worked 5 minutes ago fails with a spurious message then works when I restart the app again. This is a waste of endless hours as I cannot trust the IDE to be consistent. An Async/completed pair will work if I follow through the structure of the app, then the completed method does not get hit when I shortcut the path. This one is really weird! The WCF service will not update the reference, occasionally I have to delete the service from the SL app just to get a new method to reflect into the reference Debugging is just insane - I either need a third party app or a winforms client to debug an asynch service. Combo boxes are a complete PITA, I am astonished we have reached release 4 and these are such a disaster. The combination of the above means that productivity is about 10% of what I can do with winforms, even with a WCF service. I have the feeling I may have made a complete blunder recommending Silverlight.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
Debugging is just insane - I either need a third party app or a winforms client to debug an asynch service.
*Cough*Use Attach to running process to debug - it's a lot easier.
I have CDO, it's OCD with the letters in the right order; just as they ruddy well should be
Forgive your enemies - it messes with their heads
-
I am having serious problems with the inconsistency of the development environment and want to know if it is just me. Some of the symptoms during development are; An async call will work perfectly and then return server not found. A method that worked 5 minutes ago fails with a spurious message then works when I restart the app again. This is a waste of endless hours as I cannot trust the IDE to be consistent. An Async/completed pair will work if I follow through the structure of the app, then the completed method does not get hit when I shortcut the path. This one is really weird! The WCF service will not update the reference, occasionally I have to delete the service from the SL app just to get a new method to reflect into the reference Debugging is just insane - I either need a third party app or a winforms client to debug an asynch service. Combo boxes are a complete PITA, I am astonished we have reached release 4 and these are such a disaster. The combination of the above means that productivity is about 10% of what I can do with winforms, even with a WCF service. I have the feeling I may have made a complete blunder recommending Silverlight.
Never underestimate the power of human stupidity RAH
Well....things are not this bad. It's just you. :)
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it. My latest tip/trick Visit the Hindi forum here.
modified on Monday, October 11, 2010 11:52 PM
-
Well....things are not this bad. It's just you. :)
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it. My latest tip/trick Visit the Hindi forum here.
modified on Monday, October 11, 2010 11:52 PM
Abhinav S wrote:
Well....things are not this bad.
Oh yes they are, and then we have some stellar decisions from IT, they have decided that remote sites will have to access the systems via citrix.
Never underestimate the power of human stupidity RAH
-
Abhinav S wrote:
Well....things are not this bad.
Oh yes they are, and then we have some stellar decisions from IT, they have decided that remote sites will have to access the systems via citrix.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
they have decided that remote sites will have to access the systems via citrix.
Intersting. We too had a similar issue with a client. The client had to run SL apps on citrix. Still not found a workaround. :|
The funniest thing about this particular signature is that by the time you realise it doesn't say anything it's too late to stop reading it. My latest tip/trick Visit the Hindi forum here.
-
I am having serious problems with the inconsistency of the development environment and want to know if it is just me. Some of the symptoms during development are; An async call will work perfectly and then return server not found. A method that worked 5 minutes ago fails with a spurious message then works when I restart the app again. This is a waste of endless hours as I cannot trust the IDE to be consistent. An Async/completed pair will work if I follow through the structure of the app, then the completed method does not get hit when I shortcut the path. This one is really weird! The WCF service will not update the reference, occasionally I have to delete the service from the SL app just to get a new method to reflect into the reference Debugging is just insane - I either need a third party app or a winforms client to debug an asynch service. Combo boxes are a complete PITA, I am astonished we have reached release 4 and these are such a disaster. The combination of the above means that productivity is about 10% of what I can do with winforms, even with a WCF service. I have the feeling I may have made a complete blunder recommending Silverlight.
Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
The WCF service will not update the reference, occasionally I have to delete the service from the SL app just to get a new method to reflect into the reference
Yeah, that happens to me a lot as well - more so in WPF, but occasionally in Silverlight as well.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001 -
Mycroft Holmes wrote:
The WCF service will not update the reference, occasionally I have to delete the service from the SL app just to get a new method to reflect into the reference
Yeah, that happens to me a lot as well - more so in WPF, but occasionally in Silverlight as well.
.45 ACP - because shooting twice is just silly
-----
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001I yet to create a WPF app, working with SL is slowly getting better as I start to find the gotchas. Figured out another one today, where the completed event is not being hit, it is just AFTER the other events have been completed. I was impressed by the SL out of the browser, right click on the app in the browser and install, it copies the xbap to the local drive and it look good without the browser visual overhead.
Never underestimate the power of human stupidity RAH
