STDOUT is not displaying on cf console nor in loggregator

[ishwarps]

Hi,
I have developed the sample .net Application(visual studio 2015). I have use following code.
console.writeln("message");

The above command printing on STDOUT. But its not displaying on cf console nor in loggregator.

Like same if i will use the System.out.println() in java application with different buildpack then its printing on cf console.

Does this bug in binary buildpack?

I am using following cf and buildpack version.
Cloud Foundry version: cf -v247
binary_buildpack=v1.0.5

Thanks in advanced.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/136602589

The labels on this github issue will be updated when the story is started.

[sesmith177]

@ishwar1987 if your app writes to STDOUT it should be picked up by the cf logs.

It is unlikely that there is a bug in the binary buildpack, as the buildpack does not modify the application directory.

Can you show us the staging / application logs that you do have?

Thanks.

[sesmith177]

@ishwar1987 it looks like this is a duplicate of cloudfoundry/dotnet-core-buildpack#129, so we will close this one and continue the investigation in 129.

[MaheshRudrachar]

This issue seems different from what is marked as duplicate!!!

@sesmith177 does this bug (buildpack does not modify the application directory) resolved in latest version of binary_buildpack?

[sclevine]

Neither this issue nor cloudfoundry/dotnet-core-buildpack#129 are bugs. Neither buildpack supported Windows cells when these issues were open.

The latest release of the binary buildpack now does support Windows cells.