ModuleBuilder | PowerShell Module to help scripters write | Command Line Interface library

I am trying to make a compiler in F# using the API provided in System.Reflection.Emit. I am running into a problem when I try to create functions (delegates) for the types in the assembly that I am currently building. Example translating the following Java (a slightly modified version of Java) class:

As you can see in below screencast, manipulating the second input field in my form also changes the value of the first one. I've completely reproduced it on JSfiddle in an isolated environment to track down the bug but didn't find it.

Quick overview of my code base:

A functional component ModuleBuilder has an Array in its state called blocks and a renderFunction which renders for each element of blocks one instance of a subcomponent called ModuleElement.

The subcomponent ModuleElement displays an input form element. When I create n instances of the subcomponent and try to type something in the the form element of the second instance then the first one's value gets updated as well.

I was trying to migrate .Net Core console app and tests from 2.1 to 3.1 and got a problem in my tests. I was using Moq library and it was working fine. After migration i started to get A non-collectible assembly may not reference a collectible assembly when trying to access any mocked objects. I have reproduced same behavior in completely new project. I was not able to find any relevant information on this topic. I have tested it with both MSTest and Xunit. Is this a Moq library issue or .Net Core 3.1 should use different approach to such cases?

I tried and fail to adapt this code. This is dynamic class generator from assembly on C# language. I can't use DynamicObjects because RDLC report doesn't work with none class from System.Dynamic but work great with that class generated by assembly.

What I'm trying to do is to change the property definition from a private variable to a method get and set. Don't need to be a property if it work with two functions will be great.

The code below I have commented the part that I need to change.

To expand on the title, I'm using Reflection to generate a custom subclass that will eventually have an arbitrary number of string properties which they'll internally store in a dictionary. In this case I'm just using one. I've used Ildasm.exe to get the MSIL that I need for the My Set method works, as the debugger shows the value I'm assigning, but when I try to read it back I get an InvalidProgramException, "Common Language Runtime detected an invalid program." which points back to the get method. My get method model is:

I work for several days try to shadow base class's property and set the derived class property to protected using Reflection.Emit. When I create a derived class and set new to the base property, call GetProperties() it only show one property with the name and the derived class property is not public, but the dynamic type call GetProperties() show two properties with the same name appear(base property is public and dynamic type is not public). here is my code.

I come across HasThis and ExplicitThis calling conventions on .NET Framework reference source, and thus I begin to wonder:

• When are they set by compiler?
• Are there any examples using this combination of calling conventions (in "real world" managed program)?

MSDN has described them as:

ExplicitThis

Specifies that the signature is a function-pointer signature, representing a call to an instance or virtual method (not a static method). If ExplicitThis is set, HasThis must also be set. The first argument passed to the called method is still a this pointer, but the type of the first argument is now unknown. Therefore, a token that describes the type (or class) of the this pointer is explicitly stored into its metadata signature.

HasThis

Specifies an instance or virtual method (not a static method). At run-time, the called method is passed a pointer to the target object as its first argument (the this pointer). The signature stored in metadata does not include the type of this first argument, because the method is known and its owner class can be discovered from metadata.

Here is a sample program I wrote to generate a class and constructor using these bits set:

I created simple program, which dynamically generates GenericEmitExample1.dll assembly. Such assembly defines following type:

I am building a rule checking algorithm that using expression tree, for the type generated using reflection.emit namespace. For some reason i am not able to get it working.

Getting the exception "System.ArgumentException: 'Instance property 'Parameter1' is not defined for type 'System.Object''"

I did try creating dynamic type using expandoObject instead of reflection.emit , it did not work

I appreciate it if anybody can help me to solve the problem. Code sample is given.