blocks|key|1416791|text|在IIS中，为3个应用程序中的每个应用程序创建一个指向相同脚本文件夹的虚拟文件夹。然后，您只需要将它们保存在一个应用程序中。还有其他选择，但这实际上取决于您的应用程序的结构。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1416792|编辑|offset|length|style|BOLD|1416793|一个更可怕的想法是使用区域。在公共区域中，有一个脚本目录，并将脚本设置为要编译。然后你自己把他们从dll中救出来。如果您预见到公共区域稍后具有更多的功能，这可能是个好主意。|1416794|entityMap^0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

In IIS create a virtual folder pointing to the same scripts folder for each of the 3 applications. Then you'll only need to keep them in a single application. There are other alternatives, but it really depends on how your applications are structured. 

Edit

A scarier idea is to use Areas. In a common area have a scripts directory with the scripts set to be compiled. Then serve them up yourself by getting them out of the dll. This might be a good idea if you foresee the common Area having more functionality later.

blocks|key|3863768|text|默认情况下包含的大多数文件也可以通过各种CDN获得。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3863769|如果您没有添加您自己的自定义脚本，您甚至可能不需要脚本目录。|3863770|微软的CDN脚本：http://www.asp.net/ajaxlibrary/cdn.ashx|offset|length|3863771|entityMap|0|LINK|mutability|MUTABLE|url|http://www.asp.net/ajaxlibrary/cdn.ashx^0|0|0|9|13|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Most of the files that are included by default are also available via various CDN's.

If you're not adding your own custom scripts, you may not even need a scripts directory.

Microsoft's CDN for scripts: <a href="http://www.asp.net/ajaxlibrary/cdn.ashx" rel="nofollow">http://www.asp.net/ajaxlibrary/cdn.ashx</a>

