based on information of this site Core Discontinued
Reflection With the advent of .NET Native, we have a technology that allows us to statically link your application with the framework and third party dependencies. For the linking to be viable, it’s important that it can identify the parts of the framework that you’re not using. In other technologies, such as C++, this is somewhat straightforward as these systems don’t have dynamisms such as reflection. Of course, .NET Native still supports reflection but we wanted to make the platform more pay-for-play friendly, meaning that you don’t have to pay for features that you don’t use. This is especially true for reflection, as it imposes significant constraints on what the runtime and compilers can do based on static information.
two questions :
1) What is Advantages, disadvantages and differences of Reflection in .NET Core than .NET Framework ?
2) Based on above text Microsoft point to .NET Native, so Is this an new alternative of Reflection (Meta programming) in .NET Core or not ?
Aucun commentaire:
Enregistrer un commentaire