Hello, I've developed 2 apps in C# (VS2010 .NET 4) that write files to disk: one of them writes an XML file while the other writes a TXT file. Starting from today, every time the TXT app is executed, it is blocked and deleted by SONAR because of "suspicious behavior detected" while the XML app runs just fine so, what happened with the TXT app? I wrote a test app that only writes a TXT file to disk and got the same result: blocked and deleted. However, if any of the TXT apps is executed inside VS2010, it has no problem at all with SONAR.
It will be the only solution for this kind of apps to include them in the list of excluded items for future scans or this is going to be fixed in some future SONAR fix? While I can live with that by now, it would be annoying that this problem begins to arise in every client of mine that has N360 installed.
thanks for your response... I've spent hours doing a lot of research in my code, cutting it off almost line by line until I found the source of problem: SqlConnection.Open()
Once there, I tested exactly the same code but targetting .NET 3.5 instead of .NET 4.0 and that was all: it runs as expected so I suppose there's something in .NET 4.0 that SONAR is misunderstanding.
Hope this issue will be fixed in the near future. Until then, I'll follow your advice as I'm not thinking about downgrading my apps to .NET 3.5
Hello, I've developed 2 apps in C# (VS2010 .NET 4) that write files to disk: one of them writes an XML file while the other writes a TXT file. Starting from today, every time the TXT app is executed, it is blocked and deleted by SONAR because of "suspicious behavior detected" while the XML app runs just fine so, what happened with the TXT app? I wrote a test app that only writes a TXT file to disk and got the same result: blocked and deleted. However, if any of the TXT apps is executed inside VS2010, it has no problem at all with SONAR.
It will be the only solution for this kind of apps to include them in the list of excluded items for future scans or this is going to be fixed in some future SONAR fix? While I can live with that by now, it would be annoying that this problem begins to arise in every client of mine that has N360 installed.