Try-before-you-buy - windows-phone-8.1

I want to submit an app I wrote to the Windows store. All the examples I have found about implementing trial functionality in an app, seem to be dated. For example, most tell you to add the using directive 'using Microsoft.Phone.MarketPlace; which causes Visual Studio 2013 to ask if I have forgotten an assembly reference. Am I supposed to add a NuGet package or something? Any help would be greatly appreciated.
using Microsoft.Phone.Marketplace;
Can anyone suggest a good, reliable, and current source of information?

It should be in the Microsoft.Phone assembly, Microsoft.Phone.dll.
It may be available as an assembly reference on your machine, I couldn't see it on nuget.org.
https://msdn.microsoft.com/en-us/library/windows/apps/microsoft.phone.marketplace.licenseinformation(v=vs.105).aspx

Related

How to use VBA-JSON in Visual Studio VBA application?

I am novice in VBA, but I never thought I will have a problem like that anyway. Well, the problem is next.
I need to parse json from api in my VBA app. I am trying to use VBA-JSON library (https://github.com/VBA-tools/VBA-JSON), cause I failed to find somewhere any other suitable solution for this task. The reason I have to write here about this, is that there are billions of guides how to install this library if you use Visual Basic in Excel, but no information how to do it if you use Visual Studio.
When following instructions I am trying to import this "JsonConverter.bas" into my project, I can do this, but it is not recognized correctly, as I can see.
Errors
There is written, that:
"Add Dictionary reference/class
For Windows-only, include a reference to "Microsoft Scripting Runtime"", and I added it in references.
Reference is added
Of course I get build errors when I am trying to run application.
So, could somebody tell me please, where is my mistake, and how to install this library?
Thank you in advance.

How to open this .net project with no errors

I have this project from github, database on sales and inventory system. But when I open it, it encounters errors.
I really need help on how to open this project with no errors? What should I do to fix this project?
PS: Need a step by step explanation regarding this, I just started databases, so I'm not sure what other tools I should be needing like MS Access or SQL.
The error is self-explanatory: underlined data types cannot be found.
That's means these types are defined in assemblies, currently not available to the compiler.
So in order to build the solution you need to supply these assemblies. There are multiple options, but I'd recommend doing this through NuGet as it is fully automated(you know about it, right?).
The missing assembly is related to the Microsoft.Reporting. So install this and try to build again.

How to install JSON for Visual Studio 2013?

I Installed the Nuget Package Installer thing, and it says it installed it.
However I can't find any references to JSON in Visual Studio.
I tried using System.JSON but I can't find it.
How can I use it?
Thanks
I have had been through the same trouble today, when I almost completed my Software Project and just had to use the File to use its contents to change the content of the Project.
For that I wanted to use JsonObject class to get the contents of the .json file. When I tried to write this
using System.Json;
It gave me the exact same error that you might have been going through. It asked for the Assembly files and DLLs.
I kept searching and I stumbled upon to this post, which was totally unhelpfull for me. So I searched and got what I was looking for. After that, I wanted to share that triumph with you people too so that next visitor must have an answer to his trouble on Stack Overflow.
Solution
What I did was, I went to the NuGet website for the System.Json extension package.
http://www.nuget.org/packages/System.Json
There, I capture the command for the installation.
I just click on the Tools --> NuGet package manager --> Package Manager Console and it gave me a new window in the bottom part of Visual Studio 2013.
There I typed (pasted) the link of command I copied. It started and installed the package for me. And now I can use it!
Further answer
I was told that it is a part of .NET v4.5, but I even have the v4.5.1 and still I don't get it why I don't have that package, maybe because on the Web page of the package it is shown deprecated. But still who ever needs it, can have the answer I have posted and it would help him out!
Good luck!
I think you can use the Newtonsoft JSON.NET package.
http://www.nuget.org/packages/newtonsoft.json/
I was also looking for a way to do JSON in C# and saw that they made it easier with .NET 4.5, couldn't do it and found this stack overflow question. I wasn't really satisfied with Afzaal Ahmad Zeeshan's answer so I kept searching and found this which I guess isn't depreciated and worked for me.
Steps in plain English (for .NET 4.5):
1.Add Reference to System.Runtime.Serialization
2.Add "using System.Runtime.Serialization.Json;" to your class
3.call "JsonReaderWriterFactory.CreateJsonReader()" or whatever methods you need to use to read/write json
Install latest VS 2017
Install-Package System.Runtime.Serialization.Json -Version 4.3.0
-- in PM console

Decompile WP8 assemblies

Anyone have clue, how to go about viewing the source from the Microsoft.Phone.dll [Windows Phone 8 ]. I tried this with the .Net reflector and JetBrains dot peek , Unfortunately it did not decompile the assembly. Any help much appreciated.?
You need a WP8 Phone dump and extract System.Windows.dll from WP8Dump\3\Windows\System32 . Load that file as assembly in .Net reflector and you are on the way.
The dump was online here xda developers, if you find a new one, please post it.
Have you tried Telerik JustDecompile? It is free to download here.
NOTE: I am answering to help you but I am not condoning anything you are trying to do with the DLL code. I am not sure what you want the code for or even if it is legal to decompile it.

How to sign a binary as part of post build step using sn.exe from Windows SDK?

I am a totally unfamiliar in this C# Visual Studio programming environment but I am required to finish a task.
I am sorry if my question seems silly. But I really could not understand what other posts on this site or other site on the net explaining. I need a step by step guide to do this final step to accomplish my task.
I have been given an application called MCC written using Visual Studio 2008. However, this application could not run properly in Window Vista due to the issue of DEP. MCC has a function to display video from an IP camera. This required the ActiveX control of AxGif89aLite. However, DEP in Vista is by default enabled. The flag IMAGE_DLLCHARACTERISTICS_NX_COMPAT in PE header do not allow this control to be used. Several tests have been run and identified this is the problem.
From an article online,
http://blog.dyadica.net/archives/data-execution-prevention-workaround, they suggest I need to add the below to MCC post build event.
call $(DevEnvDir).. \tools\vsvars32.bat
editbin.exe /NXCOMPAT:NO $(C:\Program Files\Aerocut\MCC\MCC2.exe)
So, I add this and rebuild the MCC solution file. Then, I cannot get what this last step required me to do.
Please note that if you sign the binary in Visual Studio, flipping the IMAGE_DLLCHARACTERISTICS_NX_COMPAT flag in the post build step after the binary has been signed will result in an assembly that will fail strong name validation. To work around this sign your binary as part of the post build steps.
To do this, use SN.EXE from the Windows SDK.
I am really confused what is this signing binary.
From information that I googled, signing an application is getting a certificate for the program so that it is more secured, am I right here?
I got the SN.EXE in my computer. But, how do I sign my binary as post build step? The binary should be my compiled execution file right?
I reinstalled the MCC with the rebuilt setup file. It still give me the following error:
Unable to get the window handler for the 'AxGif89aLite' control. Windowless ActiveX controls are not supported.
Help is very much appreciated. I would like to express thank you in advance here first.
If you're not signing the executable already as part of the compilation then you don't need to worry about it.