We need a payment gateway API that will run on NET4, similar to the SIM package offered by Authorize.Net (which only runs on NET3.5). It also needs to be PCI compliant. Other major components of the solution require NET4 to operate. Migrating the rest of the solution to NET3.5 is out of the question.
This is of immediate concern. Any advice is appreciated.
I’ve got lots of stuff that is targeting 4.0 with 3.5 or 2.0 dependencies. No reason why it shouldn’t work.
Hey wwb, thanks for responding. While their API assembly is callable with no issues, it seems to be their mvc helper extensions assembly that’s causing the problem. It’s compiled against mvc 2, not 3.
Gotcha, check out BindingRedirect, could fix it. Otherwise I’d just contact the vendor there, you are a paying customer, no?
My client is yes.
Well it’s not a DLL version issue, so much as it’s using features of HtmlHelper that had breaking changes between the two. I do not believe that simply redirecting the assembly bind will fix that.
I suppose I can see if they offer source for download and recode the HtmlHelper extensions and compile it myself. If not, I may have to resort to backporting to 3.5 and mvc 2. What a pain…
Update: I did it the manual way. I downloaded the source, set the target framework, update the System.Web.Mvc reference from 2 to 3, recompiled and used those binaries instead.