Visual Studio 2022 .Net MAUI Project Intellisense not working for some XAML files - xaml

I have a very simple .Net MAUI project with three (XAML) pages. The project compiles and runs without any errors or warnings.
When I edit one of the XAML pages and type a < character, the following intellisense pop-up is displayed:
NOTE: The pop-up is missing several XAML statements that should be present.
When I edit a different XAML page, the following intellisense pop-up is displayed:
This time, the pop-up contains ALL of the XAML statements that one would expect.
In two of the three XAML pages, the pop-up works correctly (all statements displayed), but on one page, XAML statements are always missing -- I cannot figure out why.
Initially, I thought it may have been contextual in nature, that is, showing only those XAML statements that would be valid at the insertion point. However, in each file, my insertion point was directly below a ScrollView statement.
Any ideas why intellisense works with some XAML pages and not others? Is this a known bug in Visual Studio?
Thanks in advance.
Update: 19-Sep-2022
I think I have confirmed why this is happening -- on XAML pages WITHOUT any comments between the following lines:
<?xml version="1.0" encoding="utf-8" ?>
<ContentPage ...
... intellisense works just fine. For example, when I hover my cursor over the ContentPage node, the following is displayed:
... and when I try to insert other nodes, intellisense is present (all options are present in the pop-up).
However, on a page that intellisenses does NOT work, I have a large comment block between the two lines above, for example:
<?xml version="1.0" encoding="utf-8" ?>
<!--
Large comment block (approximately 90 lines.
-->
<ContentPage ...
When this comment block is present, intellisense stops working, that is, if I hover my cursor over the ContentPage node, nothing is displayed and when I try to insert other nodes, the following popup (which is missing all options) is displayed:
The only way around this (so far) is to remove the comment block, or move the comment block to the bottom of the page, after the closing ContentPage node.
Environment (copied from Help -> About Microsoft Visual Studio):
Microsoft Visual Studio Community 2022
Version 17.3.4
VisualStudio.17.Release/17.3.4+32901.215
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Community
ADL Tools Service Provider 1.0
This package contains services used by Data Lake tools
ASA Service Provider 1.0
ASP.NET and Web Tools 17.3.376.3011
ASP.NET and Web Tools
Azure App Service Tools v3.0.0 17.3.376.3011
Azure App Service Tools v3.0.0
Azure Data Lake Tools for Visual Studio 2.6.5000.0
Microsoft Azure Data Lake Tools for Visual Studio
Azure Functions and Web Jobs Tools 17.3.376.3011
Azure Functions and Web Jobs Tools
Azure Stream Analytics Tools for Visual Studio 2.6.5000.0
Microsoft Azure Stream Analytics Tools for Visual Studio
C# Tools 4.3.0-3.22423.10+b35bb0baca1071d50cc4f8cf5a1a89e7cc112461
C# components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Common Azure Tools 1.10
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
Extensibility Message Bus 1.2.6 (master#34d6af2)
Provides common messaging-based MEF services for loosely coupled Visual Studio extension components communication and integration.
Microsoft Azure Hive Query Language Service 2.6.5000.0
Language service for Hive query
Microsoft Azure Stream Analytics Language Service 2.6.5000.0
Language service for Azure Stream Analytics
Microsoft Azure Tools for Visual Studio 2.9
Support for Azure Cloud Services projects
Microsoft JVM Debugger 1.0
Provides support for connecting the Visual Studio debugger to JDWP compatible Java Virtual Machines
Mono Debugging for Visual Studio 17.3.20 (3f4cb00)
Support for debugging Mono processes with Visual Studio.
NuGet Package Manager 6.3.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit https://docs.nuget.org/
Razor (ASP.NET Core) 17.0.0.2232702+e1d654e792aa2fe6646a6935bcca80ff0aff4387
Provides languages services for ASP.NET Core Razor.
SQL Server Data Tools 17.0.62207.04100
Microsoft SQL Server Data Tools
ToolWindowHostedEditor 1.0
Hosting json editor into a tool window
TypeScript Tools 17.0.10701.2001
TypeScript Tools for Microsoft Visual Studio
Visual Basic Tools 4.3.0-3.22423.10+b35bb0baca1071d50cc4f8cf5a1a89e7cc112461
Visual Basic components used in the IDE. Depending on your project type and settings, a different version of the compiler may be used.
Visual F# Tools 17.1.0-beta.22363.4+1b94f89d4d1f41f20f9be73c76f4b229d4e49078
Microsoft Visual F# Tools
Visual Studio IntelliCode 2.2
AI-assisted development for Visual Studio.
VisualStudio.DeviceLog 1.0
Information about my package
VisualStudio.Mac 1.0
Mac Extension for Visual Studio
VSPackage Extension 1.0
VSPackage Visual Studio Extension Detailed Info
Xamarin 17.3.0.296 (d17-3#a0ff24b)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin Designer 17.3.0.208 (remotes/origin/d17-3#e4f67afef)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.
Xamarin Templates 17.2.28 (9b3d244)
Templates for building iOS, Android, and Windows apps with Xamarin and Xamarin.Forms.
Xamarin.Android SDK 13.0.0.0 (d17-3/030cd63)
Xamarin.Android Reference Assemblies and MSBuild support.
Mono: dffa5ab
Java.Interop: xamarin/java.interop/d17-3#7716ae53
SQLite: xamarin/sqlite/3.38.5#df4deab
Xamarin.Android Tools: xamarin/xamarin-android-tools/main#14076a6
Xamarin.iOS and Xamarin.Mac SDK 15.12.0.2 (87f98a75e)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

I compared the intellisense in Visual Studio Community 2022(17.3.4) with Visual Studio Community 2019, the intellisense works properly for the latter version even though with long comment block. It looks like it's a potential issue for the Visual Studio, you can report a problem with the Visual Studio product via this link.

Related

error BC36716: Visual Basic 9.0 does not support implicit line continuation in VB:NET in VS 2019

I need to build Class Library (.dll) as a part of my custom IIS (SharePoint 2010) web service for .NET Framework 3.5, but VS2019 (Community edition) using VB.NET refuses me to build it with the subjected error.
I found suggestions to disable "Pretty listing (reformatting) of code" in Options > Text Editor > Basic Advanced (in settings of Visual Studio), but I found this functionality useful otherwise so I would prefer any different solution.
Another suggestion was about deleting some "LangVersion" (or similar) tag from .vbproj file, but I don't have there any ;-(
p.s. I had troubles with these in VS2015 and VS2017 as well...
Any suggestions?
Thanks in advance. #JK

Universal Windows App Visual Studio 2015 Community no designer, no controls in toolbox, no properties

I am using Visual Studio Community 2015 to create Universal Windows App.
I am facing following problems-
1. No designer view.
2. No controls in toolbox.
3. Property window don't show any properties of control.
4. No phone emulators are shown after installing EmulatorSetup.exe
Visual Studio Installed Components are as follows
Microsoft Visual Studio Community 2015
Version 14.0.24720.00 Update 1
Microsoft .NET Framework
Version 4.6.01055
Installed Version: Community
Visual Basic 2015 00322-20000-00000-AA136
Visual C# 2015 00322-20000-00000-AA136
Visual C++ 2015 00322-20000-00000-AA136
Application Insights Tools for Visual Studio Package 4.2.60128.3
ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11106.0
ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
Common Azure Tools 1.5
JetBrains ReSharper Ultimate 10.0.2 Build 104.0.20151218.120627
JSLint.NET for Visual Studio 2.2.0
Microsoft Azure Mobile Services Tools 1.4
NuGet Package Manager 3.3.0
PreEmptive Analytics Visualizer 1.2
SQL Server Data Tools 14.0.50616.0
TypeScript 1.7.6.0
Visual Studio Tools for Universal Windows Apps 14.0.24720.00
Web Essentials 2015.1 1.0.209
I have had the same problem and the only way I have got the designer to work is (and this should work if build 10240 is acceptable for your development):
Open your project
Go under "Project" to "Properties"
Select "Application" on the left and change BOTH the target version and the min version to "Windows 10 (10.0; Build 10240)
Once you do that the XAML designer will start working again. I've had to do this on 4 different workstations and it's worked everytime.
As to why build 10568 doesn't work? Got me, agile development, will be fixed in a patch? :p
I had the same problem and could not change BOTH versions to Build 10240 as the Application listbox only showed 10586 in Properties/Application. I thought I could arrange that by editing the .csproj file, which is XML after all, but any change there makes all files in the Solution Explorer immediately unavailable. Then I noticed (running Winver.exe) that my W10 still shows build 10240 despite regularly (but not automatically) running Windows updates. Despite multiple solutions tried, this didn't change. I finally used the MediaCreation Tool to download a new Windows 10 on a USB stick and reinstalled Windows 10, preserving apps and data. And now I am really on 10586 ...and the Design mode shows again when I open my project.
I hope this helps a few!
If you are looking for the SSIS toolbox, click SSIS tab, then SSIS Toolbox.

Add Visual Studio Web to Visual Studio Desktop

I just wanted to start learing WCF and could not find the WCF Service Library in my Visual Studio 2012 Windows Desktop. After reading and searching I found out that I need the VS Web to get access to it. Since I try to avoid installing two versions of VS I wat to ask if it is possible to add VS Web to VS Desktop.

Using FxCop code analysis for .NET 4.5 applications

Is it possible to use FxCop for .NET 4.5 applications?
I am looking to use FxCop with the Visual Studio 2013 Professional edition.
Visual Studio 2013 Professional comes with Static Code Analysis (which is FxCop, just a fancy name for it).
In this link some information is provided:
As a developer, you can run code analysis on your project automatically or you can run it manually.
To run code analysis each time that you build a project, you select Enable Code Analysis on Build (defines CODE_ANALYSIS constant) on the project's Property Page. For more information, see How to: Enable and Disable Automatic Code Analysis for Managed Code.
To run code analysis manually on a project, on the Analyze menu, click Run Code Analysis on ProjectName. For more information, see How to: Enable and Disable Automatic Code Analysis for Managed Code.
This version runs perfectly on .NET 4.5.
FxCop 1.36 is a standalone version of Code Analysis. Microsoft no longer supports or works on the standalone version and currently only working on the integrated version that is included in Visual Studio.
There is a Uservoice going on which asks Microsoft to update the standalone FxCop version. See this link.

How to open visual basic 6 program with visual studio.net

I want to open a program (written in Visual basic 6) to be open in Visual Studio.net. Please guide, how could I do that?
While trying to open VB6 (.vbp file) program directly from the OPEN project option in visual studion.net, I was getting this error,
"Visual Basic 6 (.vbp) files cannot be opened in Visual Studio"
I am trying to open in VS 2010.
Visual Studio 2010 does not support VB6 projects. See the link here
From the msdn documentation:
Visual Studio 2010 does not provide tools for upgrading applications and projects from Visual Basic 6.0. If you want to upgrade your project from Visual Basic 6.0 to Visual Basic 2010, you can use the upgrade tools provided with earlier versions of Visual Studio and then upgrade the project again in Visual Studio 2010.
Visual Basic Tools for Visual Studio
There's a plugin called Visual Basic Tools for Visual Studio that provides the following features:
load classic VB workspace- and project-files and offers quick access to the extension´s options
integrates with the solution explorer and the code editor having support for syntax highlighting, basic outlining (allows to expand/collapse methods, properties and types) as well as navigation bar support.
Classes, Types, Modules, Forms and Controls can be inspected using the Object Browser and Class View.
From the reading, it's unclear if you can actually build the project, though it does say:
The import tool creates a new solution and MSBuild compatible projects.
Links to the plugin by VS Version
2012-2013
2015
2017
RAD Basic
There is also an independent IDE called RAD Basic that claims the following features:
New and modern IDE (Integrated Development Environment) with form designer supporting drag and drop, code completion, refactoring tools, etc.
RAD Basic Compiler: Compiler 100% compatible with your VB6 project (vbp, frm, bas and cls files). Generate native executables (exe and ocx) in both 32-bit and 64-bit.
RAD Basic Forms: Reimplementation of common VB6 controls and components supporting 32-bit and 64-bit.
etc.
Speaking from my experience, it's not easy to open a Visual Basic 6.0 project in any versions of Visual Studio above 2008.
Although 2008 and below versions do provide an automatic function to convert Vb6 code to the VB.net framework. But, the problem starts after the conversion - it can skip some code, add functions/variables on its own, or modify the functional behavior on its own, and with that the VB.proj will be created with errors and you will not be able to open it anywhere as a solution file. The same with any 3rd party tools.
If you want to open the VB6 code try Visual Basic 6.0 Portable edition.
But headache will still follow you there, please refer this link
Installation of VB6 on Windows 7 / 8 / 10
Make sure you are clicking on the project file itself... Right click on the file and select "Open With" and select your visual studio program. It may need to be converted and if so, it will prompt you to convert the project.
Thanks!
Download Visual Basic Tools for Visual Studio,allows to work with classic VB workspaces and projects