Why can PresenterBinder.Factory only be assigned once?

[ThomasBarnekow]

@DavidRogersDev, thanks for providing this awesome library!

What is the reason for constraining the number of assignments to the PresenterBinder.Factory property? Looking at the code, I can't see a reason for this. Am I missing something?

I am asking because this required special attention in UI testing, which might not even be required if there is no reason for such a constraint (e.g., because it does not exist anymore).

[DavidRogersDev]

Hi @ThomasBarnekow ,

My apologies for the belated reply.

I think this is a carry over from the original project which I ported it from i.e. WebFormsMVP. I never envisaged having to set it more than once, but I cannot really see any harm in doing it. I guess if there IS a problem, I may be providing people with some rope to hang themselves with, but I think it is unlikely.

If this will make your life easier, I'm happy to make the change any publish a new Nuget package.

Please let me know.
Cheers

[ThomasBarnekow]

Thanks, @DavidRogersDev, for your reply. That change would be appreciated, if it does not create any problems for developers.

BTW, I have made changes to my own fork by targeting net472, because I would like to use your libraries from projects that must target .NET Framework. Would you be interested in a PR?

[DavidRogersDev]

Hi @ThomasBarnekow

I have made that change and uploaded Nuget packages. I still need to push the change. Creating the packages got messy. The Nuget team keep changing/deprecating things.

Also, were you aware that there is a .NET framework version of the library? https://github.com/DavidRogersDev/WinFormsMVP

I have not made the change over there yet, but can do so if you want to stay on a non-Core version of it.

Regards
David

[ThomasBarnekow]

Hi @DavidRogersDev, thanks for that.

I am aware of the .NET Framework version but actively wanted something that uses the SDK-style projects, which can be used when targeting .NET Framework, e.g., net472. Thus, in my case, I simply replaced your net50-related target with net472. That's it. If you wanted to offer NuGet packages built from this repo for use by projects that need to target .NET Framework, you could simply multi-target (e.g., net60 and net472). You could pick whatever .NET Framework versions you would like to support, not only net472, of course.

But please don't spend any time on this if you don't see value. I have what I need.