---
title: "Strong name in .Net"  
description: "In shared system, the names of the assembly should be unique because the assemblies can be accessed by multiple applications. Therefore you need to as"  
author: "Anonymous User"  
published: 2012-09-11  
updated: 2014-09-18  
canonical: https://www.mindstick.com/blog/366/strong-name-in-dot-net  
category: ".net"  
tags: [".net"]  
reading_time: 1 minute  

---

# Strong name in .Net

In shared [system](https://www.mindstick.com/articles/23411/the-most-effective-method-to-find-the-perfect-small-business-phone-system-for-your-business), the names of the [assembly](https://www.mindstick.com/articles/25/global-assembly-cache) should be unique because the assemblies can be accessed by [multiple applications](https://answers.mindstick.com/qa/109321/what-to-do-if-my-computer-freezes-when-opening-multiple-applications). Therefore you need to assign a [strong name](https://www.mindstick.com/articles/440/what-is-strong-name-in-assembly) to assemblies before adding it to GAC.\

A strong name contains information about the assembly, such as its name, [version](https://www.mindstick.com/articles/12845/things-to-remember-while-migrating-odoo-to-a-better-version) number, and the public key of a public/[private](https://www.mindstick.com/blog/11097/java-access-modifiers-the-public-and-the-private-modifiers) key pair. It may or may not contain information about culture.

To sign an assembly with a strong name, you must have a public/ private key pair. If you do not have a key pair, generate it with the [strong naming](https://www.mindstick.com/interview/1178/what-is-strong-naming-signing-a-webpart-assembly-file-mean) [utility](https://www.mindstick.com/articles/12979/the-utility-of-accounting-tools-for-businesses-and-organizations), sn.exe.

---

Original Source: https://www.mindstick.com/blog/366/strong-name-in-dot-net

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.