MP1 vs 1.37 Visual Studio Version (2 Viewers)

[Anthony Vaughan]

Now that you are using .NET 4.7.2, over 4.0, in the upcoming release of MP1 vs 1.37, are you using VS 2022 to compile or are you sticking with 2019?

 

[ajs]

I use 2019

 

[Anthony Vaughan]

I use 2019

Yes. So do I.

I also have VS 2022 installed to handle my own development; mostly using WPF.

Ages ago I accidentally started MP1 by double-clicking the .sln file, which opened VS 2022, and it seemed to want to make loads of changes to infrastructure. It seemed to expect .NET framework later than 4.0 - I have no idea why. I've steered clear of using VS 2022 for MP1 since then.

So, I've been using a batch file that ensures MP1 is opened using VS 2019 ever since.

I think I'll try using VS 2022 to open the new version of MP1 to see whether I get the same response as last time. I'll let you know what happens.

 

[Anthony Vaughan]

I've just tried compiling vs 1.36 and 1.37 using VS 2022 and had no issues. I also tried opening 1.31 using VS 2022 without issues as well.

I can only think that in the early days of VS 2022 there were issues with projects only using 4.0 that no longer apply.

So, VS 2022 seems to work fine for MP1.

At least I don't have to maintain more than one version of VS any longer.

 

[Anthony Vaughan]

Talking about moving to .NET framework vs 4.7.2, I had an issue with EntityFramework after moving the projects to 4.7.2; EntityFramework still being at vs 4.0. As soon as I moved EntityFramework to 4.5 to issues went away. Bear in mind that I use EntityFramework for my refactored version.

This suggests to me that you may want to consider moving your packages, BASS.NET etc, to at least 4.5, though I notice that BASS.NET can go to net47.

Does that make sense?

 

[ajs]

I don't know .NET well, and I don't know how it is compatible across versions, upgrading to a higher version may break compatibility with current plugins, many of which are available as source code, others are not.
Although we already did something similar when upgrading to x64.
But overall it was not a bad idea to discuss it.

@Developers

 

[andy_p]

I hope you don't get stuck on the "old" entity framework. Switching to EF5 and .Net Core is quite a leap, but I doubt the old .Net framework will get much love from MS going forwards.

 

[ajs]

I hope you don't get stuck on the "old" entity framework.

We depend not only on plugins but also on the libraries used, not all of them are available in the new framework... Mediaportal without plugins is not a Mediaportal.
Well, we also lack developers who would understand more with C# and .NET.

 

[andy_p]

we also lack developers who would understand more with C# and .NET.

I had always said I wanted to contribute to more projects when I retired.
I've been retired for a year now and haven't really done anything useful yet - maybe this is my chance

 

[ajs]

maybe this is my chance

Perhaps, when there is desire and knowledge, you can always try.