Closed AmadeusW closed 1 month ago
First off, thank you for your work on Visual Studio!
I set the assembly file version to 1.4.5
in the latest release. Going forward, I will continue to keep the assembly and extension versions consistent. If the issue arises again, please let me know so I can come out with a fix.
Recently you've fixed a COMException caused by UI thread dependency of a COMObject in the MEF part constructor: 291bee47
I work on Visual Studio and I've worked around this crash by excluding this extension from preloading on BG thread. (Preloading reduces UI delays on startup). We'd like to restore capability to preload this extension on BG thread. To detect that developer is using fixed version, we're using the
System.Diagnostics.FileVersionInfo.GetVersionInfo(pathToTailwindCSSIntellisenseDll)
However, this version is unset regardless of release (shows as
1.0.0.0
):Would it be OK to set the file version to match the extension version (e.g.
1.4.4
) so that we can remove this extension from the exclusion list?