"Cannot find the Metalama.Compiler.Interface assembly" - Error loading extension in VS

[bradlee-s]

I've updated my references from Nuget. Also uninstalled the extension and reinstalled from marketplace (0.5.27). When VS starts up, it displays a warning at the top:"Metalama ran into an unexpected problem: Cannot find the Metalama.Compiler.Interface assembly."
Details:
Metalama.Framework.Engine.AssertionFailedException: Cannot find the Metalama.Compiler.Interface assembly.
at Obfuscated.^5Nx5YQeXj2J2..ctor(IServiceProvider serviceProvider)
at Metalama.Framework.Engine.Pipeline.ServiceProviderFactory.<>c.^0Nzc6IUSPbPz(IServiceProvider _0)
at Metalama.Framework.Engine.Pipeline.ServiceProvider.^NKXN6diP.^Ib9O1__tTiGv(IServiceProvider _0)
at Metalama.Framework.Engine.Pipeline.ServiceProvider.^j47JJ8dp.^OD2cX6Vs(IServiceProvider _0)
at Metalama.Framework.Engine.Pipeline.ServiceProvider.^HFf83eaPqWlN(Type _0)
at Metalama.Framework.Project.ServiceProviderExtensions.GetRequiredService[T](IServiceProvider serviceProvider)
at Obfuscated.^Qf3QRcMSatsB..ctor(IServiceProvider serviceProvider)
at Metalama.Framework.Engine.Pipeline.ServiceProvider.^LUKZAb4R(IEnumerable`1 _0, Compilation _1)
at Metalama.Framework.DesignTime.VisualStudio.Classification.DesignTimeClassificationService..ctor()
at Metalama.Framework.DesignTime.VisualStudio.CompilerServiceProvider.GetServiceT
at Metalama.Vsx.TextBuffers.TextBufferServicesImpl.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Metalama.Vsx.TextBuffers.TextBufferServicesImpl.d__17.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Metalama.Vsx.TextBuffers.TextBufferServicesImpl.<GetQuickInfoItemAsync_Source>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Metalama.Vsx.TextBuffers.TextBufferServicesImpl.d__25.MoveNext()

When attempting to run Show Metalama Diff, I receive this error:
"Cannot preview the transformed code: This is not a Metalama project."

Project worked fine with previous versions. Updated to attempt to resolve a separate issue.

[gfraiteur]

Do you still have the problem after restarting Visual Studio?

[bradlee-s]

Yes. Restarted, rebooted, uninstalled and reinstalled.

[gfraiteur]

I cannot reproduce it but I am trying a fix. I'll let you know.

[gfraiteur]

Please update to 0.5.27 and let me know if it solves anything.

[bradlee-s]

I've been using 0.5.27. Is this an updated version of the same build?

[gfraiteur]

You've been using the VSX 0.5.27 and NuGet 0.5.26, now we have NuGet 0.5.27.

[bradlee-s]

I have updated to 0.5.27 and am still seeing the same errors in 1 project but not another.

The working project is a .net 6 class library. The non-working project is a .net 4.7.1 web application. The web app previously worked with 0.5.25.

[gfraiteur]

Could you please create a log as described here, with:

• logging/categories/*=true
• logging/processes/DevEnv=true

Then restart VS, reproduce the issue, and attach the log found in %TEMP%\Metalama\Logs.

Don't forget to turn off logging after you're finished.

Thank you.

[gfraiteur]

I was able to reproduce the error.

Please update your nuget packages to version 0.5.29-preview.

[bradlee-s]

I've updated to 0.5.29 (extension is still at 0.5.27). The "Cannot find the Metalama.Compiler.Interface assembly" error is now gone. But a ShowDiff on my tagged class still tells me "Cannot preview the transformed code: This is not a Metalama project".

[gfraiteur]

Does it still do that after restarting VS?

[bradlee-s]

Yes. I've restarted, uninstalled/reinstalled/restarted. Cleaned/Rebuild, etc....

…

On Thu, Jul 21, 2022 at 11:06 AM Gael Fraiteur ***@***.***> wrote: Does it still do that after restarting VS? — Reply to this email directly, view it on GitHub <#26 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AGGPG5DF3XUIRLLURCEWSKLVVFRQRANCNFSM5346NEIQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[gfraiteur]

Okay so this is a different issue.
Please open a new conversation so we can track it separately.
We will probably need an msbuild binlog, produced by dotnet build /bl. The file is named msbuild.binlog by default.
If you don't want to share the file publicly on GitHub, please create a private ticket on https://support.postsharp.net/.

[gfraiteur]

This issue should be solved in the latest build.