I have just started with .net development. But while working with my first project for remoting I stucked on an error for an import present in my project.
using System.Runtime.Remoting.Channels
Gives an error showing 'The type or namespace name 'Channels' does not exist in the namespace 'System.Runtime.Remoting.' (are you missing an assembly reference?)'
And after searching a lot on web I got solution to add COM reference to the project with dll named System.Runtime.Remoting but on the pop of add reference I couldn't found the dll. Do I have to download the same or any other solution for that?
Related
I've created a reference in script to Universal.Microsoft.Bot.Connector.DirectLine in Visual Studio 2019 and everything looks fine but after I save and return to Unity, I get the following error:
error CS0246: The type or namespace name 'Universal' could not be found (are you missing a using directive or an assembly reference?)
I tried adding a reference to 'Universal' by Creating an Assembly Definition Reference asset, but did not see Universal on the list of references to add.
I'm wondering if what I'm trying to do is even possible in Unity.
You can find the package on Nuget, and grab the DLLs (and any DLLs it depends on) and put them into Assets/Plugins
https://www.nuget.org/packages/Microsoft.Bot.Connector/
if it has different folders/versions pick the Standard version
This is my first Unity project and since I know a bit about Watson, I thought I would start with that.
But when I create a new project and import the Watson Unity SDK assets into the Mono environment I get errors like :
Assets\unity-sdk-core-0.2.0\unity-sdk-core-0.2.0\Utilities\FrameRateCounter.cs(20,19): error CS0234: The type or namespace name 'UI' does not exist in the
namespace 'UnityEngine' (are you missing an assembly reference?)
When I create a new C# script in the scenes folder, the assembly reference for UnityEngine.UI can be found.
When I open the FrameRateCounter.cs file in Visual Studio, I don't get this message.
I am running version 2019.3.0a3 Personal of Unity
I have a project that references several other Projects in the solution. Project.Web references Project.Library; this reference has existed forever, but some changes have been made to Project.Library and now I'm getting the error "The type or namespace name 'Library' does not exist in the namespace 'Project' (are you missing an assembly reference?)"
I checked the target framework of all of my projects- Project.Web, Project.Library, RedirectModule, and SitecoreEloquaConnector - all of them are set to Target Framework = .NET Framework 4.5.2
I tried deleting the reference and readding it but I still get the error.
You should remove the references and add them manually.When you click add reference,choose browse and look for the library dll.After that rebuild solution,and it should work.
Whenever I take the latest code from TFS and tries to build existing solution, It fails all the project building and says that : The type or namespace name 'XYZ' does not exist in the sampace 'a.b.c' (are you missing an assembly reference?)
This is happening with all the references and only in my system. On the other systems all these code works fine.
Can it be a Visual Studio issue or some setting which might have got changed?
I have spent literally a 1 1/2 days Googling for a solution to this issue to no avail.
I am unable to reference a compiled SQLCLR assembly from code, in another project. I can add the reference to the other project, but when I try to add a "using" directive to include the referenced component in code, I receive a "The type or namespace name 'Database1' could not be found (are you missing a using directive or an assembly reference?)"
Here's what I've done:
Using VS 2012/2013 I have created a blank solution.
Added a new SQL Server Database project (Database1) targeting SQL Server 2012, and the .Net 4.5 Framework (NOT the Client Profile).
Added a new command line/winform/web app/whatever project (TestConsoleApplication1) to the solution, that ALSO targets the .Net 4.5 Framework (NOT the Client Profile).
Added references to the Database1 assembly (have tried project reference as well), and the System.Data assembly to the TestConsoleApplication1 project.
Added using directive for the System.Data assembly to the default class which was automatically added when I created the TestConsoleApplication1 project.
Attempted to add a using directive for the Database1 assembly to the default class which was automatically added when I created the TestConsoleApplication1 project.
When attempting to add the using directive for the Database1 assembly, the assembly name did not appear in intellisense, and typing in the assembly name resulted in the "red squiggle" under Database1.
Attempted to build the project, results in the "The type or namespace name 'Database1' could not be found (are you missing a using directive or an assembly reference?)" Error.
Checked, double, triple, quadruple...n-tuple-checked that both projects target the same .Net Framework version (4.5).
Database1 has no code, and here is the code for the "client" app (TestConsoleApplication1):
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;
using Database1; //Marked as design-time error, and throws ERROR on build
namespace TestConsoleApplication1
{
class Program
{
static void Main(string[] args)
{
}
}
}
Does anybody have any idea why I can add a reference to the SQLCLR assembly, but the "client" project code appears unable to actually "see" nor access the referenced assembly?
Your .net console project can not reference the .Net assembly that is within the SQLCLR project as it will be embedded in the database when you publish it. It does combile to a DLL but would be dependant on the Microsoft Sql Server libs and would normally run under the same connection context vs a defined connection string to talk back to the database. Both projects could reference a third, shared assembly, then add SQLCLR .net code directly in the database project that simply calls the shared code as a wrapper.