This is a pretty strange one.
In a nutshell I've been unable to work since last Wednesday when my environment stopped working. It's a BPM tool, that has Csharpy bits at the backend. The bit that's stopped working is being able to debug the code. It fires up VS2010 in a remote debugging session. The specific problem is that it's stopped loading the symbols so I can't put in breakpoints.
This was on my VM that I built before I got out here. Restored from snapshot, still not working. Weird.
ClientCo have been trying to get me on their environment for the past 5 weeks and this kind of expedited that a bit. So this morning I got access.
You beauty. So I have been working for 1hr 30 mins. Then their environment packs in as well.
My direct reports response was "Oh well it works for me ok". Real nice, thanks.
So I raise a ticket with the vendor. Their response?
"It's a known issue in version x.y, and we expect to roll out a new release at the end of July to address this issue. There are no known workarounds".
So I have to resort to chiselling out text files with the bits I want to debug.
I know only a bad workman blames his tools, but in this case, I feel I have a case to bring.
Thoughts?
In a nutshell I've been unable to work since last Wednesday when my environment stopped working. It's a BPM tool, that has Csharpy bits at the backend. The bit that's stopped working is being able to debug the code. It fires up VS2010 in a remote debugging session. The specific problem is that it's stopped loading the symbols so I can't put in breakpoints.
This was on my VM that I built before I got out here. Restored from snapshot, still not working. Weird.
ClientCo have been trying to get me on their environment for the past 5 weeks and this kind of expedited that a bit. So this morning I got access.
You beauty. So I have been working for 1hr 30 mins. Then their environment packs in as well.
My direct reports response was "Oh well it works for me ok". Real nice, thanks.
So I raise a ticket with the vendor. Their response?
"It's a known issue in version x.y, and we expect to roll out a new release at the end of July to address this issue. There are no known workarounds".
So I have to resort to chiselling out text files with the bits I want to debug.
I know only a bad workman blames his tools, but in this case, I feel I have a case to bring.
Thoughts?
Comment