Visual Studio 2019 no designer support on Windows Forms on .Net 5.0 - windows-forms-designer

It seems like I've lost designer support for Windows Forms on .NET 5.0. Everything was working ok last week, but now, as you can see, there's no designer support:
This is not a new .NET 5.0 Windows Forms projet, it's been migrated from .NET 4.8. I'm using Visual Studio 19 16.8.4.
Any ideas on what's going on?

This worked for me.
How to migrate a Windows Forms desktop app to .NET 5
Preview WinForms designer in Visual Studio.
To enable the designer, go to Tools > Options > Environment > Preview Features and select the Use the preview Windows Forms designer for .NET Core apps option.

Related

Visual Studio 2022 - Visual Basic ASP.NET Web Application

I 've downloaded/installed Visual Studio 2022 Community Edition but there is no way to find the ability to create a new ASP.NET Web Application (.Net Framework) using Visual Basic. It looks like i can only develop Windows Desktop Application using it.
Has it been deprecated ? If not how can i bring it back to life?
Run the Visual Studio installer.
Inside the .NET group, below the ".NET Framework 4.8 targeting pack", there is a component named .NET Framework project and item templates and make sure that you have installed it.
Visual Studio 2022 Installer - individual components .in NET group
Hovering over the component, the tooltip describes it as:
Enables .NET Framework project templates, item templates & related
features for .NET Framework development.
See: https://www.howtosolutions.net/2021/11/visual-studio-missing-asp-net-web-application-template-dotnet-framework/

Installing .Net framework 4.5 or 4.6 to MS visual studio community 2017

I installed MS visual studio community 2017 along with all the necessary plugins but when I am trying to create a web application in C# only the .net frameworks upto 3.5 are available and as a result I can not create MVC based C# web applications because only the option empty web application appears. I installed the .net framework 4.6.2 development pack separately but even that the issue could not be corrected. How can I solve this issue?

ASP.NET 4.5 is not registered after upgrading to Windows 10

I have a WCF web service which was working on Windows 8.1. After upgrading to Windows 10, I noticed that the IIS is not installed anymore. So I installed it along with ASP.NET 4.6 in Windows features. Now, when I open the project in VS2013 it says that ASP.NET 4.5 is not registered. Shouldn't it work with ASP.NET 4.6?
I had the same issue and was able to fix it by installing Visual Studio 2013 Service Pack 5 (the latest at that time).
You can download it from here:
https://www.visualstudio.com/en-us/news/vs2013-update5-vs.aspx
Make sure to select the right version according to the Visual Studio version you have.

which visual studio version should i use for asp.net framework 1.1 live maintenance

We have asp.net 1.1 framework application is in live environment with appx 200 users.
Which visual studio version is safe to use for maintenance?
We are not planning to migrate yet. I am using vs 2008 for developing a 3.5 application right now so not want to take the risk of visual studio conversion.
You can check with visual studio2005 version
Use Visual Studio .NET 2003 and MSDN Library of Jan 2006.
I think you can use any Visual studio once your project is targeting the correct framework. This Post talks you through installing aspt 1.1 on a windows 8 machine.

Is it possible to force Visual Studio 2010 to use Visual Basic 10?

To reproduce the error I'm getting:
Create a new Visual Studio 2010 ASP.NET web site in Visual Basic, targeting .NET 2.0
Type "Public Property Test As String"
Observe "Visual Basic 9.0 does not support auto-implemented properties." error
Visual Studio 2010 is happy to use VB 10 against .NET 2.0-targeted Windows Forms applications, this only appears to be an issue with ASP.NET.
Is there a way to force Visual Studio 2010 to use VB 10 when targeting .NET 2.0?
No. A Web Site project is one that compiles within ASP.NET at runtime - as such, you've chosen to ask ASP.NET to run it as a .NET 2.0 project, so it will use the .NET 2.0 vbc Visual Basic compiler that's part of .NET. That compiler has no knowledge of VB 10, and so you're rightly being warned that it will not work.
The reason it can work for other project types is because the compilation is happening using a later compiler (usually the one built into Visual Studio).

Resources