There are instructions out there on how to do it but, if you have only just started, it may be easier just to create a new project.Īlso note that, in my opinion, the current issues with VB WinForms in. It can be done but it's not just a case of selecting a version in the properties. Just note that it's not trivial to convert a project from. NET Framework 4.8 or some other recent version. You will lose little to nothing by reverting to. NET 5.0 but they would likely be of little, if any, value to you in a basic WinForms application. Should I just revert the target to 4.7.2 ?That's completely up to you. I am not deploying anything, and just running my programs on my laptop for myself. NET Core projects, because everything has been rebuilt from the ground up.NET Framework projects are unaffected. ![]() Let me stress again that this ONLY affects. It's for just this sort of thing that VS has a Send Feedback menu in the top, right corner. If you want the issue fixed sooner, you should provided feedback to Microsoft about it. This issue will likely be fixed in a future update to VS but higher priority issues get fixed first, so the more people who report this issue, the sooner it will be fixed. You can double-click on that to be taken to the offending line of code and replace Form1 in the code yourself. After the name change, a compilation error will be generated. There are some minor changes, some things are still missing and there likely are some bugs.īased on my testing, if you change the name of the startup form, that change will not flow through to the MyApplication class and the OnCreateMainForm method. While things may look pretty much the same, that's because everything has been rebuilt to provide VB.NET WinForms support in. It's nothing to do with the VS version but the fact that you're targeting. Startup object = Sub MainSo now we're getting somewhere. In 16.8.4, if you changed it from Sub Main, you will not get the cascade update ![]() It is related to the recent version updateĮnable Application Framework is checked/selected in both versions Now, with 16.8.4, you will get build errors. It ALWAYS stays form1.vbīut, in every project, I rename property name from Form1 to frmMainĪnd the NAME cascades automatically to the Startup Object Do so in future.I never said anything about the filename. You should be and have always been doing what dday9 described but you obviously didn't on this occasion. It has always been the case that you can change the file name and have the type name changed automatically. It has never been the case that you can change the name of a type and have the file name changed automatically. "It" still does do "that" automatically, but that's not what you're doing.
0 Comments
Leave a Reply. |