求助：在C# UWP项目中导入.cs库以实现树莓派SPI连接RFID阅读器

Hey there! As someone who’s tinkered with UWP on Raspberry Pi for hardware projects before, let’s walk through getting that .cs library set up so you can talk to your RFID reader. I’ll break this down based on what kind of library file/project you’re working with:

Case 1: You have a single standalone .cs file #

• Right-click your UWP project in Visual Studio’s Solution Explorer → Hover over Add → Click Existing Item
• Navigate to where your .cs library file is saved, select it, and hit Add
• Once added, check the namespace at the top of the .cs file. If it doesn’t match your UWP project’s namespace, add a line like using [LibraryNamespace]; at the top of any code file where you need to use the library’s functionality.

Case 2: You have a separate class library project #

• First, add the library to your solution: Right-click your solution in Solution Explorer → Add → Existing Project → Find the library’s .csproj file and select it
• Next, link it to your UWP project: Right-click your UWP project → Add → Reference
• In the Reference Manager window, switch to the Projects tab, find the class library you just added, check the box next to it, and click OK

Critical UWP Permission Setup for SPI Access #

Don’t skip this—your app won’t be able to talk to the RFID reader without enabling the right hardware permissions:

• Open your Package.appxmanifest file
• Switch to the Capabilities tab
• Check the Serial Communication box (this covers SPI hardware access for Raspberry Pi)
• For more precise device targeting, you can add this XML snippet directly to the manifest’s code view:

  <DeviceCapability Name="spi">
    <Device Id="any">
      <Function Type="name:spiCommunication" />
    </Device>
  </DeviceCapability>
  

Quick Troubleshooting Tips #

• If you hit compilation errors after importing, confirm the library is UWP-compatible. UWP works best with .NET Standard 2.0+ libraries—if your library targets the old .NET Framework, you may need to recompile it as a .NET Standard project or find a UWP-friendly version.
• Double-check for namespace conflicts between your project and the library.
• Ensure the library’s SPI code uses UWP’s native Windows.Devices.Spi API—if it uses a different framework’s SPI methods, you’ll need to adjust those parts to fit UWP’s requirements.

内容的提问来源于stack exchange，提问作者Pierre