Hello Claudio,
Could you please check if the same problem appears for you with the simple newly created winforms app? If not - is it possible to have your testcase for internal testing?
I checked it here with latest VS2022 and Oxygene winforms projects, newly created and the one with non-empty resources. Both shows Resources as expected.
Thank in advance.
some cases.
But not yet tests on the latest versions of elements. I’ll get back to you later on this case.
at the moment would like to try to solve the case of the resorces.
I’ve just checked - the reason for this issue is the same as for Find in solution problem. The moved API was causing the problem. Also should be fixed with the next build.
Hmm, Suppress Warnings doesn’t work for you? Specific to W72 or any warnings? A small test-case would be appreciated — this would definitely be a separate issue i’d need to log and that would not be part of the fix today.
in a new, simple application with no real functionality it works. in my application, which is quite large, it doesn’t work. I will try to isolate the case.
It is difficult to isolate the case. but one thing I noticed is that I tell it to suppress it and save it in the project file normally, but when reopening it changes the tag to < SuppressedWarnings>W72< /SuppressedWarnings > and this information does not appear on the screen, only in the project file.
This part is fixed (maybe or maybe not for the next build you get, depending on whether the one already underway is good). “SuppressedWarnings” is good/proper, and should get passed to the compiler, unless you’re using legacy. But it shouldn’t be getting migrated if you are…