Referencing ZXing.Net library - windows-phone-8

I need to reference the ZXing library to scan QR codes in my Windows Phone 8 app.
I have downloaded the ZXing.Net 0.10.0.0 from the following source: http://zxingnet.codeplex.com/
However, whenever i try to add a reference to zxing.wp8.0.dll, I get an error as follows:
A reference to higher version or incompatible assembly cannot be added
to the project.
Can I please know why am I getting this error. Is there anything that I am doing wrong or missing?

Right click on the DLL in File Explorer --> Click Properties --> Choose unblock. Then try to add a reference again.
VS2012 has the absolute worst error message for when DLLs are blocked due to the fact they were downloaded from the web.

Goto
http://nuget.org/packages/ZXing.Net
Follow the instructions to install the right version you need.

Related

Monodevelop fails to build, can't find Microsoft.DiaSymReader.Native.x86.dll'

I am trying to build a web api project using monodevelop on a mac. The thing is that after a few hiccups (explained in a question that turned out to be so messy I have just deleted) I get to the point of getting this error
/Users/myuser/git/LiveData/LiveData/CSC: Error CS0041: Unexpected error writing debug information -- 'Windows PDB writer is not available -- could not find Microsoft.DiaSymReader.Native.x86.dll' (CS0041) (LiveData)
In a windows machine the same project builds using visual studio targeting mono 4.5.
When I click on the error it tells me that /Users/myuser/git/LiveData/LiveData/CSC doesn't exist
Another thing is that in the folder structure of the solution there's a package folder (not the one inside the project) and inside this one I have a folder called Microsoft.Net.Compilers 1.3.2 that has inside another folder called "tools" that contains among other things csc.exe and the dll thta can't be found.
I have tried to install the dll directly in the project using nuget but even if it was installed the build showed me the same error
Thanks,
As for workaround for now you can just limit usage of Microsoft.Net.Compilers to Release configuration (edit *.csproj file):
<Import Project="..\packages\Microsoft.Net.Compilers.1.3.2\build\Microsoft.Net.Compilers.props" Condition="'$(Configuration)' == 'Release' And Exists('..\packages\Microsoft.Net.Compilers.1.3.2\build\Microsoft.Net.Compilers.props')" />
take a look at beginning of condition:
'$(Configuration)' == 'Release'
This way I can build and debug locally and build my project ie. in appharbor.
Building the project in release configuration should fix it!
This might not be completely related but may be helpful in some ways. Regarding the issue on 'could not find Microsoft.DiaSymReader.Native.x86.dll', have a look at this issue on GitHub: https://github.com/dotnet/cli/issues/3016
It seems like the solution is either:
Dependency to Microsoft.NETCore.Platforms needed for RID graph which
was missing. Any package which has transitive dependency on it (like
NETStandard.Library) could also make things work.
Adding dependency to "Microsoft.NETCore.Platforms": "1.0.1-" or
"NETStandard.Library":"1.5.0-" make it work.
adding Microsoft.NETCore.Platforms works as well

Error accessing WinRT sensors in C++ desktop application

I am trying to access the WinRT sensors from a Win32 desktop application using C++/CX as mentioned here: https://software.intel.com/en-us/articles/using-winrt-apis-from-desktop-applications
When I include the C++/CX header file it causes an error when building the Win32 project.
Exact error text: "error C1190: managed targeted code requires a '/clr' option."
Since I am not using /clr code at all, this is a confusing error.
Any suggestions? Please educate me if there is a better way to do this.
The error you are getting is because you are compiling some files without /ZW option for compiler. Since you are able compile at least some files with WinRT extensions, but not others, your project configuration is inconsistent.
The option /ZW (enable WinRT extensions) has to be configured on the level of project (and not on the level of individual files). There are two ways to ensure your settings are consistent. First method is through UI in Visual Studio -- you have to go through all platforms/configurations on the project and ensure /ZW is enabled, then got through all indivudual .cpp files, and ensure they don't override project level settings. This is tedious and error prone. The easier method is to open .vcxproj in notepad and do the following:
Add this section at the beginnig of the file, under root Project node:
<ItemDefinitionGroup>
<ClCompile>
<CompileAsWinRT>true</CompileAsWinRT>
</ClCompile>
</ItemDefinitionGroup>
Search and remove any other places where <CompileAsWinRT> is defined.

Error code 2001:There are duplicate files in AppManifest.xaml. Remove one of the files and then try again

I have made an app For Winodws Phone 8 platform and I am publishing it in Windows phone 8 store.All is well but at the end the error appears:
Error code 2001:There are duplicate files in AppManifest.xaml. Remove one of the files and then try again.
I have searched a lot on google, I have cleaned my solutions, rebuilt the solution, cross checked the manifest file but all in vain.
Goto ur_proj_folder/bin/release and open appmanifest.xaml in a notepad and check for repeated refrences of namespace :) Hope it helps
This usually happen if you have a duplicate reference to dependent dll. e.g. I have added reference of Advertising sdk of two different versions at one.
As Niwin said, the problem are the duplicated namespace's references in "Release/AppManifest.xaml", but the cause are the References added to the project, in my case when i added manually the "Microsoft Advertising SDK for Windows Phone 8.1 (Silverlight)" this dll started to conflict with "Microsoft.Advertising.Mobile.UI.dll", cause they have the same name. Just remove the reference and the problem will be gone.

Problems including comdef.h

I'm trying to port some existing code to WP8 and have come across a problem.
The code i am porting uses a smart pointer thats is defined in comdef.h but for some reason when I try and include comdef.h I get the following error.
comdef.h(25): fatal error C1083: Cannot open include file: 'olectl.h'
I understand what the error means and it seems there is no trace of "olectl.h" in the WP8 SDK include paths on my machine. Is anyone else having this problem, I've tried "repairing" my installation of "Visual studio 2012 Express for Windows Phone"
I have found some code that appears to include comdef.h and has gotten around the missing macro problem the link at the end of this post is talking about by not using the macro at all and explicitly using the code that the macro would expand to.
(Here is the code that does what I want to: https://devel.nuclex.org/framework/browser/graphics/Nuclex.Graphics.Native/trunk/Source/Rasterization/Direct3D11/Direct3D11Api.h?rev=1782)
Has anyone else experienced this, or could someone with the SDK installed try including comdef.h somewhere to see if it works for them.
The missing macro link:
http://connect.microsoft.com/VisualStudio/feedback/details/751127/com-smartptr-typedef-causes-errors-when-used-in-winrt-build
Thanks.
Yes, I see this too, so it appears this is "by-design".
Basically if the API isn't listed on MSDN in the list of supported COM/Win32 APIs, then it isn't a supported API on Windows Phone 8. It looks like only the combaseapi.h header is supported.
_com_ptr_t<T> and it's friends aren't on the list...

Manifest references file 'Bing.Maps.dll' which is not part of the payload

Error 1 Manifest references file 'Bing.Maps.dll' which is not part of the payload. C:\Users\xxx\Desktop\xxx\Applicationxx\Applicationxx\Package.appxmanifest Application7
I added this into a existing Metro application and its giving me that error, anyone has solution to it?
Go to the properties of the project and under Build, you will see Platform Target. Choose either x64 or x86 instead of Any CPU and it should be solved.
~Guo Hong
To correctly reference Bing Maps for a Metro app...
Go to: Project -> Add Reference -> Windows -> Extensions
Now, select both the "Bing Maps for ..." and also "Microsoft Visual C++ Runtime Package"
If you don't select the 2nd package, things will seem to be fine until you try to actually deploy your app.