When building controls and especially payment gateways and other exstensions are there any constraints on which version of the .Net framework I can target? I would obviously like to use the latest version possible but if uCommerce code is compiled against the .Net 2 CLR it won't work with a .Net 4 assembly will it?
Basically you're limited not by uCommerce but by the Framework version you choose for your assembly and app pool running the IIS site. For max compatibility build for CLR 2. For max feature build for CLR 4 knowing that you can run your assembly only under CLR 4.
I did a small pipeline task to see how a task built against Framework 4 would work out and there are no problems executing it as part of the pipeline system running under CLR 4.
Running that same assembly under CLR 2 won't work. If you want cross Framework compatibility you have to build your assembly to the lowest version of the framework you wish to support.
.Net framework version with uCommerce
When building controls and especially payment gateways and other exstensions are there any constraints on which version of the .Net framework I can target? I would obviously like to use the latest version possible but if uCommerce code is compiled against the .Net 2 CLR it won't work with a .Net 4 assembly will it?
Basically you're limited not by uCommerce but by the Framework version you choose for your assembly and app pool running the IIS site. For max compatibility build for CLR 2. For max feature build for CLR 4 knowing that you can run your assembly only under CLR 4.
I did a small pipeline task to see how a task built against Framework 4 would work out and there are no problems executing it as part of the pipeline system running under CLR 4.
Running that same assembly under CLR 2 won't work. If you want cross Framework compatibility you have to build your assembly to the lowest version of the framework you wish to support.
is working on a reply...