blocks|key|3847126|text|以下是我的建议：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3847127|右键单击该解决方案并创建一个名为Common+Javascript+Files的新解决方案文件夹(或任何您想称之为它的内容)。|offset|length|style|CODE|3847128|​|3847129|📷|atomic|3847130|3847131|3847132|3847133|3847134|右键单击解决方案，单击Windows资源管理器中的“打开文件夹”，或手动导航到Visual的其他版本:(|3847135|3847136|3847137|3847138|在解决方案目录中，创建一个名称与解决方案文件夹相同的目录(解决方案文件夹通常与源代码级别的目录不匹配，但这将是明智的)。|3847139|3847140|3847141|3847142|在这个新目录中，添加需要在解决方案之间共享的文件。|3847143|3847144|3847145|3847146|在Visual中，单击“解决方案”文件夹并选择“添加现有项”。|3847147|3847148|3847149|3847150|在“文件选择”对话框中，导航到前面创建的目录，选择添加到目录中的文件并单击“添加”。|3847151|3847152|3847153|3847154|3847155|3847156|3847157|在每个需要共享文件的项目中，右键单击项目(或项目中的目录)，然后单击Add+-现有项。|3847158|3847159|3847160|3847161|导航到共享目录，选择文件并，单击下拉箭头，然后单击Add。|BOLD|3847162|3847163|3847164|3847165|现在，项目中的文件基本上是解决方案文件夹中文件的捷径。但是它们被视为项目中的实际文件(这包括.CS或Visual文件，它们将被编译为项目中实际存在的文件)。|3847166|3847167|3847168|3847169|专业人士|3847170|在设计时，只有每个项目所需的文件才能被添加，在controlled.|3847171|Editing+(虚拟目录等)|unordered-list-item|3847172|
|3847173|中并不需要任何配置，如果解决方案在TFS源代码控制中，您可以将目录添加到TFS源代码中，共享的文件将通过在项目中的选择成为源文件，将编辑实际的file.|3847174|3847175|Deleting链接文件不删除该文件。|3847176|
H+129这不限于JS文件，链接文件可以是您可能需要的任何文件(图片、Css、Xml、CS、CSHTML等)|3847177|CONS|3847178|3847179|每个部署都有自己的文件。当了解解决方案文件夹不是存在于解决方案目录中的目录时，|3847180|有一个小的学习曲线。|3847181|3847182|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/f422ceb44c2cd574f033240c76d68271.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/ab7a10b3d0ba2d5444f95893cbe68d79.png|2|https://developer.qcloudimg.com/http-save/yehe-900000/824c927e8603792cbebf8243ad21297d.png|3|https://developer.qcloudimg.com/http-save/yehe-900000/fb9387e18f14a5a4c36cba6cfee5f6d0.png|4|https://developer.qcloudimg.com/http-save/yehe-900000/7a9e48cc7c7b0fd53f4f03dee2134405.png|5|https://developer.qcloudimg.com/http-save/yehe-900000/b8a1f6eeb29e2efcfb8aaacb38041cf2.png|6|https://developer.qcloudimg.com/http-save/yehe-900000/1c657fad2448bfe382e0453a0b05c141.png|7|https://developer.qcloudimg.com/http-save/yehe-900000/8f70e8b4ece480f962ff41cdacc3961c.png|8|https://developer.qcloudimg.com/http-save/yehe-900000/8fad871d5076e6a38396fe5a44db5709.png|9|https://developer.qcloudimg.com/http-save/yehe-900000/2acb2b0ac49405d01c96aa011ae08a74.png|10|https://developer.qcloudimg.com/http-save/yehe-900000/6247f78c108f358f26f3e519aa1ed54f.png^0|0|G|N|0|0|0|1|0|0|0|0|0|1|1|0|0|0|0|0|1|2|0|0|0|0|0|1|3|0|0|0|0|0|1|4|0|0|0|0|0|1|5|0|0|0|0|0|1|6|0|0|0|0|1|7|0|0|0|0|0|1|8|0|0|D|7|0|0|0|1|9|0|0|0|0|0|1|A|0|0|0|4|0|0|0|0|0|0|0|1|5|0|0|4|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|3F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|3G|8|@$D|3H|E|3I|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|3J|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|3K|8|@]|9|@$D|3L|E|3M|1|3N]]|A|$]]|$1|M|3|I|5|6|7|3O|8|@]|9|@]|A|$]]|$1|N|3|I|5|6|7|3P|8|@]|9|@]|A|$]]|$1|O|3|K|5|L|7|3Q|8|@]|9|@$D|3R|E|3S|1|3T]]|A|$]]|$1|P|3|I|5|6|7|3U|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|3V|8|@]|9|@]|A|$]]|$1|S|3|I|5|6|7|3W|8|@]|9|@]|A|$]]|$1|T|3|K|5|L|7|3X|8|@]|9|@$D|3Y|E|3Z|1|40]]|A|$]]|$1|U|3|I|5|6|7|41|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|42|8|@]|9|@]|A|$]]|$1|X|3|I|5|6|7|43|8|@]|9|@]|A|$]]|$1|Y|3|K|5|L|7|44|8|@]|9|@$D|45|E|46|1|47]]|A|$]]|$1|Z|3|I|5|6|7|48|8|@]|9|@]|A|$]]|$1|10|3|11|5|6|7|49|8|@]|9|@]|A|$]]|$1|12|3|I|5|6|7|4A|8|@]|9|@]|A|$]]|$1|13|3|K|5|L|7|4B|8|@]|9|@$D|4C|E|4D|1|4E]]|A|$]]|$1|14|3|I|5|6|7|4F|8|@]|9|@]|A|$]]|$1|15|3|16|5|6|7|4G|8|@]|9|@]|A|$]]|$1|17|3|I|5|6|7|4H|8|@]|9|@]|A|$]]|$1|18|3|K|5|L|7|4I|8|@]|9|@$D|4J|E|4K|1|4L]]|A|$]]|$1|19|3|I|5|6|7|4M|8|@]|9|@]|A|$]]|$1|1A|3|1B|5|6|7|4N|8|@]|9|@]|A|$]]|$1|1C|3|I|5|6|7|4O|8|@]|9|@]|A|$]]|$1|1D|3|K|5|L|7|4P|8|@]|9|@$D|4Q|E|4R|1|4S]]|A|$]]|$1|1E|3|I|5|6|7|4T|8|@]|9|@]|A|$]]|$1|1F|3|I|5|6|7|4U|8|@]|9|@]|A|$]]|$1|1G|3|K|5|L|7|4V|8|@]|9|@$D|4W|E|4X|1|4Y]]|A|$]]|$1|1H|3|I|5|6|7|4Z|8|@]|9|@]|A|$]]|$1|1I|3|1J|5|6|7|50|8|@]|9|@]|A|$]]|$1|1K|3|I|5|6|7|51|8|@]|9|@]|A|$]]|$1|1L|3|K|5|L|7|52|8|@]|9|@$D|53|E|54|1|55]]|A|$]]|$1|1M|3|I|5|6|7|56|8|@]|9|@]|A|$]]|$1|1N|3|1O|5|6|7|57|8|@$D|58|E|59|F|1P]]|9|@]|A|$]]|$1|1Q|3|I|5|6|7|5A|8|@]|9|@]|A|$]]|$1|1R|3|K|5|L|7|5B|8|@]|9|@$D|5C|E|5D|1|5E]]|A|$]]|$1|1S|3|I|5|6|7|5F|8|@]|9|@]|A|$]]|$1|1T|3|1U|5|6|7|5G|8|@]|9|@]|A|$]]|$1|1V|3|I|5|6|7|5H|8|@]|9|@]|A|$]]|$1|1W|3|K|5|L|7|5I|8|@]|9|@$D|5J|E|5K|1|5L]]|A|$]]|$1|1X|3|I|5|6|7|5M|8|@]|9|@]|A|$]]|$1|1Y|3|1Z|5|6|7|5N|8|@$D|5O|E|5P|F|1P]]|9|@]|A|$]]|$1|20|3|21|5|6|7|5Q|8|@]|9|@]|A|$]]|$1|22|3|23|5|24|7|5R|8|@]|9|@]|A|$]]|$1|25|3|26|5|6|7|5S|8|@]|9|@]|A|$]]|$1|27|3|28|5|24|7|5T|8|@]|9|@]|A|$]]|$1|29|3|26|5|6|7|5U|8|@]|9|@]|A|$]]|$1|2A|3|2B|5|24|7|5V|8|@]|9|@]|A|$]]|$1|2C|3|2D|5|6|7|5W|8|@$D|5X|E|5Y|F|G]]|9|@]|A|$]]|$1|2E|3|2F|5|6|7|5Z|8|@$D|60|E|61|F|1P]]|9|@]|A|$]]|$1|2G|3|-4|5|6|7|62|8|@]|9|@]|A|$]]|$1|2H|3|2I|5|24|7|63|8|@]|9|@]|A|$]]|$1|2J|3|2K|5|24|7|64|8|@]|9|@]|A|$]]|$1|2L|3|-4|5|6|7|65|8|@]|9|@]|A|$]]|$1|2M|3|-4|5|6|7|66|8|@]|9|@]|A|$]]]|2N|$2O|$5|2P|2Q|2R|A|$2S|2T|2U|-4]]|2V|$5|2P|2Q|2R|A|$2S|2W|2U|-4]]|2X|$5|2P|2Q|2R|A|$2S|2Y|2U|-4]]|2Z|$5|2P|2Q|2R|A|$2S|30|2U|-4]]|31|$5|2P|2Q|2R|A|$2S|32|2U|-4]]|33|$5|2P|2Q|2R|A|$2S|34|2U|-4]]|35|$5|2P|2Q|2R|A|$2S|36|2U|-4]]|37|$5|2P|2Q|2R|A|$2S|38|2U|-4]]|39|$5|2P|2Q|2R|A|$2S|3A|2U|-4]]|3B|$5|2P|2Q|2R|A|$2S|3C|2U|-4]]|3D|$5|2P|2Q|2R|A|$2S|3E|2U|-4]]]]

Here is what I would recommend: 

Right click the solution and create a New Solution Folder called <code>Common Javascript Files</code> (or whatever you feel like calling it. 

<img src="https://i.stack.imgur.com/rxsnS.png" alt="New Solution Folder">

<img src="https://i.stack.imgur.com/RYtXw.png" alt="Common Javascript Files Solution Folder">

Right click on the Solution, click Open Folder in Windows Explorer,
or navigate there manually for other versions of Visual Studio :(

<img src="https://i.stack.imgur.com/wJomM.png" alt="Open Folder In Windows Explorer">

In the solution directory, create a directory with the same name as the solution folder (solution folders do not normally match directories at the source code level but this will for sanity sake). 

<img src="https://i.stack.imgur.com/MwdH1.png" alt="Common Javascript Files Directory">

In this new directory, add files that need to be shared between solutions. 

<img src="https://i.stack.imgur.com/C9SwU.png" alt="Add Javascript Files To Directory">

In Visual Studio, click the solution folder and select Add - Existing Item. 

<img src="https://i.stack.imgur.com/ktrb3.png" alt="Visual Studio Add - Existing Itme">

In the file selection dialog, navigate to the directory previous created, select the file(s) added to the directory and click Add. 

<img src="https://i.stack.imgur.com/hppca.png" alt="Select Files To Add">

<img src="https://i.stack.imgur.com/jbsZL.png" alt="Solution Folder Files">

In each Project that needs a shared file, right click on the project (or directory within the project) and click Add - Existing Item.

<img src="https://i.stack.imgur.com/SwMPt.png" alt="Project Add Existing Item">

Navigate to the shared Directory, Select the files and click the drop down arrow then click Add As Link.

<img src="https://i.stack.imgur.com/bI9zx.png" alt="Add As Link">

Now the files in the projects are essentially short cuts to the files in the Solution Folder. But they are treated as actual files in the project (this includes .CS or Visual Basic files, they will be compiled as files that actually exist in the project).

<img src="https://i.stack.imgur.com/rHucc.png" alt="Linked Files">

PROS

<ul>
<li>Files are truly shared across projects at Design time</li>
<li>Only the files needed for each project can be added, it's not all or nothing </li>
<li>Does not require any configuration in IIS (virtual directory etc)</li>
<li>If the solution is in TFS Source control, you can add the Directory to the TFS Source and the shared files will be source controlled.</li>
<li>Editing a file by selecting it in the Project, will edit the actual file.</li>
<li>Deleting a Linked file does not delete the file.</li>
<li>This is not limited to JS files, linked files can be ANY file you might need (Images, Css, Xml, CS, CSHTML, etc)</li>
</ul>

CONS

<ul>
<li>Each deployment gets it's own file.</li>
<li>There is a small learning curve when understanding that Solution Folders are not Directories that exist in a Solution Directory.</li>
</ul>

blocks|key|3864144|text|在这里，海事组织是最好和最简单的解决办法，我花了一周的时间试图找到最好和最简单的方法，但总是有更多的缺点而不是优点：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3864145|Resources(DLL)
++Shared
++++images
++++++image.png
++++css
++++++shared.css
++++scripts
++++++jquery.js


MvcApp1
++Images
++Content
++Shared+<-+We+want+to+get+files+from+above+dll+here
++...

MvcApp2
++Images
++Content
++Shared+<-+We+want+to+get+files+from+above+dll+here
++...|code-block|syntax|javascript|3864146|将以下内容添加到MvcApp1+->+Project+->+MvcApp1+Properties+->+Build+events+->+post+build事件中：|3864147|start+xcopy+"$(SolutionDir)Resources\Shared\*"+"$(SolutionDir)MvcApp1\Shared"+/r+/s+/i+/y|3864148|下面是关于它所做的事情的解释：Including+Build+action+content+files+directory+from+referenced+assembly+at+same+level+as+bin+directory|offset|length|3864149|对于MvcApp2也要这样做。现在，在每次构建之后，新的静态文件将被复制到您的应用程序中，您可以访问诸如"~/Shared/css/site.css“之类的文件。|3864150|如果您想要调整上面的命令，将脚本从.dll复制到每个应用程序的脚本文件夹中，那么就可以将一些脚本移动到.dll，而不必更改任何路径，下面是示例：|3864151|如果希望在每次构建后只将资源/共享/脚本中的脚本复制到MvcApp1+1/脚本中：|3864152|start+xcopy+"$(SolutionDir)Resources\Shared\Scripts\*"+"$(SolutionDir)MvcApp1\Scripts"+/r+/s+/i+/y|3864153|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/16761730/including-build-action-content-files-directory-from-referenced-assembly-at-same/16762763#16762763^0|0|0|0|0|F|2U|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|14|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|15|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|16|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|18|8|@]|9|@$M|19|N|1A|1|1B]]|A|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1E|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1F|8|@]|9|@]|A|$E|F]]|$1|W|3|-4|5|6|7|1G|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]]]

Here it goes, IMO the best and easiest solution, I spent a week trying to find best and easiest way which always had more cons than pros:

<pre><code>Resources(DLL)
 Shared
 images
 image.png
 css
 shared.css
 scripts
 jquery.js


MvcApp1
 Images
 Content
 Shared &lt;- We want to get files from above dll here
 ...

MvcApp2
 Images
 Content
 Shared &lt;- We want to get files from above dll here
 ...
</code></pre>

Add following to MvcApp1 -> Project -> MvcApp1 Properties -> Build events -> post build event:

<pre><code>start xcopy "$(SolutionDir)Resources\Shared\*" "$(SolutionDir)MvcApp1\Shared" /r /s /i /y
</code></pre>

Here is explanation on what it does: <a href="https://stackoverflow.com/questions/16761730/including-build-action-content-files-directory-from-referenced-assembly-at-same/16762763#16762763">Including Build action content files directory from referenced assembly at same level as bin directory</a>

Do the same for MvcApp2. Now after every build fresh static files will be copied to your app and you can access files like "~/Shared/css/site.css"

If you want you can adjust the above command to copy scripts from .dll to scripts folder of every app, that way you could move some scripts to .dll without having to change any paths,here is example:

If you want to copy only scripts from Resources/Shared/scripts into MvcApp1/scripts after each build:

<pre><code>start xcopy "$(SolutionDir)Resources\Shared\Scripts\*" "$(SolutionDir)MvcApp1\Scripts" /r /s /i /y
</code></pre>

blocks|key|1417051|text|最好的做法，海事组织，是你自己的CDN.基本上，只需在IIS中创建另一个站点并给它自己的绑定，例如"http://cdn.somedomain.com“|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1417052|然后将所有css/js/字体/共享图像等存储在CDN站点上，并从其他站点链接到它们。|1417053|这样做可以解决两个问题，|1417054|当需要的时候，您的所有内容都是共享的，您只需管理每个文件的一个版本。用户浏览器可以将其缓存在一个位置，而不是为每个使用|1417055|的站点下载它们的副本。|ordered-list-item|1417056|1417057|我添加这个答案是因为我看到很多人引用创建虚拟目录。虽然这确实是共享文件，但它为它们创建了多个下载路径，这是对带宽的极大浪费。为什么要让用户下载jquery.js+(1+*多个站点)，而您允许他们在cdn.somedomain.com上下载一次。|1417058|另外，当我说浪费带宽的时候，我说的不仅仅是服务器带宽，我指的是数据计划上的移动用户。例如，我前几天在我的手机上访问了我们公司的人力资源站点(insuance等)，它消耗了25+my的内存，下载了jquery和一些东西5次.在一个每月2gb的数据计划中，那些做这件事的网站真的让我很恼火。|1417059|entityMap|0|LINK|mutability|MUTABLE|url|http://cdn.somedomain.com/^0|1E|P|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|14|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|15|8|@]|9|@]|C|$]]|$1|J|3|K|5|L|7|16|8|@]|9|@]|C|$]]|$1|M|3|-4|5|6|7|17|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|18|8|@]|9|@]|C|$]]|$1|P|3|Q|5|6|7|19|8|@]|9|@]|C|$]]|$1|R|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]]|S|$T|$5|U|V|W|C|$X|Y]]]]

The best thing to do, imo, is to roll your own CDN... Basically just create another site in IIS and give it it's own binding, e.g. &quot;http://cdn.somedomain.com&quot;
Then store all of your css/js/fonts/shared images etc on the CDN site and link to them from your other sites.
Doing so solves 2 problems,
<ol>
<li>All of your stuff is shared when it needs to be and you only have to manage 1 revision per file.</li>
<li>Your users browsers can cache them in 1 single location instead of downloading copies of your stuff for every site that uses them..</li>
</ol>
I added this answer because I see a lot of people referrencing creating virtual directories. While that does indeed share the files, it creates multiple download paths for them which is an extreme waste of bandwidth. Why make your users download jquery.js (1 * number of sites) when you can allow them to download it once on (cdn.somedomain.com).
Also when I say waste of bandwidth, I'm not just talking about server bandwidth, I'm talking about mobile users on data plans... As an example, I hit our companies HR site (insuance etc) on my phone the other day and it consumed 25mb right out the gate, downloaded jquery and a bunch of stuff 5 times each... On a 2gb a month data plan, websites that do that really annoy me.

blocks|key|3864203|text|允许您调试脚本而无需重新编译项目的建议：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3864204|3864205|选择一个“主”项目(您将用于调试)，并向其添加物理文件--使用埃里克答复中描述的“additional”特性，将脚本文件添加到解决方案|unordered-list-item|offset|length|style|BOLD|3864206|使用CopyLinkedContentFiles任务的构建中，就像Mac的注释中建议的那样，将文件复制到其他项目H+210F+211|CODE|3864207|3864208|通过这种方式，您可以修改“主”项目中的脚本，而无需重新启动调试器，这对我来说有很大的不同。|3864209|entityMap^0|0|0|5|1|N|2|0|1K|A|0|0|D|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|T|8|@$F|U|G|V|H|I]|$F|W|G|X|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|Y|8|@$F|Z|G|10|H|L]]|9|@]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|12|8|@$F|13|G|14|H|I]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|Q|$]]

