search

dotnet / vblang

The home for design of the Visual Basic .NET programming language and runtime library.
290 stars 64 forks source link

Any updates? #476

Open jpepg4 opened 5 years ago

jpepg4 commented 5 years ago

The VB blog has been very quite and .NET Core 3.0 doesn't seem to have VB project templates. At the very least someone should post the VB blog with current status. I don't actively develop in VB but it has a special place in my heart because I learned to program on QB and VB 5.0 . VB could be a great beginner language if it actually gets .NET Core support which drives the ability for it to be used for mobile and modern ASP.NET development.

ocdtrekkie commented 5 years ago

I know they've got a Windows Forms designer for .NET Core 3.0 that's still in an early preview, and hence, just an extension at this point. Presumably a lot of VB project templates will make sense to convert to .NET Core 3 once that's no longer a preview and a part of Visual Studio proper.

paul1956 commented 5 years ago

I don't understand the question, there are many VB project Core templates, what is missing for VB is a WinForms project Template (C# has one in 16.4 Preview 1) and of course the designer. There are instructions that I and others have posted to convert a Framework project to Core 3.0 and use the Framework WinForms designer with a shared project and in 16.4 Preview 1 there is a minimal designer I haven't tried yet. image

HEIC-to-JPEG-Dev commented 5 years ago

There is no WPF template for .Net Core 3.0.

jpepg4 commented 5 years ago

Yep no WPF or Winforms or Blazor or good mobile app options. The entire appeal of VB isn't to go and write libraries, especially for beginning users. IMHO the focus of VB going forward should be to provide a easy pathway into programing on platforms that are actually used.

ConstantinRom commented 5 years ago

Everyone who wants WPF and Windows Forms .NET Core support in VB.NET should vote here: https://developercommunity.visualstudio.com/idea/750543/add-visual-basic-support-to-net-core-3-wpfwindows.html

AdamSpeight2008 commented 5 years ago

No or little information about nullable reference types, interoperability with other .net languages.

Berrysoft commented 4 years ago

Sorry for being late, but I HAVE ADDED VB.NET TEMPLATES for WPF and WinForms. The reason why they are not in the SDK is because Microsoft.VisualBasic.dll is not completed.

aarondglover commented 4 years ago

I can't believe that there is no commitment by Microsoft to support VB in .NET Core Winforms and WPF.

WTF are we all doing here if that's the case. The support a language which will be stuck on 4.8 Framework or consigned to doing hello world console apps in .NET Core.

Arguably Winforms and WPF is the bread and butter or MANY VB projects and to not yet have a commitment to supporting VB on .NET Core is atrocious. Even the diatribe which was the VB strategy made it clear that VB would be supported where it made sense to do so. What could be more clear than this use case.

@KathleenDollard .. I'm clearly not the only person tired of the weasel words and ambiguity with regard to the future of VB and its support as a first class citizen in the .NET Core etc. I thought you would be a strong advocate for VB when you assumed your role but from my observations you are fitting in very well with rest of the C# fanbois and sicophants at Microsoft.

paul1956 commented 4 years ago

The latest update of VS Preview has broken all the workarounds that allow VB WinForm apps to be edited. Prior to that you could have a parallel Framework solution and edit the form, now when you try the Framework app tries to use the new Core editor and you just get a blank screen or an error telling you to enable the new editor.. Also the settings.editor which worked for VB now fails even though it shows up in properties of a VB Core project. VB seems to be going backwards. I have reported the settings issue through Feedback. Not clear how to report the Framework workaround not working. Also @Berrysoft where should the VB.NET Templates show up, I am not seeing them in Version 16.4.0 Preview 6.0. I have seen some discussion of unique VB features becoming available for C# (Single instance Apps for example), settings would also be nice. This seems like the time to move those things to common code.

Berrysoft commented 4 years ago

@paul1956 where should the VB.NET Templates show up

