# Dotnet setter code coverage in serialization scenarios

**URL:** <https://community.sonarsource.com/t/dotnet-setter-code-coverage-in-serialization-scenarios/22855>\
**Category:** SonarQube Cloud\
**Tags:** csharp, dotnet, sonarqube-cloud, coverage\
**Created:** [April 8, 2020, 2:35pm UTC](https://community.sonarsource.com/t/dotnet-setter-code-coverage-in-serialization-scenarios/22855 "2020-04-08T14:35:05Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Andrei\_Epure](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andrei_epure/32/77402_2.png) [@Andrei\_Epure](https://community.sonarsource.com/u/Andrei_Epure)\
**Post date:** [April 9, 2020, 2:04pm UTC](https://community.sonarsource.com/t/dotnet-setter-code-coverage-in-serialization-scenarios/22855/2 "2020-04-09T14:04:35Z")

</div>

hi @larryautravail

I moved your message on a separate topic to be able to discuss here

regarding

> [@C#/VB.NET: SonarQube and SonarCloud support Branch/Condition Coverage data](https://community.sonarsource.com/t/c-vb-net-sonarqube-and-sonarcloud-support-branch-condition-coverage-data/22384/2):
>
> Is there a way to disable this feature? Our coverage just dropped into oblivion and there is no real way for us to go back on our old code o bump up the condition coverage.

can you please share with us more details? how much did your code coverage drop? is it just because POCO serializable objects with uncovered setters or is there something else?

---

_[View the full topic](https://community.sonarsource.com/t/dotnet-setter-code-coverage-in-serialization-scenarios/22855)._