This is called mixed authentication mode. Basically you cannot achieve this within a single application because in IIS once you set up Windows authentication for a virtual directory it will no longer accept users from different domains. So basically you need to have two applications, the first with Windows Authentication and the second (the main … Read more
The best would probably be to recompile your class library for .NET 4.0 in Visual Studio 2010 (ie. opening up the project, converting it, and changing the target framework.) If you can’t, or won’t, do that, then you can try adding the following to your app.config file for your .NET 4.0 application: <startup useLegacyV2RuntimeActivationPolicy=”true”> <supportedRuntime … Read more
Well, no, it doesn’t get to be mix-mode until you tell the C++/CLI compiler that your legacy DLL was written in unmanaged code. Which should have been noticeable, you should have gotten linker errors from the unmanaged DLL exports. You need to use #pragma managed: #pragma managed(push, off) #include “oldskool.h” #pragma comment(lib, “oldskool.lib”) #pragma managed(pop) … Read more
After a bit of time (and more searching), I found this blog entry by Jomo Fisher. One of the recent problems we’ve seen is that, because of the support for side-by-side runtimes, .NET 4.0 has changed the way that it binds to older mixed-mode assemblies. These assemblies are, for example, those that are compiled from … Read more