I'm told that if you use the option Options.DisableSocForLiveDbs, SDK 10 will stop trying to load "linqbridge".
Licensing is pretty-well documented on the website. However trying to licence the components in a website is an ordeal because ASP .NET uses dynamic compilation and the licensing scheme works by embedding a resource into the assembly at compile-time.
Red Gate put up an article about creating a resource dll that you can build for ASP .NET in order to persist the activation, but it's not easy to understand.
http://documentation.red-gate.com/displ ... plications
I always recommend putting all of the SDK logic into its' own class library and sticking that in the website BIN folder so you can do the licensing in the officially-supported way and let the Microsoft Licence compiler create the resource automatically when it detects the licenses.licx file.
NB that you can't apply an evaluation licence to a web app because you always have to click OK on a nag requester of any app built with an evaluation version of the SDK.