A suggestion that will allow you to debug your scripts without re-compiling the project: 

<ul>
<li>Pick one "master" project (which you will use for debugging) and add the physical files to it</li>
<li>Use "Add As Link" feature as described in Eric's answer to add the script files to the other projects in solution</li>
<li>Use CopyLinkedContentFiles task on Build, as suggested in Mac's comment to copy the files over to the second over to your additional projects</li>
</ul>

This way you can modify the scripts in the "master" project without restarting the debugger, which to me makes the world of difference.

blocks|key|1417072|text|这是一个迟来的答案，但微软增加了一个名为Shared+Project启动Visual+Studio+2013+Update+2的项目类型，它可以在不需要link文件的情况下完成您不想做的事情。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1417073|1417074|共享项目引用显示在解决方案资源管理器中的References节点下，但共享项目中的代码和资产被视为链接到主项目的文件。|blockquote|1417075|1417076|1417077|“在Visual的早期版本中，您可以通过添加->现有项，然后选择链接来在项目之间共享源代码。但这有点笨重，每个单独的源文件都必须单独选择。随着支持多个不同平台(iOS、Android等)，他们决定通过添加共享项目的概念，使项目之间更容易共享源代码。”|1417078|https://blogs.msdn.microsoft.com/somasegar/2014/04/02/visual-studio-2013-update-2-rc-windows-phone-8-1-tools-shared-projects-and-universal-windows-apps/|1417079|来自这个帖子的信息：|1417080|What+is+the+difference+between+a+Shared+Project+and+a+Class+Library+in+Visual+Studio+2015?|1417081|https://stackoverflow.com/a/30638495/3850405|1417082|entityMap|0|LINK|mutability|MUTABLE|url|1|https://stackoverflow.com/questions/30634753/what-is-the-difference-between-a-shared-project-and-a-class-library-in-visual-st|2^0|K|E|10|R|24|4|0|0|0|0|0|0|0|48|0|0|0|0|2I|1|0|0|18|2|0^^$0|@$1|2|3|4|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|1C|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|1D|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1G|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|1H|8|@]|D|@$9|1I|A|1J|1|1K]]|E|$]]|$1|P|3|Q|5|6|7|1L|8|@]|D|@]|E|$]]|$1|R|3|S|5|6|7|1M|8|@]|D|@$9|1N|A|1O|1|1P]]|E|$]]|$1|T|3|U|5|6|7|1Q|8|@]|D|@$9|1R|A|1S|1|1T]]|E|$]]|$1|V|3|-4|5|6|7|1U|8|@]|D|@]|E|$]]]|W|$X|$5|Y|Z|10|E|$11|O]]|12|$5|Y|Z|10|E|$11|13]]|14|$5|Y|Z|10|E|$11|U]]]]

