{
	"id": "bc1ed68d-c4a2-4972-9455-f5e21e70dedc",
	"created_at": "2026-04-06T00:17:52.420168Z",
	"updated_at": "2026-04-10T03:21:13.852928Z",
	"deleted_at": null,
	"sha1_hash": "b745aa835588762011e649a613ceaac2c8798d03",
	"title": "Visual Basic support planned for .NET 5.0",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 37284,
	"plain_text": "Visual Basic support planned for .NET 5.0\r\nBy .NET Team\r\nPublished: 2020-03-11 · Archived: 2026-04-02 10:36:14 UTC\r\nWe’ve heard your feedback that you want Visual Basic on .NET Core. Earlier versions of .NET Core supported\r\nClass Library and Console applications types. Starting with .NET 5 Visual Basic will support:\r\nClass Library\r\nConsole\r\nWindows Forms\r\nWPF\r\nWorker Service\r\nASP.NET Core Web API\r\nWe are supporting these application types to provide a good path forward for the existing VB customer who want\r\nto migrate their applications to .NET Core. This allows Visual Basic customers to take advantage of new platform\r\nfeatures like side-by-side deployment, cross platform support, performance and new API improvements.\r\nOne of the major benefits of using Visual Basic is that the language has been stable for a very long time. The\r\nsignificant number of programmers using Visual Basic demonstrates that its stability and descriptive style is\r\nvalued. Going forward, we do not plan to evolve Visual Basic as a language. This supports language stability and\r\nmaintains compatibility between the .NET Core and .NET Framework versions of Visual Basic. Future features of\r\n.NET Core that require language changes may not be supported in Visual Basic. Due to differences in the\r\nplatform, there will be some differences between Visual Basic on .NET Framework and .NET Core.\r\nIf you are happy with .NET Framework, you can be confident that it will remain supported as long as Windows is\r\nsupported because it is shipped with the OS. Both Visual Basic and C# customers can continue to use .NET\r\nFramework and need to port to .NET Core only if you want features like those listed above. If your application\r\nuses technologies that aren’t supported on .NET Core, like WebForms, Workflow or WCF, you might want to stay\r\non .NET Framework because porting will require work to move to newer technologies.\r\nVisual Studio regularly adds new features to improve the experience for developers, including those using Visual\r\nBasic and either .NET Core or .NET Framework. An example is the recent addition of IntelliCode for Visual\r\nBasic.\r\nVisual Basic is a great language and a productive development environment. The future of Visual Basic will\r\ninclude both .NET Framework and .NET Core and will focus on stability, the application types listed above, and\r\ncompatibility between the .NET Core and .NET Framework versions of Visual Basic.\r\nAuthor\r\nhttps://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/\r\nPage 1 of 2\n\n.NET is the free, open-source, cross-platform framework for building modern apps and powerful cloud services.\r\nSource: https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/\r\nhttps://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/\r\nPage 2 of 2",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://devblogs.microsoft.com/vbteam/visual-basic-support-planned-for-net-5-0/"
	],
	"report_names": [
		"visual-basic-support-planned-for-net-5-0"
	],
	"threat_actors": [],
	"ts_created_at": 1775434672,
	"ts_updated_at": 1775791273,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/b745aa835588762011e649a613ceaac2c8798d03.pdf",
		"text": "https://archive.orkl.eu/b745aa835588762011e649a613ceaac2c8798d03.txt",
		"img": "https://archive.orkl.eu/b745aa835588762011e649a613ceaac2c8798d03.jpg"
	}
}