It's up to Visual Basic team (see here), and I'm only a contributor. If you really want the templates now, it is easy to clone the latest WPF and WinForms repository, pack the template by yourself, and replace the templates from the .NET Core SDK.

paul1956 commented 4 years ago

@Berrysoft easy is subjective. I know how to clone repository, but no clue how to do the rest. Even if I did know how without any designer there is not much I can do.

Berrysoft commented 4 years ago

but no clue how to do the rest.

Take WinForms templates for example. Change the SDK version in global.json to an installed one, and execute dotnet pack in pkg/Microsoft.Dotnet.WinForms.ProjectTemplates directory. Then you get the Microsoft.Dotnet.WinForms.ProjectTemplates.nupkg.

Replace the nupkg in C:\Program Files\dotnet\templates\<version> and remove the cache in C:\Users\<username>\.templateengine\dotnetcli\<version>. Run dotnet new to generate the cache. That's how to get the VB template.

Padanian commented 4 years ago

Anyone wishes to share the result?

Da: Berrysoft notifications@github.com Inviato: sabato 30 novembre 2019 02:42 A: dotnet/vblang vblang@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Oggetto: Re: [dotnet/vblang] Any updates? (#476)

but no clue how to do the rest.

Take WinForms templates for example. Change the SDK version in global.json to an installed one, and execute dotnet pack in pkg/Microsoft.Dotnet.WinForms.ProjectTemplates directory. Then you get the Microsoft.Dotnet.WinForms.ProjectTemplates.nupkg.

Replace the nupkg in C:\Program Files\dotnet\templates\ and remove the cache in C:\Users\.templateengine\dotnetcli\. Run dotnet new to generate the cache. That's how to get the VB template.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/dotnet/vblang/issues/476?email_source=notifications&email_token=AB3I2BEBAHITZF5GS6AKJU3QWHAGFA5CNFSM4I2COTE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPXEIQ#issuecomment-559903266 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AB3I2BF4AI4DMJCPEV4L4ULQWHAGFANCNFSM4I2COTEQ . https://github.com/notifications/beacon/AB3I2BDR46X3TA2CKQ375D3QWHAGFA5CNFSM4I2COTE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPXEIQ.gif

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/dotnet/vblang/issues/476?email_source=notifications\u0026email_token=AB3I2BEBAHITZF5GS6AKJU3QWHAGFA5CNFSM4I2COTE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPXEIQ#issuecomment-559903266", "url": "https://github.com/dotnet/vblang/issues/476?email_source=notifications\u0026email_token=AB3I2BEBAHITZF5GS6AKJU3QWHAGFA5CNFSM4I2COTE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFPXEIQ#issuecomment-559903266", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

paul1956 commented 4 years ago

I looked at the VB WinForms project template, I don't believe the resulting project will run. Where is the code that is normally in Applications.Designer.vb also in framework the default project has Settings.Settings.

Berrysoft commented 4 years ago

Those codes are not necessary to run. As to Settings.settings, the c# template also moves that.

paul1956 commented 4 years ago

As @Berrysoft pointed out elsewhere with 3.1 the StartupObject setting in vbproj file will start the application, I don't know if it using the setting from Application.myapp but it basically works without adding Main.

Berrysoft commented 4 years ago

That's not true. The entry point is auto-generated by specifying <StartupObject> node in the project file.

paul1956 commented 4 years ago

I have always specified

VBApp.Form1

and in 3.1 you are correct the app starts. Thanks for the update.

paul1956 commented 4 years ago

If looks like the GitHub branch Release /Fix_2395_pack_Microsoft.VisualBasic.Forms has a lot of what is needed to more completely support VB on Core 3.1. Has this been released? The VS UI disabled editing of AssemblyInfo.vb but that is where Framework stores several settings (autosave settings on exit and Application information (version, name...) the SplashScreen.vb form uses values from AssemblyInfo, with the fix above the SplashScreen display could work but without the values it will not compile. Is there any documentation about how all these pieces go together and what are things that need to change from Framework to utilize these features.