I need to create a DoubleUpperTriMatrix data structure in my app but I can't find where it is located so I can import the needed libraries. Using Google found that people include it via System.Object.CenterSpace.NMath.Matrix.DoubleUpperTriMatrix but it seems on Visual Studio 2010 it is not there anymore. How do I include it?
This component is not a part of Visual Studio, nor is it published by Microsoft. It is published by a 3rd-party called CenterSpace Software as part of their NMath package, which you will need to purchase.
Related
I am trying to import a dll into my Unity project. I have the dll copied into the Assets folder. When I try to "Add Reference" in Visual Studio, I keep getting this error.
Can anyone point to what issue may be causing this error? The dll in question is from the Native SDK for the Varjo headset. I am trying to import it so I can use the Native API from within my Unity project (requires functionality the Unity plugin does not provide).
Don't add the .dll to the references in visual project. Just drop it into your assets folder (better yet some subfolder).
To be able to use the relevant APIs from C# you will need to write a wrapper class similar to the one shown in this example:
https://docs.unity3d.com/Manual/NativePlugins.html
If you want you can give me a few examples of methods you want to call and I can show you how to expose them to c#.
What is the difference between a NuGet package, a Reference (is reference similar to a tool?), and a template in Visual Studio?
Why do we need them?
What is done / changed in our project when we install each one of them?
Are they dependent on each other in some way? Which one(s) of them are global installs, and which one(s) need to be installed in every project?
Before any comments or misunderstandings: this answer is NOT composed by me, but it was accepted as an answer here, so for the sake of the users trying to find an answer to this, I am literally Copying the answer to your question in this place.
What is the difference between a NuGet package, a Reference (is reference similar to a tool?), and a template in Visual Studio?
References are used to pull additional libraries into your project. For example, your colleague develop a library which implement some functions that you wanted. You needn't write it by yourself, just add the dll into your project through add reference. Of course you can add any libraries not it come from third part or from Microsoft. But it won't notice you when the libraries changed or updated.
NuGet package is the package manager for the Microsoft development platform including .NET. It will help you manage your packages which installed on your project. When the package has new version released, it will notice you to update it. The NuGet client is a tool provide the ability to produce and consume packages.
Template is similar to a sample project which provides the frameworks based on different type of project. You just need to add your content/functions into this frameworks to implement your requirement. For example, if create a WinForms project, it will reference System.Windows.Forms automatically which contains all stuffs you needed in WinForms project.
Why do we need them?
NuGet package and Reference can help us invoke some functions which have been implemented by others or some have been encapsulated by Microsoft. And the Template can help us create a project without build framework by our self. All of them help us save a lot of time when developing a project.
What is done / changed in our project when we install each one of them?
Add references in your project, it will let you invoke the functions in these references in your project.
Install NuGet packages will add the package reference into your project automatically and then you can use the functions the package provided.
The template will be installed when you install Visual Studio. Most of common templates will be installed. Then you can create a new project through these templates quickly.
Are they dependent on each other in some way? Which one(s) of them are global installs, and which one(s) need to be installed in every project?
Reference and NuGet packages need to referenced/installed on a project. But this project can be create through the templates or can be create by customer self. So in some way, reference and NuGet package are dependent on project.
Templates is global installs and NuGet packages and reference need to be install in every project.
I'm trying to make a very simple Xamarin.Forms test application to explore some features of the System.Data.SQLite package (namely encryption). However, I can't seem to get Visual Studio 2012 to add a reference to the package to the project.
Here are the steps I am taking:
Created a new Xamarin.Forms Portable blank app.
Right-click on TestApp (core project) and select Manage NuGet Packages
Search for "sqlite"
Install the "System.Data.SQLite (x86/x64)" package. (This package is version 1.0.97.0 and it is described as "the official SQLite database engine for both x86 and x64 along with the ADO.NET provider.")
According to NuGet, the package was successfully installed.
However, I cannot see the reference added under my project's "References" folder, and I also cannot write "using System.Data.SQLite" without errors ("cannot resolve symbol 'Data'"). Does anyone have any idea why this is happening?
On a side note, I can follow the exact same process described above except instead of creating a Xamarin.Forms Portable blank app, I choose a regular C# console app. This allows me to install the NuGet package fine and it shows up in references as expected.
Posting an update to share what I've learned.
So as Jason sort of alluded to in his answer, the reason I was not able to reference the package in my Xamarin.Forms project is because Xamarin.Forms is, by definition, a PCL project. It's meant to work on all platforms. The package I was referring to in my question is not a PCL, which means that anything in the package that is platform dependent is inaccessable (which is basically the entire package). The SQLite.Net-PCL package is basically the same thing as System.Data.SQLite, but in PCL form, which means it is compatible for use in a Xamarin.Forms project.
Following this logic, it makes sense that I was able to access System.Data.SQLite from a console project, since a console project is not a PCL project and it targets a specific platform.
For PCL projects, use SQLite.Net-PCL.
I've generated pseudo-localized versions of an app's resource files (for example Order Summary and Payment is localized as [[[[[Òŕd̂ër̊ S̀úm̂m̈år̀ý ân̈d̊ P̀áŷm̈e̊ǹt́]]]]]) so that we can test for localizability bugs ahead of getting actual translations.
I have named them using the qps-ploc resource identifier to match the existing pseudo-locale identifier, e.g. my pseudo-localized version of Details.resx is named Details.qps-ploc.resx.
However when I add these resx files to the project, Visual Studio ignores them. If I rename them using a "real" language code (such as Details.fr-FR.resx) then Visual Studio does create a subfolder named with this language code and builds the satellite assembly.
So it looks to me like Visual Studio rejects qps-ploc (without even a build warning). Am I missing something or can anyone suggest a way to get these qps-ploc resources built as part of my Visual Studio project?
The qps- locales work fine in my ASP.NET web application with .resx files (not compiled resource dll), however, I did find this MS article on enabling pseudo locales in the registry. Perhaps it will help.
Using Pseudo-Locales for Localization Testing
Additionally, you may wish to create custom locales, as given in this MS article:
How to: Create Custom Cultures
Best regards.
I've been following alone with this tutorial. Everything is going great, until I get to this part:
Set a reference to the StorageClient
library. You can either add the
sample project to the solution and add
a project reference or you can add a
reference to the compiled dll. I am
going to add the StorageClient project
to the solution and add a project
reference.
I am not able to find the StorageClient project. I have SDK v1.2, and it has samples-cs.zip. StorageClient is not there.
The SDK does have ref/Microsoft.WindowsAzure.StorageClient.dll. I tried adding a reference to it in my ASP project, but it's not working. VS does not recognize the type TableStorageEntity, nor the namespace Microsoft.Samples.ServiceHosting.StorageClient.
What am I doing wrong? Can I just find the StorageClient somewhere and use that? If it was taken out of the SDK, does it mean that it's not supported any more? If so, why have the DLL?
The problem is that the tutorial you're looking at is from mid-2009, when the storage client library was an add-on that was distributed as a sample with the SDK.
With the latest SDK (which I see you're using), the Azure storage support is now officially part of the SDK. The reference you're looking for is Microsoft.WindowsAzure.StorageClient.
Take a look at the Azure platform training kit - they should have updated samples.
Also: when you create a new cloud project with v1.2, you'll see that you automatically get references to the Azure dll's and don't need to manually add them. This includes:
Microsoft.WindowsAzure.Diagnostics
Microsoft.WindowsAzure.ServiceRuntime
Microsoft.WindowsAzure.StorageClient