Quantcast
Channel: Visual Studio and Visual Web Developer Express
Viewing all articles
Browse latest Browse all 3509

XML files and assemblies in bin directory

$
0
0

This post was placed in the Visual Studio General Questions forum but was move to off-topic because the moderators there don't want to answer the hard questions.  It has to do with the behavior of Visual Studio 2012 when it creates an Asp.Net project

  • In VS 2010 the bin directory was very simple and straight forward.
  • Now in VS 2012 Web apps the bin directory is filled with a bunch of System and Microsoft assemblies a bunch of folders named with the two letter country code use in URLs and a bunch of xml files with the name of the System and Microsoft assemblies. 
  • I can guess the reason for the assemblies is so that the web app can be deployed to servers without the .Net Framework installed or to which the installed app does not have access to the GAC.
  • But what is the reason for all of the xml files. Then to add insult to injury, even though the project is created with all of these xml files listed in the bin folder, each and everyone has a yellow triangle with an exclamation mark beside which I assume means that the file does not exist physically in the folder. When you go to windows explorer sure enough they aren't there.

What is the purpose of all of these xml files, and if they are needed then why aren't they physically added to the bin folder? I can not publish my project because the files do not exist. Can I delete these files with impunity?

Additionally when the output window opens in the IDE it opens at the top where the code windows are located. When a code file is double clicked in the Solution Explorer it opens at the bottom where the output window is supposed to be located.  This is very annoying requiring me to stop what I am try to do to properly position those windows manually.


Viewing all articles
Browse latest Browse all 3509

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>