Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Cory Smith
    @DualBrain
    Would you mind putting together something; maybe in a README.md for the project that discusses how to setup the environment? Also, it appears that you should add a few more things to your project file for .NET Core 3... let me find a link.
    <Target Name="SetVBRuntimePath" AfterTargets="ResolveAssemblyReferences"> <PropertyGroup> <VBRuntime Condition="'%(ReferencePath.FileName)' == 'Microsoft.VisualBasic'">%(ReferencePath.Identity)</VBRuntime> </PropertyGroup> </Target>
    Well that didn't format like I'd expect...
    In .NET Core 3 Preview 6 this will enable the VB additions that have been done; so you don't have to do a lot of the workarounds you are having to do (hopefully). MsgBox is one that you still need a work around for.
    Cory Smith
    @DualBrain
    There is a problem where the one that is embedded is conflicting with the external reference... additionally, you can use the <MyType>Console</MyType> in the <PropertyGroup> section to enable "My". dotnet/sdk#3387
    Doing the Target name fixed an issue that I encountered related to END not providing an error in the IDE, but would not execute.
    Paul M Cohen
    @paul1956
    Interesting I have run the app with just the project changes and all tests pass. The references I am trying to resolve are internal to the application not the compilation. Not following the My issue I removed almost all of them.
    The project on Gitbub don't work on Core you are missing 2 projects and 5 project files
    Cory Smith
    @DualBrain
    I tried opening it up in VS 2019 (proper) and VS 2017 with similar errors.
    (With no changes made.)
    Paul M Cohen
    @paul1956
    I will look at that I have been working on Tuple support and may have pushed an unstable version. Sorry.
    It will not work on VS2017 it requires VB16
    Cory Smith
    @DualBrain
    I'm not seeing how I'm supposed to fix the CodeConverter > Dependencies > Assemblies > Microsoft.VisualBasic (which is the root of most of the errors).
    I saw that right away in VS17. ;-)
    Was just taking a guess and giving it a try.
    I'd love to experiment with your project and (most likely) contribute.
    (Which I guess I'm kind of doing now, even if it isn't from a "code" poing of view.)
    Paul M Cohen
    @paul1956
    image.png
    Don't know if that helps
    Cory Smith
    @DualBrain
    Almost identical to what I have, except I have a "yield sign" on the Microsoft.VisualBasic entry.
    image.png
    Paul M Cohen
    @paul1956
    I has frustrated with note being able to get a code fix VSIX working to fix up code after the port so I am adding an As Clause whenever possible and that has broken some code.
    I have seen that something I usually I just exit and reload and it goes away
    I know 0 about project file so I don't know what your recommendations do or where to put them but I will give them a try.
    Cory Smith
    @DualBrain

    OK... that is completely silly stupid (talking about VS).

    • Open project.
    • Click on first error.
    • CTRL period on error.

    Suggests to add a reference to Microsoft.VisualBasic

    Can't do that (errors out) since it already is referenced. Removed the reference. Repeated process.

    • Removed sign file.
    • Updated setting to reflect no longer signing.

    Compiles and runs in VS2019 Preview.

    Paul M Cohen
    @paul1956
    What I did was create a new project in Preview 6 for each or my Framework project of the same type and then just copy the file structure.
    Cory Smith
    @DualBrain
    image.png
    This is from another project... where I was playing with My, End, etc. Before adding the changes... wasn't working... after... magic.
    Paul M Cohen
    @paul1956
    I sign it because I use it a lot and didn't want to have to keep run under VS.
    Cory Smith
    @DualBrain
    I'm guessing there has to be some way to set things up so that you can sign it locally but not have that as part of what is in the github repo; however, I have no idea how that would be done (or if it is really possible - just guessing that it seems like it would be).
    Paul M Cohen
    @paul1956
    I can add that and see what happens maybe it will fix the few uses of #If
    I have see the issue on GitHub many times and I think they are working on a fix or have one.
    Cory Smith
    @DualBrain
    There's been a lot of progress with the runtime; so I'd definately give it a go. I'd also like to see what your doing with MsgBox; so I'll keep an eye out for when you update the repo. At this point, I now have a working local copy and can begin exploring.
    Paul M Cohen
    @paul1956
    Interesting that you need the "Magic" and I don't. You can select Convert/Folder and point at Roslyn and it will convert the whole thing to VB (it doesn't actually run because of Unsafe and a few other missing features in VB but you get very close) It will create a parallel directory called Roslyn.VB and not touch the original files.
    Paul M Cohen
    @paul1956
    Also I don't know how to create a project, I can convert all the files starting with the project but I don't know how to actually create the project file or find the references that would help with the conversion.
    Cory Smith
    @DualBrain
    For .NET Core 3 (especially during preview), you might want to take a look at dotnet/sdk#2793
    The "magic" is more about certain features not working as expected. End, Chr() as a constant value, My, etc. In other words, if you called the methods directly, everything is fine. It's more about what the compiler does with your code for optimizations and such that fail because there are effectively two different instances of the "runtime" in .NET Core 2+.
    Paul M Cohen
    @paul1956
    Ran into lots of runtime issues but not around the documented issues and more about assumptions I made in Framework that were not actually true.
    Paul M Cohen
    @paul1956
    BYW output folder is _vb not .VB
    Paul M Cohen
    @paul1956
    @DualBrain Adding the extra lines to the project file cause Error BC30002 Type 'Global.Microsoft.VisualBasic.MyServices.Internal.ContextValue' is not defined.
    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...