C# Corner

Related resources for .NET Client
  • Understanding SignalR From Scratch2/20/2017 9:20:58 AM. In this article, we are going to learn the fundamentals of SignalR and its client.
  • Creating And Calling A Web API From A .NET Client In ASP.NET Web API 27/11/2016 5:25:38 PM. In this article, you will learn how to create WEBAPI, and consume them to perform CRUD opperations in MVC Project.
  • How to update the properties of a website in the Sharepoint 2013 using CSOM4/21/2015 12:49:07 AM. In this blog you will see how to update the properties of a website in the Sharepoint 2013 .Net Client Side Object Model.
  • How to retrive the List templates are available in the Sharepoint 2013 using CSOM4/21/2015 12:35:42 AM. In this blog you will see how to to retrive the List templates are available in the Sharepoint 2013 .Net Client Side Object Model.
  • How to delete a website in Sharepoint 2013 using CSOM4/21/2015 12:14:35 AM. In this blog you will see how to delete a website Sharepoint 2013 .Net Client Side Object Model.
  • How to Add a User Custom Action for List Items4/20/2015 2:09:31 AM. In this blog you will see How to Add a user custom action for list items in SharePoint 2013 .Net Client Side Object Model.
  • .NET Client Profile4/14/2015 8:35:08 PM. This video will explain the purpose of .NET Client Profile.
  • Understanding Cross Language Interoperability With C# .NET11/27/2014 1:14:08 PM. This article explains case sensitivity/insensitivity of cross language interoperability in Microsoft .NET that allows compliant languages to interoperate with each other.
  • Understanding .NET Client Profile6/15/2014 1:36:10 PM. Lets understand the .NET Client Profile, which is supported by .NET Version 3.5, 4.0 and 4.5.
  • Cross Language Interoperability With C# .NET6/3/2014 12:10:48 AM. As you know Microsoft .NET is designed with cross language interoperability. I.e. two .NET compliant languages can interoperate with each other. Which simply means a function in VB .NET can be called by C# and vice-versa.
  • .NET Client Profile Vs. .NET Framework 1/30/2013 1:01:20 PM. This blog ost describes the purpose of NET Client Profile and .NET Framework.
  • COM Components from .NET Clients using VB.NET12/1/2012 2:08:08 AM. The .NET framework exposes COM objects through a proxy called the runtime callable wrapper (RCW). The primary function of RCW is to marshal call between a managed client (.Net) and unmanaged COM object. The runtime maintains a single RCW for each COM object.The example uses a COM component and DotNet client extending the functionality of the COM component using delegation.
  • Web Services between .NET, Java and MS SOAP Toolkit: Part I10/13/2012 5:17:18 AM. WinGhost 2.0 application allows you to show and hide applications running on your machine. I find this program useful at my work as I do lot of programming at any given time I can have a bunch windows open. I use it normally to hide just my windows I don't access that often.
  • Telnet client in Windows Vista7/2/2012 6:30:41 PM. Telnet client in Windows Vista
  • Web Services Between .NET, Java, and MS SOAP toolkit5/19/2012 6:45:26 AM. This article will try to explain the how you can build web services and/or clients with any of the three languages: .NET, MS SOAP Toolkit and Java. But the real point of the article is to show you how you can build clients for web services from any of above-mentioned languages.
  • Web Services for .NET and J2EE Interoperability1/30/2007 4:56:51 AM. Web services technologies are designed to support the interoperability between many different application development platforms that exist today. This article is focused on the fundamentals of .NET and Java interoperability using Web services technologies.
  • Using a COM Components from .NET Clients3/18/2006 4:22:51 AM. The .NET framework exposes COM objects through a proxy called the runtime callable wrapper (RCW). The primary function of RCW is to marshal call between a managed client (.Net) and unmanaged COM object. The runtime maintains a single RCW for each COM object.The example uses a COM component and DotNet client extending the functionality of the COM component using delegation.
  • Using a COM Components from .NET Clients3/18/2006 4:22:51 AM. The .NET framework exposes COM objects through a proxy called the runtime callable wrapper (RCW). The primary function of RCW is to marshal call between a managed client (.Net) and unmanaged COM object. The runtime maintains a single RCW for each COM object.The example uses a COM component and DotNet client extending the functionality of the COM component using delegation.
  • Web Services Between .NET, Java, and MS SOAP toolkit3/3/2006 12:41:58 AM. This article will try to explain the how you can build web services and/or clients with any of the three languages: .NET, MS SOAP Toolkit and Java. But the real point of the article is to show you how you can build clients for web services from any of above-mentioned languages.
  • Integrating .NET Web Services with Java and classic ASP Clients for Interoperability2/13/2006 11:02:47 PM. The goal of this article is to show to integrate Microsoft's .NET Platform Web service with other platform like Java and ASP. The samples demonstrate basic techniques and principles that are used to cross-platform interoperability via Web services.
  • Web Services between .NET, Java and MS SOAP Toolkit: Part I2/12/2006 11:02:42 PM. WinGhost 2.0 application allows you to show and hide applications running on your machine. I find this program useful at my work as I do lot of programming at any given time I can have a bunch windows open. I use it normally to hide just my windows I don't access that often.
  • .NET Framework and Web Services - Part 22/9/2006 12:48:50 AM. Here we are going to learn how to create a WebService using VS.NET (using VB.NET.) and consume the Webservice from VB.NET Client. This Article is based on VS.NET RC1 Release.
  • Accessing .NET Components from COM Clients and COM components from .NET Clients12/23/2005 1:20:59 AM. In this article I am going to explain how to access a .NET component from a COM client and accessing COM from .NET clients.