Runs in VS2022 in debug, not sure if it works #7
Conversation
|
This extension tracks the loading of DLLs in to the current VS process, not the process under debug (mainly to assist in extension writing), so not flagging the assemblies shown in the output window isn't unusual. The changes look good to me, thanks for doing that. |
|
Given this PR represents all of my experience in VS extension coding, I'm planning to follow this guide to see if I can get something publishable: My aim is to find out what in my MVC project is loading "System.Data.OracleClient" amongst other surplus dlls, if I can archive that, I'll publish the PR and if its up to standard, perhaps this may help some one else too |
…kageReference items
|
The extension won't help to find what loads things in your project though, it helps to find what's loading things in the Visual Studio process itself. You could presumably use the same technique the extension uses within your code, but the extension itself doesn't help to that end. |
|
Ah, yes, that does make sense (based on what you said, the documentation and my observed behaviour!) I'll still try to finish what I've started and then use what I've learned to see if I can get what I'm after. |
| [Guid("71604717-b15d-4d1e-9fb4-03f5122e8858")] | ||
| public class AssemblyLoadDebuggerToolWindow : ToolWindowPane | ||
| { | ||
| public AssemblyLoadDebuggerToolWindow() : base(null) | ||
| { | ||
| this.Caption = Vsix.Name; | ||
| this.Caption = "Assembly Load Debugger"; |
There was a problem hiding this comment.
@mlorbetske I can see that you were generating the Vsix class based on the manifest file.
In order to target VS2022 you need a different manifest file per target so I couldn't use that in the shared code.
... I couldn't figure out how to generate the static class either, but the above point means that is moot
| <PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011" xmlns:d="http://schemas.microsoft.com/developer/vsx-schema-design/2011"> | ||
| <Metadata> | ||
| <Identity Id="34f00824-cb6a-4bc1-a27d-7375239cdd2f" Version="1.2" Language="en-US" Publisher="Mike Lorbetske" /> | ||
| <DisplayName>Assembly Load Debugger</DisplayName> |
There was a problem hiding this comment.
@mlorbetske this section is now missing the license as I couldn't get that playing nice with the shared code.
In the resources folder there is a link to the LICENSE file, but when I reference that in the manifest, I get a compile error
Can run in VS2022, opens new VS with plug in loaded
Debugging MVC5 app in modified VS wasn't detecting dll shown in output window
Some dlls were showing up, but I'm not sure where from