Should CLI only run in 64 bit mode?

[felix-b]

Symptom: when debugging in Visual Studio on 64 bit Windows, the process runs in 32 bit mode.

Cause: NWheels.Cli project defines Platform=Any CPU. Since Visual Studio is a 32 bit process, Any CPU defaults to 32 bit mode.

Fix: if we want to always run in 64 bit, we need to set Platform=x64 for NWheels.Cli.

[felix-b]

The question is, can we say that we only run 64 bit microservices?

There may be a use case when a microservice has to load a 32-bit 3rd party component. If we do what I suggested (Platform=x64), we block this use case.

[felix-b]

The following is an offline discussion between me and @ILyaIL83:

@ILyaIL83: I'm not sure. On one side, who needs 32 bit processes today.
@me: (I mention two projects where we had to load 32 bit components in-process)
@ILyaIL83: On the other side, we can continue developing on 32 bit, and it will run on 64 bit, then we can leave everything as is.
@me: I think we have to be able to run in both 32 and 64. But there needs to be a way to choose.
@ILyaIL83: Yes, I thought about it, too
@me: the question is, how we can make F5 run in 64 bit by default
@ILyaIL83: I'm also thinking about creating integration test for both 32 and 64 bit, but maybe it's an overkill
@me: I think we should have such tests
@ILyaIL83: Well, by now I have more questions than answers. Which means we should put it on hold, until the problem matures.
@me: I agree.