As SY01 problems go

[suityou01]

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?

[Spacecadet]

Thoughts?

tulip happens, you're paid to deal with

[DimPrawn]

Does disaster stalk you?

Were you born on a Wednesday?

Did your mum upset a Gypsy when she was carrying you?

Oh and

[suityou01]

tulip happens, you're paid to deal with

So I should ask the vendor for access to their code repository and fix it myself?

[suityou01]

Does disaster stalk you?

Were you born on a Wednesday?

Did your mum upset a Gypsy when she was carrying you?

Oh and

Yes.

Yes.

Yes.

[aussielong]

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?

Logging.

[minestrone]

The meltdown is starting.

[SimonMac]

Have you tried turning it off and on again?

[suityou01]

Logging.

Not with this tool I'm afraid. Dumping out to text file is about the best I can achieve. Bluddy annoying.

[suityou01]

Have you tried turning it off and on again?

That would involve kicking out the other devs. Not my call.