tinaschrepfer on tinali
Remove use of "any" content typ… (compare)
tinaschrepfer on tinali
Merge pull request #169 from Mi… Add sample support for "any" co… (compare)
tinaschrepfer on master
Update VSSDK package and remove… Merge pull request #169 from Mi… (compare)
Hi all,
I created a Visual studio extension (code analyzer with fix + provide a setting in option page)
the setting can be used in VS 2017 Community + VS 2017 Pro + VS 2019 Community.
But not work in VS 2019 Pro + Enterprise
When I downloaded VS 2019 Enterprise and debug my extension, It shows a lot of errors at XAML Binding Failures. Please see above picture.
How do I fix this and debug my extension?
Source code: https://github.com/jinyafeng/DocumentationAssistant
Thanks a lot
@hemantnavarkar
I have Visual Studio Isolated Shell applicaton, I have hosted one Windows Form View on Factory.
The Windows form having Grid control and Property Grid.
Problem is when user clicks on the Property Grid and do Shift+Alt+Enter then window maximize but the same not working on
GridView ?
I tried to handle the KeyDown event as below
private void dataGridView1D_KeyDown(object sender, KeyEventArgs e)
{
if (e.KeyCode == Keys.Enter && e.Modifiers == (Keys.Shift | Keys.Alt))
{
e.Handled = true;
return;
}
base.OnKeyDown(e);
}
the condition never calls.
Please suggest any solution
Recommended approach now @usysware is to just use the roslyn apis directly.
Correct me if I'm wrong please, Roslyn is available for C# and VB only but not C++. My extension supports all these 3 main languages supported by VS - C#, VB and C++. Sounds like I'd have to continue using file code model for C++ but switch over to Roslyn for C#/VB and recode existing code model support. If so, that totally blows.
Yeah, threading and performance issues I'm well aware of regarding file code model unfortunately. It's definitely not the prettiest aspect of file code model to deal with.
Right. But c++ doesn't have records. So your need there doesn't apply.
I disagree. What I was bringing up there is that I have 1 and consistent way of presenting the code model to the user for all 3 major in-the-box VS versions languages. With this new change for my extension to move forward I'd have to still continue using file code model for C++ projects but switch over to Roslyn for C#/VB. No matter how you slice it, it's gonna be 2 classes that produce similar outcome to maintain now, and as you pointed out one that has threading implications and one that doesn't. That's the most troubling part for me and is gonna be a cluster/f. Now, if there was Roslyn for C++ I wouldn't be airing it here. Alternatively, I'd have to drop C++ support, which my users aren't gonna be happy about.
Inline
MSBuild
task to update values of common variables such as AdditionalIncludeDirectories
programatically , AND have them be reflected in Visual Studio property pages. I'm trying to leverage the information here but am still failing to get the results: https://github.com/dotnet/project-system/blob/master/docs/design-time-builds.md#targets-that-run-during-design-time-builds
Hi,
Maybe someone know how to configure ToolWindow search view? I added search as described here https://docs.microsoft.com/en-us/visualstudio/extensibility/adding-search-to-a-tool-window?view=vs-2019. Is it possible to change (customize) something? Thanks!
I am getting this warning with all the latest package references:
WARNING: NU1603: Microsoft.VisualStudio.Data.Framework 16.7.30328.74 depends on Microsoft.VisualStudio.Shell.Interop (>= 7.10.6073) but Microsoft.VisualStudio.Shell.Interop 7.10.6073 was not found. An approximate best match of Microsoft.VisualStudio.Shell.Interop 16.7.30328.74 was resolved.
Should the dependency be updated?
@ErikEJ i don't bother adding individual SDK packages anymore. I just install the Microsoft.VisualStudio.SDK nuget package (or an earlier version of it depending on requirements)
it greatly simplifies the whole SDK experience, and you never have to worry about individual package dependency versions again. it covers all the main packages that you'd normally need.
you can still individually add anything that isn't included in the SDK nuget package