As SY01 problems go

[suityou01]

You really are a cut today aren't you

[mudskipper]

Lambda's can produce some very ugly code, but used judiciously, they're great.

I love lambdas.

[Spacecadet]

I love lambdas.

In a Lambda Korma?

[suityou01]

I love lambdas.

[OwlHoot]

So what happens is that, when it stops working it tries to launch the 64bit csc.exe in a 32bit shell. And boom. But silent boom.

Can't you try running it in a 64 bit VM?

[DimPrawn]

Can't you try running it in a 64 bit VM?

This video explains the techniques involved

https://www.youtube.com/watch?v=SG3kbcTJ0yo

[eek]

No. It stops generating them.

Specifically what I have tracked down by decompiling the vendors product is that it uses CodeDomProvider to launch a remote debugging session. It could specify the target but it doesn't. Appalling code.

So what happens is that, when it stops working it tries to launch the 64bit csc.exe in a 32bit shell. And boom. But silent boom.

Took quite a bit of digging to find that little nugget.

What do the project build settings say? Can you set

"Configurations to build" to X86
"MSbuild Platform" to X86

(basically for any dropdown with auto and X86 as options set it to X86).

and see how that helps. These may not be the correct bits depending on the version of VS you are running but if it used to work and has now stopped then chances are someones messed up the project configuration and thats the cause of the problem.

[suityou01]

Can't you try running it in a 64 bit VM?

It is a 64 bit VM.

It doesn't make the app 64 bit. The 32 bit app runs under a thunking layer called wow6432 or somesuch.

[suityou01]

What do the project build settings say? Can you set

"Configurations to build" to X86
"MSbuild Platform" to X86

(basically for any dropdown with auto and X86 as options set it to X86).

and see how that helps. These may not be the correct bits depending on the version of VS you are running but if it used to work and has now stopped then chances are someones messed up the project configuration and thats the cause of the problem.

Spot on, if i could.

Picture a BPM Designer, written in .net with a Debug button on the ribbon bar. This should automagically launch VS2010, inject from temp files, build the pdb, and attach the debugger to the BPM engine.

I have no control over how it does this, all I can do is reverse engineer their code and weep.

This method is being called

CodeDomProvider.CompileAssemblyFromDom Method (System.CodeDom.Compiler)

The first agument takes one of these

CompilerParameters Class (System.CodeDom.Compiler)

So it should be possible to specify the target platform using the compilerparameters, but they don't appear to be doing that.

So it windows "defaults" to Framework rather than Framework64 then it works, otherwise it breaks.

[DimPrawn]

It is a 64 bit VM.

It doesn't make the app 64 bit. The 32 bit app runs under a thunking layer called wow6432 or somesuch.

Who would have thunk it?

JWoww - Wikipedia, the free encyclopedia