How to use WASDK API outside of WASDK as a nuget package? #5197
-
|
I am trying to compile WASDK APIs outside of WASDK and use them in C# via projection. However I can't use the methods because I get an error that types don't exist Is this even possible? Or am I missing something? @DrusTheAxe @codendone
|
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 13 replies
-
|
IAsyncOperation is part of the general WinRT API. This would mean that you need the Windows SDK projection referenced. This should happen automatically if you set the TFM to a Windows 10 version.
Have you set the TFM? To clarify, this implicitly sets a reference to the Microsoft.Windows.SDK.NET.Ref package. |
Beta Was this translation helpful? Give feedback.
-
|
@DarranRowe Thank you very much, this was just what I needed. |
Beta Was this translation helpful? Give feedback.
-
|
@DarranRowe can you clone my repo and test it?
|
Beta Was this translation helpful? Give feedback.
-
|
No, I do not see the same error. Sometimes you have to just clean and rebuild everything because the C# project system just fails to notice these changes. This is the build output I get after doing things like adding CsWinRT to the main application. This is fixed changing the return type of myButton_Click from Task to void as is expected. |
Beta Was this translation helpful? Give feedback.
-
|
If you are still having problems now, depending on how confident you are about modifying files, may I suggest that you just delete the current projection project and then create a new one? This may sound a bit weird, but sometimes Visual Studio does things that are problematic and cause major issues. I had a look again at your project from the repository, and I get an almost constant error message:
What's more, Solution Explorer shows:
This means that the projection project is always being skipped. The application will never see the projection and therefore errors will occur. The issue here is that the .sln file contains entries for the projection project that don't exist. The solution contains specific platforms, but these don't exist for the project. This mismatch between configurations between the solution file and the project file was effectively disabling the projection from building. So if you don't have the confidence to manually edit the .sln file, just delete your projection project and then create a new one. The other issue your solution has is that in the WinUI 3 application, CsWinRT is being referenced as a transitive package. CsWinRT has to be a top level package for it to actually work.
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you @DarranRowe But when I use the pickers, I get the following error Do you also have this problem or do the pickers run without errors? |
Beta Was this translation helpful? Give feedback.
-
|
While the error itself isn't that great, have you set the file type filter? Since those pickers are modelling the WinRT pickers, then the file type filter must be set before you call PickSingleFileAsync. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @DarranRowe
and in visual studio there is some warning:
|
Beta Was this translation helpful? Give feedback.
-
|
All I can say is that I went the other route and had no issues. I edited the .sln file to remove the bad platform mappings. I also left the projection as AnyCPU. |
Beta Was this translation helpful? Give feedback.
-
But "outside of WASDK" do you mean you're trying to use WASDK APIs at build-time without the WinAppSDK nuget? Or that you're trying to use WASK APIs at run-time without WASDK's MSIX packages? Are you aware of WADSK's "Self-Contained" option? Or are you trying to directly use WASDK's files yourself w/o WASDK's MSIX packages and without WASDK's nuget and support for WASDK/SelfContained? |
Beta Was this translation helpful? Give feedback.
-
I want to compile some of the experimental APIs myself and use them as nuget packages in C# and C++. If I'm not mistaken, each of the APIs was created as a separate project. I mean, copy the code from one of these projects and paste it into a newly created project. (In this case i am trying to use Microsoft.Storage.Picker (which currently is in draft in pr)). I was able to compile the newly created project and the C++ example works fine. But the problem is using it in C#, which I haven't been able to implement yet. In wasdk projections i can see that you are refrencing |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
If you are still having problems now, depending on how confident you are about modifying files, may I suggest that you just delete the current projection project and then create a new one? This may sound a bit weird, but sometimes Visual Studio does things that are problematic and cause major issues.
I had a look again at your project from the repository, and I get an almost constant error message:
What's more, Solution Explorer shows:
This means that the projection project is always being skipped. The application will never see the projection and therefore errors will occur.
The issue here is that the .sln file contains entries for the projection project that don't exist.