No suitable constructor found
Hans Karlsen (talk | contribs) No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Working with CodeDress and if you get this error "No suitable constructor found" check the following: | Working with CodeDress and if you get this error "No suitable constructor found" check the following: | ||
* In the GAC check that you only have the current Eco.Interfaces - and not any old copies of the assembly - and that the GACed version is the version in MDrivenServer/bin: C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Eco.Interfaces | |||
In the GAC check that you only have the current Eco.Interfaces - and not any old copies of the assembly - and that the GACed version is the version in MDrivenServer/bin: | * Also check the CodeDress assemblies (\ModelCodeAssemblies) so that you do not have any Eco.* assemblies there - the linker will wrongfully mix in these instead of the ones in your running application (Turnkey or MDrivenServer) | ||
* When the linker tries to resolve the reference to Eco.Interfaces - it may end up with the wrong one and then nothing matches up correctly and we have no access to the correct contstructor. | |||
C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Eco.Interfaces | * This issue does not normally arise on the server since you probably have not installed MDrivenFramework there. The problem arises due to a fight on what version to use between MDrivenFramework (that must GAC assemblies to allow for VisualStudio to work) and MDrivenServer that does not GAC assemblies. | ||
I Visual Studio doing "Clean" on your solution and rebuilding usually helps. | |||
Also check the CodeDress assemblies (\ModelCodeAssemblies) so that you do not have any Eco.* assemblies there - the linker will wrongfully mix in these instead of the ones in your running application (Turnkey or MDrivenServer) | |||
When the linker tries to resolve the reference to Eco.Interfaces - it may end up with the wrong one and then nothing matches up correctly and we have no access to the correct contstructor. | |||
This issue does not normally arise on the server since you probably have not installed MDrivenFramework there. The problem arises due to a fight on what version to use between MDrivenFramework (that must GAC assemblies to allow for VisualStudio to work) and MDrivenServer that does not GAC assemblies. | |||
Revision as of 13:07, 5 June 2019
Working with CodeDress and if you get this error "No suitable constructor found" check the following:
- In the GAC check that you only have the current Eco.Interfaces - and not any old copies of the assembly - and that the GACed version is the version in MDrivenServer/bin: C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Eco.Interfaces
- Also check the CodeDress assemblies (\ModelCodeAssemblies) so that you do not have any Eco.* assemblies there - the linker will wrongfully mix in these instead of the ones in your running application (Turnkey or MDrivenServer)
- When the linker tries to resolve the reference to Eco.Interfaces - it may end up with the wrong one and then nothing matches up correctly and we have no access to the correct contstructor.
- This issue does not normally arise on the server since you probably have not installed MDrivenFramework there. The problem arises due to a fight on what version to use between MDrivenFramework (that must GAC assemblies to allow for VisualStudio to work) and MDrivenServer that does not GAC assemblies.
I Visual Studio doing "Clean" on your solution and rebuilding usually helps.
This page was edited more than 11 months ago on 02/10/2024. What links here