Getting error
Error MSB3819 Cannot find assembly
"plugins\cordova-sqlite-storage\src\windows\SQLite3-Win-RT\SQLite3\SQLite3.UWP\release\SQLite3.UWP\SQLite3.UWP.dll",
which may contain managed resources that need to be included in this
app package. Please ensure that this assembly exists.
[platforms\windows\CordovaApp.Windows10.jsproj]
While building windows app for release using visual studio 2015
Although is it working fine for debug mode.
Related
I'm trying to publish my app on the Microsoft Store. When I run the Windows App Certification Kit I receive for each action an error related with Microsoft.Windows.SoftwareLogo.TestBase.
I'm using Visual Studio 2017 Version 15.9.3
Bytecode generation
Error Found: The bytecode generation test detected the following errors:
System.NullReferenceException: Object reference not set to an instance of an object. at Microsoft.Windows.SoftwareLogo.Tests.Utility.IsPackageWWA(AppXPackage package) at Microsoft.Windows.SoftwareLogo.Tests.BytecodeGenerationCheck.BytecodeGenerationCheck.ExecuteSharedValidation(String manifestFilePath, String packageFullName) at Microsoft.Windows.SoftwareLogo.TestBase.TestBase.ExecuteTest()
Impact if not fixed: As a performance optimization to accelerate JavaScript execution time, JavaScript files ending in the ".js" extension generate bytecode when the app is deployed. This optimization significantly improves start-up and ongoing execution times for JavaScript.
How to fix: You may need consider one or more of these steps to fix the issue:
- Avoid deploying the app by pressing F5 in Visual Studio, create an app package instead
- Ensure that event logging is enabled
- All JavaScript files are syntactically valid; otherwise exclude the respective files from the package
- Please note that you should uninstall all previous versions of the app before deploying
Otherwise exclude the respective files from the package.
I verified in my Visual Studio Installer and the Windows SDK in installed.
Also, I checked the targeting version of the project:
Target version: 1809 (10.0; Build 17763)
Min version: November Update (10.0; Build 10586)
There is not SDK for this build...
We are new to .Net Core and are trying to deploy our first application that uses it. We are deploying to a Windows server which has .NET Core Windows Server Hosting Module (2.2.0), the .NET Core Runtime (2.2.0) and I even installed the SDK (2.2.103) to see if that could solve the problem, which it did not.
Error:
An assembly specified in the application dependencies manifest (accesslog.deps.json) was not found:
package: 'System.Data.SqlClient', version: '4.5.1'
path: 'runtimes/win/lib/netcoreapp2.1/System.Data.SqlClient.dll'
So, here is my issue...the above error is being generated when we try to run a .NET Core application via the "dotnet filename.dll" method. We "publish" the application to generate all needed dependencies, or so I thought. The publish (and thus application) folder contain "A" version of this file (System.Data.SQlClient.dll), but apparently not the right one (version in publish path shows 4.6.26606.5), but yet that is the one being generated by Visual Studio.
Oddly, we also have an ASP.NET application on this same server which runs fine and references the same file.
Any help, guidance, troubleshooting steps, etc would be GREATLY appreciated.
I'm using Visual Studio to make an app. It works on Android and I'm trying to get it to work on iOS, but I need to resolve this unstable package in my dependencies.
Any advice about what I should do?
Error Message:
Package 'OxyPlot.Xamarin.Forms 1.1.0-unstable0011' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework'.NETStandard,Version=v2.0'. This package may not be fully compatible with your project.
That's a warning message, not an error message, and this is by design.
Please refer to https://learn.microsoft.com/en-us/nuget/reference/target-frameworks for target framework information.
.NET Standard 2.0 and .NET 4.6.1 have a huge surface area overlap.
For this Visual Studio and NuGet have added the concept of a fallback framework, where when a user tries to install a .NET Standard package in a .NET Framework project, it will allow the installation but warn the user that it's not 100% compatible and that there may be certain cases in which this does not work.
Related
https://github.com/NuGet/Home/issues/5192
https://github.com/NuGet/Home/wiki/Enable-.NET-Core-2.0-projects-to-work-with-.NET-Framework-4.6.1-compatible-packages
Trying to setup my build server for Xamarin Android builds, but i constantly keeps getting into this issue:
[error]C:\Program Files
(x86)\MSBuild\Xamarin\Android\Xamarin.Android.Common.targets(1832,3):
Error MSB6006: "aapt.exe" exited with code 255.
Anyone know what this error code means? We dont have this issue on the teams local computers. So i assume i am missing something on the build machine, but cannot figure out what.
Visual Studio Team Services Build Agent
MS 2012 R2 Datacenter
Visual Studio 2015 Community
Android SDK Manager w/all SDK's up til revision 24
Xamarin 6.1.1.0
There must be a problem in build tool. So, can you compare the installed build tool version in your local machine and build machine.
Note: Add the following line under PropertyGroup tag in your project file to specify the build tool version.
<AndroidSdkBuildToolsVersion>23.0.3</AndroidSdkBuildToolsVersion>
I believe you are probably missing some files in your SDK manager for android. Open the sdk manager and ensure you have downloaded all API levels you are targeting as well as the up to date build tools and extras.
I have a VC++ based application developed in VS2010 which uses some of the win32 component. I ported the code in VS2013 and I built the code after removing all compilation error in Release Mode. Now when I am trying to run the exe in Computer where VS2013 is installed it is working fine where as it is giving an error of mfc120.dll is missing where only VS2010 is installed. I don't think after building the code in Release mode I should get an error of missing dll. I have not tried to run the exe where no Visual Studio is installed.
If you are using the DLL version of the MFC you also need to install the corresponding VS-2013 runtime DLLs vsredist_x86
Or you switch to a complete static build.
I have found out the solution for this problem. Basically the win32 code I was building was using the Configuration Properties->General-> 'Use MFC in a Shared DLL' which I changed to 'Use MFC in a Shared DLL'. All working fine there after