See http://codebeat.wordpress.com/2008/06/23/almost-missed/

No more missings!

Take a look to this MSDN page! I already reported the “blah blah” placeholder.

MSDN Blah Blah Placeholder

Yesterday I faced an issue: I needed to host an .NET 3.5 application in a .NET 3.0 web server, because the .NET 3.5 web server wasn’t available at time. The application was built using Linq to Sql instead of “traditional” CRUD classes. So I had no choice, but make the app run.

Well, a workaround is to make a local copy of the referenced assemblies; in my case, System.Data.Linq.dll and System.Core.dll.

1. First, configure the target framework of the projects using Linq to .NET 3.0. The .NET 3.5 references will be removed.
2. Then, copy System.Data.Linq.dll and System.Core.dll in the solution, wherever you prefer (in my case, the root folder).
3. Add them as references in all the corresponding projects. Visual Studio will warn about the assemblies need a later version of the framework. Press Yes.
4. Set the SpecificVersion property of the references to true. This will prevent compiling errors.
5. Compile.
6. Run the app!

Download Example Code Using Sql Server Express

Download Example Code Using Just Linq

Microsoft.Office.Interop.Word.Document openDocument = wordApplication.Documents.Open(
    ref path,
    ref missing, ref missing, ref missing, ref missing,
    ref missing, ref missing, ref missing, ref missing,
    ref missing, ref missing, ref missing, ref missing,
    ref missing, ref missing, ref missing);

Expect more “dummy” members in future releases of the Microsoft Office Word 2007 PIA ApplicationClass! Is a shame they aren’t documented.