Could Toolkit Namespace - C# - c#

I recently got to experimenting with the Cloud-Toolkit controls in my Applications i develop for customers, however adding the controls is easy(Simply add the dll) but when building the solution it seems i'm getting a stating i'm missing a namespace reference, what could it be ? The toolkit did not come with any instructions.
Thank you for your time.

Related

XAML C# + Unmanaged C++

I have a large amount of code in C++ (unmanaged), and I'd like to take advantage of the new fluent design features in the latest Windows 10 WPF/XAML. I found a very old sample for Windows 8.1 which shows a C# XAML page being driven by a C++ library, however, both of these are Universal Windows Platform (UWP) projects.
As far as I can tell it is not possible to reference a non-UWP library from a UWP project. The alternative, then, is to use the slightly older WPF components to host XAML controls using functions that allow you to load and render XAML pages (created in Blend, for example), but I've not been able to find a working example of this particular configuration.
Any thoughts or ideas about how to attack this issue will be appreciated, if any of you have figured out how to bridge C# WPF + XAML and unmanaged C++ projects, please let me know!

c# GDIPlus not found

Hello I am trying to develop an application using c# and I am using the System.Drawing DLL. However, I get an exception for when I run it pretty much saying the System.Drawing.GDIPlus DLL was not found when I am including the System.Drawing DLLin my build. Are there any ways to do this or am I hopeless and need to figure out a workaround.

Win8 Javascript Metro App, with C# WinRT Component and SQLite

I'm creating a Windows 8 Store App. The front-end (main project) of this app is in HTML5/Javascript. And I'm following this guide by Tim Heuer to create a C# WinRT component that wraps SQLite calls and behave as a controller. The front-end calls this component via Javascript, to update data, and get presentation content.
So there are 2 projects in my solution, 'main' in javascript, and 'db' in C#. I've managed to get SQLite working according to the guide. The reason I have this structure is that I'm trying to port an app from iOS to Win8. The 'controller' part is an isolated component from the get-go, and it's already ported to C#.
However, there is one caveat. Because of this known problem, I have to remove the reference to C++ Runtime v11 from the 'db' project to make it compilable. Though it runs fine in the development machine.
Then I got this test machine (samsung xe700t1a to be exact, Intel i5), I discovered that when 'debugging remote' on this test machine, Visual Studio won't deploy SQLite3. As a result, my SQLite calls fail with error: "Unable to load DLL 'sqlite3': The specified module could not be found. (Exception from HRESULT: 0x8007007E)".
According to the guide I mentioned previously, the point SQLite was made available via WinRT extension, is to make deployment automatic.
I'm wondering why this happens and how to make it correct? I'm also wondering if there's any certification problems for Windows Store for apps in this structure?
I also came across this post and this post suggesting that it's currently not possible to use SQLite in a WinRT component. But it's too late for me to change now, and this project won't be possible without a hybrid structure.
I found the solution. I used the hint from this post, and it's very straightforward.
What I have to do, is to create another project in the solution, with Output Type set to C# Class Library. Move the reference to SQLite for WinRT, and sqlite-net (nuget) wrapper to this new project. After that, I have to manually go through classes in sqlite-net, and change all the 'internal' classes to 'public'.
For the original controller project, I add using myclasslib; so that class definitions are found.
Apparently this workaround will work flawlessly. SQLite3 is deployed, and there's no warning against missing reference.

WPF and Windows Forms Mixed Environment Issue

I have a WPF dll with a user control. It works just fine when I use it in a WPF project as a reference.
I needed to test in a mixed environment. So I created a Windows Forms solution, added the reference to both the WPF dll and the WindowsFormsIntegration dll. I placed an ElementHost in the form.
In the code behind, I called using on the WPF user control namespace, created an object of the user control and assigned it as the child of the ElementHost. Till this point, intellisense also seemed to work fine. The moment I built the project, however, I got a build error saying that the WPF namespace that I had used was not found.
All dlls are built in .NET 3.5 and the client solution is also in .NET 3.5. Is this a known issue? What could be off with this scenario?
Can you please follow the following link to check whether you have referred all the dll's which is necessary to run WPF custom control in Winform
http://msdn.microsoft.com/en-us/library/ms742215.aspx.

System.Windows.Shell Reference missing

I have a windows form application and i want to make my own custom jumplist. To do this i need to use the namespace System.Windows.Shell but i can't access it, and i can't find a reference for it in the list of references either. I have checked some tutorials but they all use XAML (WPF Application) and some of them just mentions this can be done by coding as well.
So my question is, is it possible to access the namespace needed in a windows form app or do i need to use WPF? And if it is possible then how? And if not, then is there another way to do it in a windows form app?
I'm using Visual Studio 2010 Ultimate (C#).
Thanks in advance!
The System.Windows.Shell namespace is in the PresentationFramework.dll assembly. You can find that out on your own if you search for the namespace, the containing assembly will be displayed in the details.
An assembly reference to PresentationFramework is required. The namespace is only available in .NET 4. Use Project + Properties, verify the Target Framework setting. Using it in a Winforms app is fine, the classes don't require the WPF plumbing to work. They are wrappers for the Vista API extensions.

Categories