Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Adam Speight
    @AdamSpeight2008
    I've published a small vbnet analyser. Number Suffix Analyser and Codefix
    Paul M Cohen
    @paul1956
    I just update my C# converter app to work on .Net Core 3.0 and added a readme. https://github.com/paul1956/CSharpToVB/tree/Core3.0 the converted code requires VS2019.
    Cory Smith
    @DualBrain
    @AdamSpeight2008 The link doesn't appear to work; also, is this available on github?
    Paul M Cohen
    @paul1956
    @DualBrain The reason the app may have crashed when you first installed it was an incorrect assumption about how VS creates folders during install. I can fix it in master if I can figure out how to get a single file from a branch into Master. The file "FileSupport.vb" needs to be updated.
    Adam Speight
    @AdamSpeight2008
    @DualBrain I hadn't made it public.
    Cory Smith
    @DualBrain
    So who else here is utilizing .NET Core 3.x?
    I do want to share how AWESOME!!!!! it is that you can combine three different options to have a small (relatively), "native" single executable that requires no installation. After the first start, having the application start pretty much instantly is also pretty incredible.
    Paul M Cohen
    @paul1956
    @corySmith Yes but something I am missing is how do I find file resources. I have language dictionaries and when I make it a single executable those don’t come along or if they do I don’t know how to read them.
    Aaron Glover
    @aarondglover
    I only recently discovered this fitter for VB.
    Aaron Glover
    @aarondglover
    Let me try that again without the interruption...
    I only just discovered the gitter for VB... Very hard to discover and unfortunately it seems to have lost momentum already 😩
    Paul M Cohen
    @paul1956
    @aarondglover what are you looking for?
    Cory Smith
    @DualBrain
    @aarondglover Welcome! It's not that it's "lost momentum"; we are still working on gaining momentum. ;-) With that said, is there something in particular you are looking for, want to share, etc.? If not, welcome and hope to hear more from you! Also, help spread the word. ;-)
    Cory Smith
    @DualBrain
    I'm so excited to share, with the latest version of the VS2019 preview build that I'm able to build a WinForms application in VB. To do so, I had to start with a default C# application converted to VB by hand; but now that it's converted... it's working (so far) as desired. We aren't 100% of the way there; meaning that there are a lot of VB'isms that aren't available... but I'll be honest... I'll take what I can take. ;-)
    Cory Smith
    @DualBrain
    For discussion: Why do you think it is important for VB to be on .NET Core?
    Paul M Cohen
    @paul1956
    Performance, x-platform, a future and dealing with project files is simple vs. guru only.
    Paul M Cohen
    @paul1956
    What was frustrating about the link was the lack of 2 letters in the entire document. I tripped on the fact that VB sort of works (about as well as C#) so no issue. Looking forward to next update for support of menu which at least shows up. Please provide a way to do new VB project with settings soon. I am still having big issues changing settings in designer. My settings files came with the port from framework and need changes to be edited and I have no examples.
    Cory Smith
    @DualBrain
    There are still many hurdles to getting things working. With that said, I just finished getting a utility project to the same functional stage as the .NET version. There does appear to be a rendering bug though in the "buttons" in a DataGridView - whether it's a bug or not... it DOES NOT look like the .NET counterpart. Additionally, NAudio (not a Microsoft project) "sort of" works with .NET Core - it provides excellent ability to playback audio... as for recording... not available. ????? With that said, I just spent several hours porting 8 classes out of that project (converting them to VB in the process) so that I can mix/match both NAudio in .NET Core (for what does work) with an internal replacement to the missing WaveIn functionality (that does exist - and works - in the .NET version of NAudio). It's a "simple" utility that serves to assist in recording over 7,000 audio recordings for a project that I'm working on.
    Paul M Cohen
    @paul1956
    @DualBrain The default font is different between Framework and Core, it causes all controls in Core that don't specify a font and size to render larger and in my case not fit. I changed the Framework Font to match the Core default font (I agree with the change it looks better), adjusted everything then ported to Core. My VB converter is a very large project and runs significantly faster under core, plus starts faster if I prebuild it (but some features that depend on accessing files break, likely my issue). I wanted to add some UI elements to specify some defaults and preserve compile time Constants plus allow setting of user defined constants but anything that touches Settings.Designer breaks my application at runtime and I get VS errors while modifying settings, also the runtime VB Setting savings on close don't work out of the box. I had to write my own MsgBox which I hosted on NuGet if anyone needs it, with source on GitHub and its close but not perfect due to lack of some functionality on Core.
    I have used TryConvert and it works reasonably well now on VB projects.
    Cory Smith
    @DualBrain
    Yeah, I'm definately experiencing the "rough around the edges" aspects; I just keep reminding myself that VB isn't officially supported at this point. ;-) (That doesn't mean that it doesn't/can't work, just that it's not super easy to make the transition at this early stage.)
    Also, what is the Core default font?
    As for MsgBox, I too was using that... switched to using MessageBox.Show to get around the issue.
    Cory Smith
    @DualBrain
    Answered my own question: Segoe UI 9pt
    It looks like the default behavior of the DataGridView regarding the column headers has changed. Actually setting it in Form.Load produces the same result in both projects: EnableHeadersVisualStyles = False (I want the column headers to be all the same color - not different based on the "column" that is currently selected as I am also doing fullrowselect.)
    Paul M Cohen
    @paul1956
    I use MsgBox way too often to change it. I ported the Open Source version of MsgBox and wrote all the tests to verify compatibility so it is a direct replacement. Even though the tests pass the semantics are not exact because VBHost is not implemented and I can't find its source. I hope someone is collecting all the behavior changes. I could not ever find out the new Font since I have not dealt with it since January.
    You can search for MsgBox on NuGet and you will get mine or the source is available on my GitHub page. I just updated it to 3.1 not that it matters.
    Jay Asbury
    @vbjay
    I stopped using msgbox years ago. Make the switch and it makes things a lot easier.
    Cory Smith
    @DualBrain
    @paul1956 I'll take a look at MsgBox... I value "muscle memory". ;-) Speaking of muscle memory, one of the annoyances with the "core" WinForms experience is that the toolbar item to "view code" is gone. You now have to either right click on the item and choose to view code or edit the form... or use keyboard to do so. However, when using the keyboard... I had it open the winforms designer in the .NET Framework version when highlighting the source file in the "core" version. If I unload the .NET Framework version, it seems to work as expected. So still very rough around the edges. ;-)
    @vbjay I ran an (unofficial) survey regarding the usage of MsgBox; as it turns out more than 2/3rds of the people that took the survey either use it as their primary and/or mixed. In other words, less than 1/3rd stated that they never use it in their WinForms development. So it being removed will potentially impact (good or bad) the majority of those who are developing in VB... that's a pretty big impact. We still haven't recovered from the last time things significantly changed in the spirit of "course correcting" existing VB behaviors back in 2001/2002. I'm not saying changes are bad, just that the problem isn't really all that simple (it's not binary).
    Paul M Cohen
    @paul1956
    @DualBrain Using MessageBox is a lot more complicated and does not give the exact same semantics, MsgBox is part of the VB language just like "End". The reason I have heard it is not included and from my experience, is there are/is missing API('s) needed to "fully" support it that don't layer well. My version would be a breaking change (not that I understand exactly what is broken) I think I has to do with Z-order between Forms and/or blocking execution and I think whatever it is doesn't effect my use.
    Paul M Cohen
    @paul1956
    I created #2501 against WinForms to ask that these changed to included in the Read Me for Core and VS
    Cory Smith
    @DualBrain
    @paul1956 Do you have a direct link to 2501? Clicking on it in here doesn't take us there. I'd love to take a look see.
    Paul M Cohen
    @paul1956
    Jay Asbury
    @vbjay
    I fully support MessageBox and its idea. Msgbox returns a Msgbox only enum result while MessageBox.Show returns a DialogResult that matches with all other common dialogs.
    Jay Asbury
    @vbjay

    Winforms: https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.dialogresult?view=netframework-4.8 Of course that matters if I am writing winforms or not.

    WPF: https://docs.microsoft.com/en-us/dotnet/api/system.windows.messageboxresult?view=netframework-4.8

    I use the one needed in the ui framework I am using.

    They made it so that all you have to remember MessageBox.Show in either ui framework.

    Paul M Cohen
    @paul1956
    there are other differences as I understand it having to do with z-order and/or relative position. That was one of the reasons MsgBox couldn’t be part of the initial core port. MsgBox depends on ParentWindow and (I)VBHost which i don’t believe is implemented yet.
    Paul M Cohen
    @paul1956
    It looks like WinForms Master now has MsgBox,InputBox, SaveSettings, logging and more VB stuff but I have no idea when that code will be shipping.
    Cory Smith
    @DualBrain
    @paul1956 SWEET!
    Cory Smith
    @DualBrain
    Who else here uses DevExpress?
    Jay Asbury
    @vbjay
    @DualBrain Me. But not in a long time.
    Paul M Cohen
    @paul1956
    I did but the last time was 2009.
    André Obelink
    @obelink
    I do, on a daily basis..
    Kathleen Dollard
    @KathleenDollard

    I am working in dailies to get the application model working. If anyone has been working on that, or is interested, let me know.

    My status, it requires some extra stuff in the project file, but when we got that straight, we found a bug on something missing in the runtime. That is in PR and should be in daily builds next week.

    Paul M Cohen
    @paul1956
    @KathleenDollard I am interested. Your comments are a little vague. If you mean SplashScreen, Single Instance and Title definitely. At first I liked the C# SplashScreen model but I noticed in broke older VB Framework code.
    Aaron Glover
    @aarondglover
    @DualBrain I use them and Infragistics
    Paul M Cohen
    @paul1956
    Has anyone seen Tests just stop running, and when you look in Output Window/Tests you see
    No test matches the given testcase filter `FullyQualifiedName=XUnitTestProject1.XUnitTestProject1.UnitTest1.AdditionTest|FullyQualifiedName=XUnitTestProject1.XUnitTestProject1.UnitTest1.EqualsTest|FullyQualifiedName=XUnitTestProject1.XUnitTestProject1.UnitTest1.MultiplicationTest|FullyQualifiedName...` in C:\Users\PaulM\Source\Repos\VBUncheckedMath\XUnitTestProject1\bin\Debug\netcoreapp3.1\XUnitTestProject1.dll
    Paul M Cohen
    @paul1956
    If anyone cares the issue above happens when a VB core app gets an error initializing before main starts and the framework code that catches those errors isn’t there do the app or test quietly exits.
    Paul M Cohen
    @paul1956
    Is anyone interested in a Vb code coverage UI based on Coverlet? I just finished something usable and will post to Github if anyone else cares. If there is enough interest I would like to merge into VS.