Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating Rule “method-1-using-project-reference-assemblies-within-vsnet/rule” #8309

Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1,25 @@
---
type: rule
title: "Method #1 - Using Project Reference Assemblies within VS.NET"
uri: method-1-using-project-reference-assemblies-within-vsnet
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this rule 😅 @bradystroud?

@fenix2222 can we change the uri to be a bit smaller 🙏

authors:
- title: Adam Cogan
url: https://ssw.com.au/people/adam-cogan/
created: 2014-03-14T05:53:00.000Z
guid: 061c1865-2110-4f4a-bbac-37a5e0c361fd
---
The first attempt was the following method of adding project references to a large solution.

<!--endintro-->

![Figure: Adding a project reference](betterlargedotnet_projref.gif)

Each project within a solution references other product's assemblies by the project's GUID.

**Advantages**

The advantages of adding the project to the solution is that you can easily switch between debug and release versions, and the build time is quicker.

**Disadvantages**

The main disadvantage is that the project can only reference other projects within the same solution.
Loading