We have added UNO in our existing project created in Visual studio 2019( using .NetStandard). we have set target and min version for UWP as per BugTracker sample project but we are getting below error while running the .wasm project.
Severity Code Description Project File Line Suppression State
Error NU1201 Project XXXXXX.UWP is not compatible with netstandard2.0 (.NETStandard,Version=v2.0). Project ImageViewerPOC.UWP supports: uap10.0.16299 (UAP,Version=v10.0.16299) XXXXXX.Wasm D:UnoXXXXXXX.WasmXXXXXX.Wasm.csproj 1
In order to use .NET Standard 2.0 in UWP, you need to target Fall Creators Update (FCU) as the minimum version of your UWP project. That’s because .NET Standard 2.0 contains many APIs that require FCU to make them work in the context of the UWP execution environment, specifically AppContainer.
Related
I have a full and perfectly working Azure Function within the Azure portale. One part of the function copies blobs from one azure storage container into another one.
I developed the application in VS 2017 and adjusted it within Azure Functions afterwards. In Azure Functions, I extracted my application as a VS 2017 project from Azure Functions in order to make & deploy changes quickly.
I added the current WindowsAzure.Storage 8.4.0 Nuget package to the VS 2017 solution but unfortunately VS Azure Functions does not recognize the package
, see:
I tried to add the Assembly manually but also in that case, I receive that message that the "reference is invalid or unspported".
Any suggestions ?
Binding redirect support hasn't been added to Azure Functions yet. You'll need to use a version 7.x Nuget package of WindowsAzure.Storage. If you are able to use version 7.2.1, you won't have any issue, as that's what Azure Functions is currently shipping with.
Github issue for: Binding redirect support
I am trying to deploy and test a Universal Windows App to a Surface Pro 3 directly from Visual Studio 2013 (Update 4) and I am unable to launch the App (by hitting F5). I am running into the following error and not able to find a fix to it. There are a bunch of solutions of DEP0700 errors online, but none of them work for the specific sub-error message Cannot map the serial well-known device name to a device interface GUID (blah blah blah)
Here is the error that I am seeing
Error : DEP0700 : Registration of the app failed. c:\Builds\TestAppRT\AppX\AppxManifest.xml(38,6): error 0x80070002:
Cannot map the serial well-known device name to a device interface GUID for the 11156705-8b60-4c7f-a75f-f8c7516401fc_1.0.0.0_neutral__1g7p71hbj7m7y package.
Check that the device name is correct. (0x80073cf6)
Have you declared any serial communication in your AppxManifest file?
If your other apps work, your issue might be because opening/editing ApxManifest file in the designer. Try making a new solution, and edit the manifest through only through XML Editor, if required & do not open with the designer.
Reference for more information:
http://ms-iot.github.io/content/en-US/win10/samples/SerialSample.htm
"Visual Studio 2015 has a known bug in the Manifest Designer (the visual editor for appxmanifest files) that affects the serialcommunication capability. If
your appxmanifest adds the serialcommunication capability, modifying your appxmanifest with the designer will corrupt your appxmanifest (the Device xml child will be lost). You can workaround this problem by hand editting the appxmanifest by right-clicking your appxmanifest and selecting View Code from the context menu."
I have created a windows phone Project that use HTML Agility Pack. I tried to reference to System.Xml.XPath.dll file but a error message say:
A reference to a higher version or incompatible assembly cannot be added to the project.
I'm using VS 2013 and Silverlight 5.
According to this, You need to use Silverlight v4 of the dll and not v5.
Can you please provide some guide how to create DriveQuickstart demo application (https://developers.google.com/drive/quickstart-android, steps 2-3) in Android Studio?
The problem is that Android Studio can't find com.google.api.* classes, like com.google.api.client.googleapis.extensions.android.gms.auth.GoogleAccountCredential. And I can't find it neither in google-play-services.jar, not in Android SDK folders.
I use "Compile with: Google APIs 17" in Android Studio, I downloaded all the latest updates in SDK manager (including Google APIs for API17, Google Play services, Google Repository).
According to http://developer.android.com/google/play-services/setup.html I added
dependencies {
compile 'com.android.support:appcompat-v7:+'
compile 'com.google.android.gms:play-services:4.1.+'
}
in build.gradle. What other actions should I perform to compile the sample source code, add some external library? You have provided great detailed steps for Eclipse, but said nothing about Android Studio with Gradle.
Try adding this to project build.gradel,worked for me in android studio 0.4.3,
sync and then optimize imports(Ctrl+Alt+O) in windows.
compile 'com.android.support:appcompat-v7:19.0.1'
compile 'com.google.android.gms:play-services:4.1.32'
compile('com.google.api-client:google-api-client-xml:1.17.0-rc') {
exclude group: 'com.google.android.google-play-services'
}
compile 'com.google.http-client:google-http-client-gson:1.17.0-rc'
compile('com.google.api-client:google-api-client-android:1.17.0-rc') {
exclude group: 'com.google.android.google-play-services'
}
compile 'com.google.apis:google-api-services-drive:v2-rev105-1.17.0-rc'
Credits go to user #smokybob
In the Quickstart, did you follow all of the items in Step 2?
Specifically it looks like you missed out the last two (confusingly numbered 1 & 2 which install the Google Client Libs into your project. Open the "libs" folder in your project and check that you have a bunch of client libs such as "googleapi-client.jar".
The question is how to resolve conflicts between versions of assemblies in my project that was upgraded to MVC4 and EF5?
The problem is manifest in the fact that my controllers and models can include System.Data.Objects, but now my views.
I am using MVC 4, my project was upgraded from MVC 3.
Entity Framework is version 5.
I have a controller that is able to use objectcontext from System.Data.Objects.
My Usings:
using System.Data.Objects;
using System.Data.Entity;
When I try to include the using in the view form System.Data.Objects, I get :
CS0234: The type or namespace name 'Objects' does not exist in the namespace 'System.Data' (are you missing an assembly reference?)
I am targeting .net 4.5
My Build Displays this message:
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets(1561,5): warning MSB3247: Found conflicts between different versions of the same dependent assembly.
You can build your solution in diagnostic mode to get more detailed information about the error.
Open the VS Options dialog (Tools > Options), navigate to the "Projects and Solutions" node and select "Build and Run". Change the MS Build project build output verbosity to Diagnostic.
Have a look here.
If you look at the build message, it states the 4.0 version of the .net framework is referenced... Is there a setting in your project file or web/app.config specifying a conflicting version of the .net framework?
Are you familiar with fuslog? you can set it up to log all assembly bindings that .net is doing while running your application. You should then be able to see detailed information on what is getting bound when. If you still can't figure it out, you can always do a binding redirect on that .dll in the web.config.
http://msdn.microsoft.com/en-us/library/eftw1fys.aspx -- binding redirects
http://msdn.microsoft.com/en-us/library/e74a18c4(v=vs.71).aspx -- fusion log viewer
Set up fusion logger and take a look at what the output is. If you don't get an answer from that, try the binding redirect (which would give you at least a temporary solution).
In the directory I was publishing to, there was a folder named aspnet_client. I moved it (instead of deleting it), republished, and it worked. I'm not sure why that folder decided to give me trouble out of the blue.