I am trying to using wordpress xml-rpc on windows phone 7 but can't find any API's for making rpc calls. Does anyone know of any libraries or a way to do it.
Try using XML-RPC.NET which is a free library. Once you download the bundle, there is a CF (Compact Framework) version of the DLL - due to platform restrictions, you have to use this version.
Note, however, that (quote from the documentation):
6.11 Does XML-RPC.NET work with .Net Compact Framework?
The XML-RPC.NET distribution contains
an assembly which provides support for
the .NET Compact Framework:
CookComputing.XmlRpc.CF.dll. Note that
this is an experimental version and is
mostly untested. Also, because the
Compact Framework does not support
reflection it is necessary to
implement XML-RPC.NET proxies manully.
The XML-RPC.NET library version 3.0 is now compatible with Windows Phone 7 projects.
I believe XmlRpcProxyGen doesn't exist in the Windows Phone library as the platform doesn't support the System.Reflection classes.
Related
I've created a Cross platform Application for Xamarin in Visual Studio. The application is running on .NET Standard 2.0 and it's not possible to select a higher version.
Isn't possible to run a Xamarin project on a newer .NET version? The problem is that a want to install nuget packages that requires at least .NET 4.5.
Thanks in advance.
You are confusing .net and .net standard. .net standard gathers many other .net platform (for example .net core, uwp, windows phone etc...) including the classical .net (from 4.5 to 4.6.1). Take a look at this table to have a better understanding.
This means that you should be able to include your library that targets .net 4.5.
Now that you know that, you can define a fallback version if the library does not target .net standard. To do so add this line in your .net standard .csproj in the PropertyGroup node
<PackageTargetFallback>$(PackageTargetFallback);portable-win+net45+wp8+win81+wpa8</PackageTargetFallback>
.NET Standard is a standard, official documentation is nicely covering it. Beside that must read, here is a compatibility table.
So please, read the official documentation. Setup your mind and come back with a proper question. Currently it does not make sense.
Good luck!
P.S.: Currently you are trying to use an outdated library that does not support .NET Standard, you might want to look for alternatives.
In Visual Studio for .net projects I can use built in tools to generate API clients by swagger. It simply and works great.
This option is missing from Windows Runtime projects as well, like Windows 10 IOT ones.
What is the best way to create API clients by swagger for this? If there is no built in tool / extension for VS, any external tools are highly appriciated.
Thanks a lot!
I don't get your question completely; on Windows IOT Core you can run UWP (background) apps; they are compatible with .net framework and .net standard up to version 1.4. This should work with a generated client from swagger.
Also you can use Refit to create a REST client according to best practices based upon an interface with attribute decorations.
we have developed a program on Motorola's EMDK 2.8 for .net for Motorola MC3090G and it worked just fine, but when running on MC3090Z it did not work and we wonder if the EMDK 2.8 for .net supports the MC3090Z RFID.
For the device MC3090Z, the only EMDK one can use is the 2.5 for .NET, from EMDK 2.6 and upwards only compatible with MC3190Z
Actually if you have your MC3090Z up to date with the correct .Net CF and OS, and current DLLs installed, then you'll be able to develop many type of software using any version of EMDK for .Net. But there are some specific APIs and DLLs depending on hardware requirements you won't be able to use. In order to help a little bit with documentation you may check these links out from official Motorola website:
a link to EMDK for .Net filtered search
Enter on current v2.5 and further versions and go to the Release Notes link on Public Software section. You'll notice in the table from Device Compatibility section the devices approved for each version which means best compatible rates between hardware and software.
I think you should know also the best way to test this is deploying directly to your Mobile device from Visual Studio IDE
Hope this may be usefull
I just started to study Nemerle. Since this is .NET language, I wonder, is possible to use for Windows Phone development? Does Visual Studio support it well?
Nemerle compiler uses System.Reflection.Emit for assembly manipulations. Then it can create assemblies same CLR version only.
I know only one reciepe for build WP assemblies: ildasm ncc.exe, fix all references to WP framework and ilasm it again.
This may not be possible, since Windows Phone runs a subset of the full .NET Framework which is closer to the .NET Compact Framework.
Looking at this page (translated from Russian) it looks like Compact Framework support is something that is/was planned for Nemerle version 2. However that article was written before Jetbrains acquired the project, so objectives may have changed.
Having said that, much more recently (Feb 2013) one of the Nemerle developers spoke about their difficulties in getting Nemerle to support other frameworks. So perhaps it is on their agenda after all.
I have a Windows Phone 7.1 project with a Portable Class Library targeted to SL4, .Net4.5, WP7.5, Store Apps, but this is not available: http://msdn.microsoft.com/en-us/library/dd642331.aspx
It says it should be available in .Net 4.5. Of course I can program it myself, but I prefer to use functionality provided by the framework.
If I change to Windows Phone 8 (and remove SL4) it is available. Any hacks possible to get it working targeting WP7.5 / SL4?
You'll need to implement it yourself for WP7.5 and SL4. However, you can make it so that on platforms that already support it (ie .NET 4.5, WP8, etc), it will use the in-box version (and thus you can share it with other libraries that use the "official" version.
Basically, create your implementation as a PCL that targets all the platforms you want. Then create another PCL targeting the platforms that do support System.Lazy. This second library should have the exact same assembly identity as the first one, but instead of having an implementation of the type, it should use the TypeForwardedToAttribute to forward to the existing version of the type.
Then PCLs targeting broader platforms can use the first assembly you created, while platform-specific projects or PCLs targeting narrower platforms can reference the second one. You can make it easy to reference the right version of the assembly from the right projects by packaging them up into a NuGet package.