jeme commented on issue #1041:
URL: https://github.com/apache/lucenenet/issues/1041#issuecomment-2518084671
> Okay, that is a bit puzzling.
>
> If you have a completely different API that is conditionally compiled for
`netstandard2.0` vs `net462`, that would certainly break if it were the case.
>
> ```cs
> public class SomeClass
> {
> #if NETSTANDARD2_0
> public static void SomeMethod()
> {
> }
> #else
> public static void SomeMethod2()
> {
> }
> #endif
> }
> ```
>
> If your `ClassLibrary1` project targeting `netstandard2.0` called a
multi-targeted assembly with this class in it, does your call to `SomeMethod()`
inside of `ClassLibrary1` break?
Yes, that was what I was refering to when I said you could certainly be
malicious here. It could also happen unintentionally.
But if you think about the intention of NET Standard, and stick with that
intention, the output targeting NET Standard SHOULD be the common subset that
is shared between you NET 8 and NET 462 output, it should not add ADDITIONAL
stuff.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
