I've got a custom port supplier, so that allows me to connect to our engine over the network, which is more or less sufficient for our needs, but I'm curious, in the debug engine sample, which uses c++ as the example, but it only works for x86, none of the x64 processes listed the sample debug engine under the "Type" column of the attach to process dialog.
What do I need to specify to enable a debug engine that can use the default transport and attach to x64 processes? (my guess is a particular guid, but I couldn't find it searching high and low across the internet)
What do I need to specify to enable a debug engine that can use the default transport and attach to x64 processes? (my guess is a particular guid, but I couldn't find it searching high and low across the internet)
I'm in the middle of a task of unknown length and finding the answer will take a bit of time. I might forget to come back but it's not my intent to ignore.
VS Marketplace folk: Maybe you should reach out to the owners of these pages, so they can get stats form VS Marketplace iso Gallery: https://social.msdn.microsoft.com/Profile/ErikEJ/extensions
Where do project template categories for custom project types come from? I have a VSIX which if installed in the "normal" instance of will appear in a "CPS Projects" category, which isn't defined anywhere in my solution. When installed into the experimental instance of Visual Studio, it will appear in a "ADF Community" category (which is a name related to my project type, so it's acceptable). Unless, I also have installed the WindowsScript sample from Microsoft/VSProjectSystem in the experimental instance, in which case my template appears in a "Windows Script" category, while the actual Windows Script template appears in a "WindowsScript" (no space) category. Why does the Windows Script sample change the category of my unrelated project template?
My private gallery is no longer behaving correctly after update 3. It shows up but when I look at it under 'online' section, its content is the same as the default "visual studio marketplace" so it is unusable. We've been using a regular web service for years instead of atom or sharepoint list so wondering if that support was removed
@sharwell We have changed this code now. We are now using the the RDT FindAndLockDocument() method. This returns the IVshierarchy and itemID. Then we do a call to hierarchy.GetProperty() and we ask for a property from which we know what our return value is. The IVsHierarchy matches the project. With GetProperty() you can also locate the project object when needed.
Our call to FindAndLockDocument looks like this:
rdt.FindAndLockDocument((uint)(_VSRDTFLAGS.RDT_NoLock), fileName,out hierarchy, out itemID, out unkDocData, out cookie);
Our call to FindAndLockDocument looks like this:
rdt.FindAndLockDocument((uint)(_VSRDTFLAGS.RDT_NoLock), fileName,out hierarchy, out itemID, out unkDocData, out cookie);
Make sure you Marshal.Release unkDocData if the return value is not IntPtr.Zero
Does anybody know why IVsUIShellOpenDocument.OpenStandardEditor() returns E_ABORT (0X8004004) under certain circumstances.
Background info: we have implemented support for the Test Explorer window in our extension recently
When clicking on a source line in this window then opening a file will always fail with this error. Opening the file from the solution explorer seems to go through the same route in our code and works successfully. I checked and in both cases the code is executed on the UI thread, so that is not the problem. We are using the __VSOSEFLAGS.OSE_ChooseBestStdEditor for the openflags and an empty Guid for the logicalView. The strange thing is that it also fails when the document is already open.
When I add a call to VsShellUtilities.IsDocumentOpen() and return the IVsWindowFrame from the already open file, then the TestExplorer correctly navigates to the source code line of the test that failed.
Background info: we have implemented support for the Test Explorer window in our extension recently
When clicking on a source line in this window then opening a file will always fail with this error. Opening the file from the solution explorer seems to go through the same route in our code and works successfully. I checked and in both cases the code is executed on the UI thread, so that is not the problem. We are using the __VSOSEFLAGS.OSE_ChooseBestStdEditor for the openflags and an empty Guid for the logicalView. The strange thing is that it also fails when the document is already open.
When I add a call to VsShellUtilities.IsDocumentOpen() and return the IVsWindowFrame from the already open file, then the TestExplorer correctly navigates to the source code line of the test that failed.
@zeaposs We are not detecting anything. The Test Explorer window calls DTE.ItemOperations.OpenFile when you click on a failed test, and passes the filename and a null guid for the logicalView. This arrives at ProjectNodeOpenItem which then results in FileDocumentManager.Open() where call the OpenStandardEditor is. Maybe the DTE layer is the cause of the problem? I have no idea, I cannot debug into that because that layer is unmanaged.
The strange thing is that it also fails when the file is already open...
@RobertvanderHulst That strange thing bothers me, something similar was around here before: https://gitter.im/Microsoft/extendvs?at=597e8d84329651f46ed7f95d .VS was acting weird depending on whenever the file is already open or not. But in that case it was just opening with a different editor and not with an error.
In that case adding the editor factory fixed the problem. apoch/epoch-language@ba0ad98
Well we already have an editor factory so that cannot be the problem
What I will try is to call OpenDocumentViaProject in stead of OpenStandardEditor. Maybe that works.
(i need to know some props to build it for mono on our device)
@zeaposs I have added an overload to my ProjectNode code (we are using MPF) for the OpenItem() method. In this overload I am now opening the file with IVsUIShellOpenDocument.OpenDocumentViaProject() and this works. Thanks for the suggestions. You saved my day !
thanks
@AlonAm You have to use
IVsUIShell.ShowContextMenu, and define your menu items as part of your VSCT. It's quite convoluted if you are used to just working in a WPF tool window, but you can see an example here: https://github.com/tunnelvisionlabs/InheritanceMargin/blob/102eaca2d5a0c3a387711339d16024c77c48b82d/Tvl.VisualStudio.InheritanceMargin/CommandTranslation/CommandRouter.cs#L47
@AlexEyler it is set in the registry key. See this post I made that has screen shots. I have a tool that sets to the registry but that is irrelevant as I could just manually set there myself....its in the instance's privateregistry.bin. https://social.msdn.microsoft.com/Forums/vstudio/en-US/4e80ba40-35f2-4769-8ae2-bd6c7bdb21d9/vs-2017-update-33-causes-my-private-extension-gallery-to-not-show-correctly-anymore?forum=vssetup
Other than that - if you'll use the VS SDK from 2015, it will deploy the debug version to vs2015 instance.
@chelvaric You should target vs2015 versions of the dll's. And it will work fine too on vs2017, because all those assemblies will be rebinded to newer versions via devenv.exe.config configuration. Also, it's better to use nuget packages with assemblies you want to use: https://www.nuget.org/profiles/VisualStudioExtensibility
Does anyone know if it is programmatically possible to determine if an extension is free, trial or paid for ? I’m pretty sure the answer to this question will be “no”, since this is defined as part of the extension manifest, only as part of the market place website, but thought I’d ask anyway. Thanks
@koo9 I'm in the process of doing it, using the Common Project System and a combination of the sample in Microsoft/VSProjectSystem and looking at dotnet/project-system. But I find it frustrating, as some stuff only works for .NET projects, and there's little documentation, so it takes a lot of effort to solve little issues. I've been unable to solve big problems myself unless a Microsoft employee replies to one of my github issues, but I also have some unanswered github issues, so no solution to some issues I have trying to finish off my project system.
where the sample project downloaded from the link MPF for Projects 2013 has lots of issue after upgrading to the vs 2017 project. im in the process of fixing those issue see if it will work
