locked
[U8.1]Cannot resolve Assembly or Windows Metadata file 'SharpDX.Direct3D11.dll'

    Question

  • OS : Windows 10 build 10074 (installed kit platform version 10069) - IDE: using Visual Studio 2015 RC

    I have started getting the following error messages throughout all my solutions (error occurs 3 times).

    Error        Cannot resolve Assembly or Windows Metadata file 'SharpDX.Direct3D11.dll'    VPSample  G:\PRODUCTION\Projects\Samples\VPSample\VPSample.csproj

    I have a Universal application (Desktop) and a class library that targets Windows Universal (Windows 8.1). Even when i take all the references to the dll out of my executable, I still get the error messages. And in another solution, which i can confirm is building and running .. spits out the error messages as well! That should not happen, if there are error messages, it shouldn't build. But it does.

    Some other problems which may be related because they were not occurring previously ...

    Graphics diagnostics has stopped working. The diagnostics session runs. But when frame is captured and i look at the diag session, I see that something is wrong .. The captured frame is the wrong shape, it doesn't match the window. And when i open the frame, the graphics analyzer opens and the report shows:

         Playback failed...

    Also, the framerate is 30 instead of 60 (not really important at the moment). The graphics diagnostics not working is a big issue. If I can't debug the gpu pipeline then I'm going to have to switch back to Windows 8 for now.


    Edit: So i rebuilt the solution in Windows 8 and i still have the issue with the error messages. Except Graphics Diagnostics runs and after running it, the error messages go away.

    Edit2: And now, without doing anything I have another problem ...
    Visual Studio 2013 can't see a lot of classes, so MainPage and TimeSpan are cyan but nothing else is cyan in the MainPage.xaml.cs file. All class tokens such as RoutedEventArgs are white. And if I right click over ANY class 'Go to Definition is greyed out', 'Peek definition' only works for the two cyan classes MainPage & TimeSpan, it doesn't work for any other class in the file.

    I've seen this problem before and there is much talk about it if you go looking.

     Edit : Fixed this last problem with classes not being recognized by deleting the .suo file.

    Tuesday, May 12, 2015 11:46 PM

Answers

  • I think I have located the problem. Although my BlendStates collection was correctly set to internal, I had left my DepthStencil, Rasterizer and Sampler states as public classes. That would be the 3 references.

    My apologies, I completely panicked about those errors, and didn't think through the obvious problem.
    Thursday, May 14, 2015 8:24 AM

All replies

  • OS : Windows 10 build 10074 (dev version 10069) - IDE: using Visual Studio 2015 RC

    I have started getting the following error messages throughout all my solutions (error occurs 3 times).

    Error        Cannot resolve Assembly or Windows Metadata file 'SharpDX.Direct3D11.dll'    VPSample  G:\PRODUCTION\Projects\Samples\VPSample\VPSample.csproj

    I have a Universal application (Desktop) and a class library that targets Windows Universal (Windows 8.1). Even when i take all the references to the dll out of my executable, I still get the error messages. And in another solution, which i can confirm is building and running .. spits out the error messages as well! That should not happen, if there are error messages, it shouldn't build. But it does.

    Some other problems which may be related because they were not occurring previously ...

    Graphics diagnostics has stopped working. The diagnostics session runs. But when frame is captured and i look at the diag session, I see that something is wrong .. The captured frame is the wrong shape, it doesn't match the window. And when i open the frame, the graphics analyzer opens and the report shows:
     
         Playback failed...

    Also, the framerate is 30 instead of 60.
     

    • Merged by Kristin Xie Wednesday, May 13, 2015 5:09 AM the same issue
    Tuesday, May 12, 2015 8:28 AM
  • I suggest to move this post to Building Windows Store apps with C# or VB by the moderator.


    Fouad Roumieh

    Tuesday, May 12, 2015 5:01 PM
  • Ok, thanks.
    Tuesday, May 12, 2015 11:44 PM
  • Don't keep updating on your first post, because people subscribed doesn't get updates when you edit. So if you want to update just create it in a new post. I suggest to create a post about your current and latest issue you're facing.

    Fouad Roumieh

    Wednesday, May 13, 2015 6:30 AM
  • Hi Gavin,

    What's your issue now? As Fouad Roumieh suggested, because you have edited your original post many times, we can't get your latest status using e-mail notification, so please reply this thread directly.


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, May 13, 2015 8:09 AM
    Moderator
  • Ok, sorry for the updates. I'll change how i post issues. So I will stick to the one issue, that being .. I have 3 errors in my application that I can't pin down:

    Cannot resolve Assembly or Windows Metadata file 'SharpDX.Direct3D11.dll'    x3

    I thought it had gone away, but today I have them back again in the Win8.1 rebuild of the solution. So, I have

    GameEngine (Portable) project.

    CubeSampleApp (Windows 8.1) project

    The sample project references the GameEngine project. The GameEngine project uses SharpDX, but I have tried to internalize all sharpdx code.

    The only reasonable idea I have at the moment about what's wrong, is that somewhere in my GameEngine, is a class that is not being used but is within scope of used namespace. Resulting in an unresolved entry in the metadata, but not a compile error (because it's not actually being used). Maybe I have a method somewhere that exposes SharpDX.

    Thursday, May 14, 2015 7:52 AM
  • I think I have located the problem. Although my BlendStates collection was correctly set to internal, I had left my DepthStencil, Rasterizer and Sampler states as public classes. That would be the 3 references.

    My apologies, I completely panicked about those errors, and didn't think through the obvious problem.
    Thursday, May 14, 2015 8:24 AM