This is a late answer but Microsoft has added a project type called <code>Shared Project</code> starting <code>Visual Studio 2013 Update 2</code> that can do exactly what you wan't without having to <code>link</code> files.

<blockquote>
 The shared project reference shows up under the References node in the
 Solution Explorer, but the code and assets in the shared project are
 treated as if they were files linked into the main project.
</blockquote>

"In previous versions of Visual Studio, you could share source code between projects by Add -> Existing Item and then choosing to Link. But this was kind of clunky and each separate source file had to be selected individually. With the move to supporting multiple disparate platforms (iOS, Android, etc), they decided to make it easier to share source between projects by adding the concept of Shared Projects."

<a href="https://blogs.msdn.microsoft.com/somasegar/2014/04/02/visual-studio-2013-update-2-rc-windows-phone-8-1-tools-shared-projects-and-universal-windows-apps/" rel="noreferrer">https://blogs.msdn.microsoft.com/somasegar/2014/04/02/visual-studio-2013-update-2-rc-windows-phone-8-1-tools-shared-projects-and-universal-windows-apps/</a>

Info from this thread:

<a href="https://stackoverflow.com/questions/30634753/what-is-the-difference-between-a-shared-project-and-a-class-library-in-visual-st">What is the difference between a Shared Project and a Class Library in Visual Studio 2015?</a>

<a href="https://stackoverflow.com/a/30638495/3850405">https://stackoverflow.com/a/30638495/3850405</a>

In case the question wasn't clear. I have 3 MVC projects in one Solution. Every time I create a new project it adds the "Scripts" folder with all the .js files I'll ever need. I don't want to have this created every time for every application. Is there a way to reference scripts from a central folder in the solution so all applications/projects can share one common script folder with all the scripts common among them?

Edit:
Please explain the pros and cons of doing this if there are any...now I'm curious.

How do you share scripts among multiple projects in one solution?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

万一问题还不清楚。我在一个解决方案中有3个MVC项目。每次我创建一个新项目时，它都会添加“脚本”文件夹，其中包含我所需要的所有.js文件。我不想每次都为每个应用程序创建这个程序。有没有一种方法可以从解决方案的中央文件夹引用脚本，以便所有应用程序/项目都可以与它们之间的所有脚本共享一个公共脚本文件夹？编辑：，如果有any...

问如何在一个解决方案中的多个项目之间共享脚本？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在一个解决方案中的多个项目之间共享脚本？EN