I want to manipulate docx files in wp7,c#. In windows I always use : http://docx.codeplex.com/ but it can't be added as a reference to a wp7 project.
Is there any control or alternative dll? Or is there any simple documentation about making doxc file? I read msdn documentation and I just got confused!
As far as I know there isn't a library for editing docx files for WP7 / Silverlight. However, the DocX library you link to is only dependant on the ./NET 4.0 framework. As DocX is most likely composed of non-UI code, there is a good chance that if you place the code into a WP7 Silverlight class library, you will be able to compile it.
Independentsoft has set of Office APIs compiled as Portable Class Library. It works on Silverlight, Windows Phone 7/8 and .NET Windows Store Apps.
Related
I'm looking for source code (as I bet a lot of others are / were and will) for learning purposes of DirectX. I would like something similar to the vs2013 Graphics Editor when dealing with *.fbx files, etc. Every thing I find is old and outdated, or way to simple and does not show the basics like transformation cursor, picking objects or points on objects. I'm just looking for something basic.
many thanks in advance
The DirectX Tool Kit is a good place to start and includes some tutorial content as well. It supports loading models using the VS 2013 content pipeline that produces CMOs from FBX files.
You didn't state if you were looking to write a Windows desktop application (aka a Win32 application) or if you were looking to write for Windows Store / Windows phone. DirectX Tool Kit supports either, although the tutorial is written using a Windows desktop application template so that developers using Windows 7 could also utilize it.
You should also refer to the DirectX SDK Samples Catalog for locations of updated versions of the legacy DirectX SDK samples that build fine using VS 2013 only.
I want to make a pdfreader with the native pdf reader in Windows 8 (consumerpreview version). I find a dll (Microsoft.LightSwitch.Design.Extensions.Reader) Is this the dll that I can use ?
It's not likely the pdf library is exposed in any way. An earlier question on MSDN forums suggested opening a pdf file with the default program associated with it like this:
Windows.Storage.StorageFile file =
await Windows.ApplicationModel.
Package.Current.InstalledLocation
.GetFileAsync(#"Images\test.pdf");
Windows.System.Launcher.LaunchDefaultProgramForFile(file);
Microsoft.LightSwitch.Design.Extensions.Reader is not native, it's a WinRT library, its PE header reveals its real identity.
You can use the freeware PDF Reader for Windows 8, or its DLL for your development.
http://www.pdfeight.com
Can I use "System.Windows.Controls" and "Microsoft.Xna.Framework.Graphics" assemblies in the same project without facing any problems from Microsoft Certification process.
Because it has been said that, "4.2.5:-The application must not call any APIs in the Microsoft.Xna.Framework.Game assembly or the Microsoft.Xna.Framework.Graphics assembly when using any methods from the System.Windows.Controls namespace."
No you can't .The requirements are explicit. Can you describe what kind of functionality are you looking for? Do you want to combine Silverlight and the XNA Framework in a Windows Phone Application? Do you want to use one of its types?
The Marketplace certification requirements are explicit - and they were correct for applications which target WP7.0. However they aren't accurate for WP7.1 "Mango" apps.
For WP7.1 it is possible to write a combined SL/XNA application. There is even a code sample for this on MSDN (see link).
I need to work with some bitmaps in managed code and save them as PNG files. Should I use Microsoft.WindowsAPICodePack.DirectX.WindowsImagingComponent, or System.Windows.Media.Imaging? They both seem very similar, and I'm not sure why I would choose one over the other. Can anybody compare and contrast them?
They both use WIC, that's why they are so similar. The Windows API Code pack is retired content, you'll want to use the WPF namespace since it is available on .NET 3 and up and doesn't require a separate install.
Microsoft.WindowsAPICodePack.DirectX.WindowsImagingComponent is in the Windows API Code Pack, which is a source code library that you would need to build into your application. On the other hand, System.Windows.Media.Imaging is included in the .NET Framework.
If you have no other use for the Windows API Code Pack, I would recommend using System.Windows.Media.Imaging. I believe the inclusion of a WIC API in the Windows API Code Pack is primarily for interoperability with the DirectX APIs in the Code Pack, which have no equivalents in the .NET Framework.
There has to be an easier way than to read the entire source code and check each line against what's compatible from the msdn docs
Suggestions?
I am assuming you mean from a Silverlight solution to a Windows Phone 7 solution? Anyhow, the answer is no - there is no simple / easy migration path. Simply copy the project files into a new WP7 project and start working through the compilation errors.
There is on tool that can help you creat portable code, the Portable Class Library which allows you to create assemblies which can be linked to Silverlight, WP7, WPF, XNA solutions. However, the code that you can shae is somewhat limited.