[Question] How to run 2.0.2.4 - x64 without error

[samkatakouzinos]

Describe the bug or Issue
Starting StaxRip from their unpacked locations gives an error of not finding the Versions.txt file under the Apps folder from where they run.

Step To Reproduce the Problem

1. Go to unpacked 'Staxrip.2.0.2.4.x64' folder
2. Go to either v4.7 / v4.8 folder.
3. Start StaxRip.exe
4. Main window opens.
5. Error message opens.

Screenshots
If possible, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows 10 Build 1809 17763.592
• StaxRip Version: 2.0.2.4 - x64
• Post your Logs, There Tell contain Allot of Information that Could Help.

Question
Am I meant to choose one version and copy the exe and config file to the folder above?

[stax76]

Thanks for the detailed report.

Am I meant to choose one version and copy the exe and config file to the folder above?

Yes

@Revan654

Maybe it's better if we use 4.8 in the next build.

[Revan654]

Yes, Pick you version and Then move it to base directory next to the App folder. if you have 4.8 installed use 4.8.

4.7.2 is the standard default now, However most PC's now use 4.8 as the default Framework. Even though that will be killed off early next year with Net5.

I wonder If We could just move the Code to .NetCore and do away with all Framework. .NetCore 3 is Suppose to be Faster 5x faster then Framework now.

[stax76]

@Revan654

I think this should be planned carefully, what if MS drops Win 7 support in .NET 5?

[Revan654]

this should be planned carefully, what if MS drops Win 7 support in .NET 5?

Windows 7 is already on life support. I doubt There going drop Win7 Support and go with One OS Setup for .Net5. That would be more .Net 6 or 7.

[stax76]

For now, we should stick to 4.8 I guess. I can't think of any real benefit in a port though. We don't have scaling issues, we don't have performance issues, there aren't any upcoming interesting language features or framework features. Using new tech is always exciting, I agree with that. If you want to do all the work I have no problem with a port but you should probably ask the users before.

[Revan654]

For now, we should stick to 4.8 I guess. I can't think of any real benefit in a port though. We don't have scaling issues, we don't have performance issues, there aren't any upcoming interesting language features or framework features. Using new tech is always exciting, I agree with that. If you want to do all the work I have no problem with a port but you should probably ask the users before.

Might be worth look at this: https://github.com/onovotny/MSBuildSdkExtras

I came across this the other day, I usually don't may much attention to the sdk code inside the project file. This allows multi target from .netcore to .netFramework 4.8.

FYI, might consider moving to reference package from normal package file. Since Package file setup is no longer under development and being dropped in future releases.

Makes everything very clean:

<Project Sdk="Microsoft.NET.Sdk.WindowsDesktop">
<PropertyGroup> WinExe
<TargetFramework>netcoreapp3.0</TargetFramework> ****
<UseWPF>true</UseWPF> 8.0
</PropertyGroup>
<PropertyGroup Condition="'$(Configuration)|$(Platform)'=='Debug|AnyCPU'"> DEBUG;TRACE
<PlatformTarget>x64</PlatformTarget> 1701;1702; NU1701
<OutputPath>bin\</OutputPath>

<PackageReference Include="DynamicData" Version="6.12.6" />
<PackageReference Include="MahApps.Metro.IconPacks" Version="3.0.0-alpha0188" />
<PackageReference Include="Microsoft.Data.Sqlite.Core" Version="3.0.0-preview6.19304.10" />
<PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite.Core" Version="3.0.0-preview6.19304.10" />
<PackageReference Include="System.Reactive" Version="4.2.0-preview.566" />

<ItemGroup>
<Folder Include="Data\" />
<Folder Include="Interface\" />
<Folder Include="Views\" />

[samkatakouzinos]

I'm happy for you to change the title to better reflect the direction of this issues conversation.