---
schema_version: "1"
id: fc2e7aec60c0631526d44360ee74b4dc831f36bc26ec115b8545d019f82fab5b
title: Microsoft .NET Connector 3.1
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/microsoft-dotnet-connector/latest/index.md
canonical_url: https://docs.mulesoft.com/microsoft-dotnet-connector/latest/
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 5b5fc6d8d046238a88b5b93918c839b6b91031c9d99019275c59fbe93e29f5b1
description: MuleSoft Documentation Site
release: "3.1"
latest: true
---
---
product: Microsoft .NET Connector
version: 3.1
is-latest-version: true
---

# Microsoft .NET Connector 3.1

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Microsoft .NET (Microsoft .NET Connector) enables you to execute native .NET
code in a Mule application. Microsoft .NET Connector has a dependency on the .NET CLR, which is
available only on Windows machines.

This connector executes .NET code using Java Native Interface (JNI), which provides fast
interprocess communication between Java Virtual Machine (JVM) and a native application that runs in
a host operating system.

The connector supports one operation, **Execute**, which enables users to select a class and method
to execute, and to pass the corresponding arguments for that method.

> [!NOTE] This connector supports standalone deployments only. This connector does not support
> CloudHub or Runtime Fabric deployments.

## Before You Begin

To use this connector, you must be familiar with:

- The .NET API

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- Creating a Mule app using Anypoint Studio or Anypoint Code Builder

Before creating an app, you must have access to:

- The .NET target resource

- Anypoint Studio or Anypoint Code Builder

## Common Use Cases for the Connector

Common use cases for this connector include:

- Executing code in an existing binary assembly (DLL) without modification

- Developing new .NET code that extends the capability of your integration application

For examples, see [Examples](https://docs.mulesoft.com/microsoft-dotnet-connector/latest/microsoft-dotnet-connector-examples).

## Audience

- New users, read:

  - [Using Anypoint Studio to Configure the Connector](https://docs.mulesoft.com/microsoft-dotnet-connector/latest/microsoft-dotnet-connector-studio) to create
    your Mule app

  - [Examples](https://docs.mulesoft.com/microsoft-dotnet-connector/latest/microsoft-dotnet-connector-examples), which provides one or more use cases for the
    connector

- Advanced users, read:

  - [XML and Maven Support](https://docs.mulesoft.com/microsoft-dotnet-connector/latest/microsoft-dotnet-connector-xml-maven)

  - [Examples](https://docs.mulesoft.com/microsoft-dotnet-connector/latest/microsoft-dotnet-connector-examples), which provides one or more use cases for the
    connector

## Next Step

After you complete the prerequisites and experiment with examples, you are ready to create your own
app and configure the connector using [Anypoint Studio](https://docs.mulesoft.com/microsoft-dotnet-connector/latest/microsoft-dotnet-connector-studio).

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Salesforce Help](https://help.salesforce.com)