Problem between C # system and Warsaw plugin (GAS Technology)

To solve the incompatibility problem, I had to contact GAS Technology describing the problem that was occurring.

They asked for a lot of information, they asked me to send my project, including the path where it was installed on windows and everything ... They also passed the link that @Randrade gave me and nothing to solve the problem. So after much insistence, they solved the problem. They did not explain what they did, but from what I understand, Warsaw is quite intrusive in OS, also acting in other applications and not just the browser, which is its purpose.

I also understand that they "release" applications by the path of the files where they are in the "Program Files" or another place where your application keeps the necessary files to boot.

That is, to resolve, you need to contact them by email, because they do not pass phone support, describing the problem and keeping in touch as they can end the problem, but do not notify the interested party.

/ p>

I hope I have helped!

I finally solved my problem with this plugin!

I spent a few months with this problem, without detecting that the cause was the plugin, with forms getting white, system slowing down and even totally paralyzing Windows, getting to the point of having to reboot the whole system.

Until one day I was able to see his loading in the Output screen, running the application in Debug mode. Then I opened the loaded Modules window in Visual Studio (Menu Debug-> Windows-> Modules), and confirmed the loading of that plugin. See Figure below:

Note that this was an unmanaged process load, I just disabled the project option that allowed debugging these (Project Properties - > Debug -> Enable Unmanaged Code Debugging).

I have several projects in C, C ++ and Fortran in my solution that require this option to debug, but now I will only activate it as long as I need it.

After disabling this option the plugin was no longer loaded and the entire application was faster!

I think it's worth mentioning too that while this plugin was being loaded, there were some slow loops in unmanaged code, including those we might use unknowingly, such as OpenFileDialog and SaveFileDialog, which internally load Win32 APIs.

I hope this is everybody's problem or that it helps someone find other plug-in points for this plugin!