We have integrated CM API DLL with our CMS through VS 2008 .net 3.5 successfully.
Now we are porting the entire solution (considerably huge) to VS 2010 .net 4.0 and so far we didn't face any incompatibilities but worry that there might be glitches we have missed out.
Are there any constraints to this porting? Are there any obsolete types and members.
Are there any compatibility issues with the dll considering x86, x64 porting?
You should not have any trouble at all using the dll in a 4.0 project - we intentionally made it really simple to avoid anything like this happening.
One thing to make sure of is that the project target framework is the full .NET Framework 4 and not just the client profile, as for whatever reason there are issues with using the referenced dll in that case.
Let us know if you have any other questions.
Currently we are using the provided dll in a .net 3.5 project. There we get a compiler warning as
"The predefined type 'System.Runtime.CompilerServices.ExtensionAttribute' is defined in multiple assemblies in the global alias; using definition from '<path>\createsend-dotnet.dll <project>"
This is due to ExtensionAttribute is defined in .net 3.5 framework. Is there a dll targeted for .net 3.5 or 4.0 or any other work around to get rid of the warning?
This issue has been fixed, as explained here.