VS 2022 V17.6 Issue with Show Metalama diff
Installed the latest version of Vs 2022 today. On the very first opening Show Metalama Diff worked but it has steadfastly refused to do so since. No error message, no warning just an endlessly cycling Dialog telling me to please wait while Metalama is transforming the file.
12 Replies
It might be a red herring but I'm wondering if this might have something to do with MetalamaCompileTime Dependency Injection?
Unknown User•2y ago
Message Not Public
Sign In & Join Server To View
We'll look at this.
I've been working between my Desktop (VS 17.6) and surface pro (vs 17.5) for the past two days and VS 17.6 is definitely a non starter with Metalama at present.
Projects do compile so in that respect you can live without the Show diffs capability, but what I really find myself missing is the ability to declare classes as partial and then reference the introduced code therein.
Projects do compile so in that respect you can live without the Show diffs capability, but what I really find myself missing is the ability to declare classes as partial and then reference the introduced code therein.
Solved in 2023.0.116 but not yet in 2023.1
Does that mean one wants the 2023.0.116 Visual Studio Extension or does that work with the 2023.1.1 VS extension?
The issue is in the packages. The VSX should not be updated.
Thanks
Have updated Metalama to the latest preview nugets and (possibly this was an error) I also updated VS to 17.2).
Same problem dialog is stuck asking me to wait while metalama shows the diffs.
Project is available on Github https://github.com/domsinclair/VtlSoftware.LoggingWithStringHandler Error occurs in Calculator class in Logging Console App.
Project is available on Github https://github.com/domsinclair/VtlSoftware.LoggingWithStringHandler Error occurs in Calculator class in Logging Console App.
GitHub
GitHub - domsinclair/VtlSoftware.LoggingWithStringHandler
Contribute to domsinclair/VtlSoftware.LoggingWithStringHandler development by creating an account on GitHub.
Bit more info for you.
I closed everything and rebooted my machine. On returning to VS I'm now being informed of LAMA0041 error 'MissingMethodException'.
Sorry folks looks like there is still an issue somewhere.
Thanks for the report. We did an incorrect merge of the fix to our 2023.1 branch, so 2023.0 should be fine (but I get that you need a different fix from 2023.1 to make your code work). I am going to release 2023.1 again today, which should fix it.
Thanks
So far so good!