WF4 service workflow designer holding reference to its own assembly, preventing project build in x64?

I don't really have an answer but you might try to compare the working one against the non-working using something like Beyond Compare or WinDiff . I've used them in similar situations when just eye-balling differences didn't make the differences apparent.

I eventually found the answer to this question. Basically the WF designer will not work if the solution is setup to compile as 64x. The reason is visual studio itself is a 32bit app and so is unable to load the required assemblies and find any of the types.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.