Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The information in the warning dialog is different from the .Net Framework when the EnableRaisingEvents property of FileSystemWatcher is changed to true #3649

Closed
Jessie-Zhang01 opened this issue Jul 27, 2020 · 1 comment
Labels
tracking-external-issue An issue is caused by an external system and won't be fixed in this repo

Comments

@Jessie-Zhang01
Copy link

  • .NET Core Version:
    .Net 5.0.100-rc.1.20376.1 from 5.0 master branch

  • Have you experienced this same bug with .NET Framework?:
    No

Minimal repro:

  1. Open the attached ‘WindowsFormsApp5.zip’ application in VS, then build and run it.
  2. Change the EnableRaisingEvents property to true.
  3. A warning dialog will pop-up, then click the "Details" button.
  4. Observe the information in the details.
  5. Click the "OK" button and observe whether the EnableRaisingEvents property is changed to true.

Expected behavior:
In step4, the information in the warning dialog should be the same as .Net Framework.
In step5, the EnableRaisingEvents property should be changed to true.

Actual behavior:
In step4, the information in the warning dialog is different from the .Net Framework.
image
In step5, the EnableRaisingEvents property has not been changed to true.
Issue1

Framework project: WindowsFormsApp6.zip

@RussKie
Copy link
Member

RussKie commented Jul 28, 2020

System.IO.FileSystemWatcher is part of the BCL, we don't own it. The error message is also supplied by the BCL.

@JeremyKuhne may provide additional information.

@RussKie RussKie closed this as completed Jul 28, 2020
@RussKie RussKie added the tracking-external-issue An issue is caused by an external system and won't be fixed in this repo label Jul 28, 2020
@ghost ghost locked as resolved and limited conversation to collaborators Jan 31, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
tracking-external-issue An issue is caused by an external system and won't be fixed in this repo
Projects
None yet
Development

No branches or pull requests

2 participants