Re: .net and Direct X path
You have to add the references to your project before you can use them.
Just right click on the References in the Solution Explorer and then click Add.
Re: .net and Direct X path
Typically I will delete duplicate threads, but as both of them had replies, I've simply merged the two.
CodeMaker: Please do not double post.
Everyone else: If you spot duplicate posts and I'm not around, just send me a PM and I will take care of it. Thanks.
Re: .net and Direct X path
2. You have to specify that unsafe code is allowed in the project properties, which adds the "/unsafe" switch to the compiler commandline.
3. Whatever assembly that "Framework" namespace or type is defined in has not been added as a reference to your project. A project can't know about every assembly by default. It knows about a few common ones but anything else you have to tell it about, which means adding a reference to yuor project.
Re: .net and Direct X path
Where did this code come from that uses this "Framework" identifier? I think you'll find that the Microsoft.Build.Framework namespace is for the use of the IDE, presumably for building projects. I doubt that it's something that the casual developer should be messing with.
Re: .net and Direct X path
I am having the same problem, from the exact same MSDN article. Google isn't returning any results on this other than your question. I tend to believe that dxmutmisc.cs is apparently out-of-date with the current DX build and was overlooked by MS.
Re: .net and Direct X path
OK, I've learned that I need to include *all* of the sample Utility Toolkit framework files, or Samples\Managed\Common\dxmut*.cs. However, it only worked if I used the .NET v1.1 DX assemblies. Using the single .NET v2 assembly, I still get compiler errors.