Closed florindragos closed 9 years ago
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/188/ Test FAILed.
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/189/ Test PASSed.
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/190/ Test PASSed.
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/192/ Test passed.
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/193/ Test passed.
Please enable stylecop and code analysis. Also, I believe this is the only assembly that only has a NET45 lib. What happens if I add the nuget package to a non-NET45 project?
Please add an example on how to use this new feature in the readme
The manifest library will not be referenced if the nuget package is added to a non-net45 project. It is added only for net45 target in nuspec.
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/195/ Test PASSed.
Enabled stylecop and fixed all related errors
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/197/ Test PASSed.
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/198/ Test PASSed.
Refer to this link for build results (access rights to CI server needed): https://jenkins.paas.hpcloud.net/job/als-cf-dotnet-sdk-babysitter/199/ Test PASSed.
:+1:
.net version of the cf manifest library