I am trying to use the CardBuilder.showStackIndicator(boolean) method, which was introduced in version XE22, but Android Studio tells me that the method can not be found.
I have the latest version installed from the SDK Manager and the latest software version installed on my Glass device. Is there something else that needs to be done to use this method?
This method should be in revision 11 of the GDK: make sure you've updated your add-on and refreshed your IDE.
If it doesn't show up in your IDE, try compiling anyway to make sure it's not a sync issue between autocomplete/autocompile and your SDK.
Related
I'm trying to build a simple object detection runner, really just following this MS Docs guide: https://learn.microsoft.com/en-us/windows/ai/windows-ml/tutorials/tensorflow-deploy-model
I already figured out building the View and adding capabilities so the provided code actually compiles.
Just one more problem right now: When creating the session, it crashes claiming "Unknown model file format version" which seems to translate to "Opset of the model you use is not supported".
Looking at github issues google showed me, I'm supposed to install the Microsoft.AI.MachineLearning nuget package and all is well. Except when I installed it, nothing changed.
So, what's left to do beside open yet another github issue? I already re-exported my model from opset 15 to opset 11 because the nuget package only supports that.
I'm on windows 10, UWP targeting 2004.
I created a sample application to open a webpage on microsoft edge, by following below URL guidance.
https://learn.microsoft.com/en-us/microsoft-edge/webview2/gettingstarted/win32
I installed packages using NuGet packet manager as instructed. Everything worked fine on development machine.
Then I copied the exe of my sample application and the library "WebView2Loader.dll" into testing machine, which has Microsoft edge Version 83.0.478.50 (Official build) (64-bit). I got "ERROR_FILE_NOT_FOUND" error, means "Either it failed find the edge installation or version is Not compatible with SDK version". This error is on call CreateCoreWebView2Environment(), which supposed to find browser.
I am trying to find out why it is not working when it has higher version of than minimum required version. As per documentation, minimum required version of edge is 82 I have 83.0.478.50.
Let me know what I am missing on test environment? should I set any environment variables? I tried find online if there any environment variables required, couldn't find any.
Edit:
The current version Microsoft.web.webview2 SDK is 0.9.488. The testing box has edge version 83.0.478.50. I understand that I need to update my edge version on Testing machine.
What version of the SDK package are you using?
The way to find out the minimum version of the browser for a given SDK package is to look at the build numbers. For example:
SDK version 0.9.538 requires Edge n.n.538.n+
More details can be found here:
https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/versioning
CreateCoreWebView2Environment or CreateCoreWebView2EnvironmentWithOptions returns 'FILE_NOT_FIND'?
You need webview2 runtime. You should download WebView2 Runtime installer (Preview) and then run it.
Separate webview2 runtime is not necessary if there is a fully functional Microsoft edge(Chromium). But the stable channel Microsoft edge(Chromium) is not supported by now, as the webview2 is in its preview stage.
I upgraded my azure function sdk from 1.0.14 to 1.0.28 and I get this build error:
The ExtensionsMetadataGenerator package was not imported correctly.
I can't find any documentation or ways to resolve it.
According to the 1.0.28 function sdk released several day ago, it may have some bugs in it.
Workaround:
Manually adding the
Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator nuget package to your project and it will work well.
I got this error when starting with the Visual Studio Function App template which uses Microsoft.NET.Sdk.Functions 1.0.31 and is a .NET Core 2.0 App.
Nuget Package Manager wants to update the Microsoft.NET.Sdk.Functions package to version 3.0.2 which it tries to do but the app is still .NET Core 2 and you get the error:
The ExtensionsMetadataGenerator package was not imported correctly.
To resolve this update the application to .NET Core 3:
Make sure you update your Microsoft.NET.Sdk.Functions NuGet package to the newest version that supports your app's version of .NET.
For example, I have a web app running .NET 2.1, I had to rollback the NuGet version to 1.0.36, and the next version (3.0) only worked on .NET 3 and up. After doing this, Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator NuGet was not needed at all and all my errors were gone.
I am working with microsoft.net.sdk.functions 1.0.38 and see the same message but in my case it is a build warning and not an error.
I installed the suggested NuGet package with the version required. However, I then received 3 warnings:
The ExtensionsMetadataGenerator package was not imported correctly. Are you missing 'C:\Users\me\.nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.2.0\build\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets' or 'C:\Users\me\.nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.2.0\build\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.props'? "C:\Users\me\.nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.2.0\build\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.props" cannot be imported again. It was already imported at "C:\Users\me\.nuget\packages\microsoft.net.sdk.functions\1.0.38\build\Microsoft.NET.Sdk.Functions.props (56,3)". This is most likely a build authoring error. This subsequent import will be ignored. [D:\myproject.Web\myproject.Web.AzureFunctions\myproject.Web.AzureFunctions.csproj] "C:\Users\me\.nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.2.0\build\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets" cannot be imported again. It was already imported at "C:\Users\me\.nuget\packages\microsoft.net.sdk.functions\1.0.38\build\Microsoft.NET.Sdk.Functions.targets (64,3)". This is most likely a build authoring error. This subsequent import will be ignored. [D:\myproject.Web\myproject.Web.AzureFunctions\myproject.Web.AzureFunctions.csproj]
Worse still my project would not build - it freezes on build with no way to cancel. The only way to cancel was to do, elevated PowerShell:
stop-process -name "dotnet"
To fix this I tried uninstalling the NuGet package but this is not enough as it still seems to be used if it is on the system (even though the project does not reference it?!?).
It is necessary to actually delete the package from package store, i.e. at.
C:\Users\me\.nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator
Or an alternative is to comment out the lines:
<GenerateFunctionsExtensionsMetadata SourcePath="$(_FunctionsExtensionsDir)" OutputPath="$(_FunctionsExtensionsDir)"/>
From:
C:\Users\me\.nuget\packages\microsoft.azure.webjobs.script.extensionsmetadatagenerator\1.2.0\build\Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets
I have no idea if this is safe to do so but it gets rid of the warning message. I instead opted to just delete the NuGet package and live with the original warning.
Looks like a real mess with microsoft.net.sdk.functions package.
cannot start .NET Core app because of this error:
"It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '2.0.7' was not found.
- Check application dependencies and target a framework version installed at:
\
- Alternatively, install the framework version '2.0.7'.
The program '[1560] dotnet.exe' has exited with code -2147450749 (0x80008083)."
Editing .csproj didn't help. It looks like this:
<PropertyGroup>
<TargetFramework>netcoreapp2.0</TargetFramework>
<RuntimeFrameworkVersion>2.0.7</RuntimeFrameworkVersion>
<DockerComposeProjectPath>..\docker-compose.dcproj</DockerComposeProjectPath>
<MvcRazorCompileOnPublish>false</MvcRazorCompileOnPublish>
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
You don't have the right .NET Core runtime installed. It's not good enough that's a .NET Core 2 runtime; it needs to be a minor version that is equal to or encompasses the version you're trying to target. You can see all the available runtimes here: https://www.microsoft.com/net/download/all. Specifically, you need 2.0 Runtime (v2.0.7) or higher. You can just choose 2.1, though. 2.0.7 will be rolled in and then, if you do end up upgrading your project later, you won't run into this issue again.
After playing around for a (longer) while, eventually it turned out that the solution is to comment out RuntimeFrameworkVersion in .csproj:
<PropertyGroup>
<TargetFramework>netcoreapp2.0</TargetFramework>
<!--<RuntimeFrameworkVersion>2.0.7</RuntimeFrameworkVersion>-->
<DockerComposeProjectPath>..\docker-compose.dcproj</DockerComposeProjectPath>
<MvcRazorCompileOnPublish>false</MvcRazorCompileOnPublish>
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
It is worth mentioning that the problem occured after my collegues upgraded a .NET Core to higher version and I did 'Get latest version'.
Following a Livecard tutorial, I realized that eclipse keeps throwing the following error: "import com.google.android.glass.timeline.TimelineManager cannot be resolved". The solution I found online was to set the project to compile with the Glass GDK by changing the build target to Glass Development Kit Sneak Peak version 15.
I dont have a Glass Development kit sneak peek under Android 4.0.3. I downloaded the ADT bundle from http://developer.android.com/sdk/index.html. However, I have a Glass Development kit preview under the android 4.2.2, version 19.
Could that be the problem as to why timelineManager is not being identified or imported?
I can't move forward until I figure this out.. =(
Here is a screenshot of the error: https://dl.dropboxusercontent.com/u/14109184/Screen%20Shot%202014-05-31%20at%209.42.38%20PM.png
Yes, TimelineManager was removed with XE16 with no immediate replacement. If you're planning on creating a GDK based app going forward - don't try to use the old GDK.
If you really need to insert a static card, you may wish to evaluate the Mirror API to see if it meets your needs.