Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p><strong>Source Control:</strong></p> <p>Ben Straub said in a comment to this post: The <code>.dll.refresh</code> files should be added to the source control if required, while the <code>.xml</code>, <code>.pdb</code> and of course the <code>.dll</code> files should not be added.</p> <p>John Rudy explained when to add the <code>.refresh</code> file:</p> <blockquote> <p>Why is this a good thing (sometimes)? Let's say you're in a team environment. Someone checks in code for foo.dll, and your build system builds a new DLL, outputting it in a file share on a server. Your refresh file points to that server copy of the DLL. Next time you build, VS will auto-magically grab the latest and greatest copy of that DLL.</p> </blockquote> <p><strong>.xml</strong> like David Mohundro said:</p> <blockquote> <p>The xml file is there for XML comments and intellisense. Visual Studio will parse that and display the XML comments that were added when you call methods in those DLLs.</p> </blockquote> <p><strong>.pdb</strong> like David Mohundro said:</p> <blockquote> <p>The pdb is there for debugging and symbols. If you get an exception thrown from it, you'll be able to get stacktraces, etc. You're in control of choosing whether or not the PDB is built.</p> </blockquote> <p><strong>.refresh</strong> <a href="http://sanjaysainitech.blogspot.com/2007/11/what-are-dllrefresh-extension-files.html" rel="nofollow noreferrer">from a blog post about .refresh files:</a></p> <blockquote> <p>It tells VS where to look for updated versions of the dll with the same base name. They're text files, you can open them and see the path it's using.</p> <p>Their purpose is to prevent you from having to copy new versions yourself. In VS2003, the project file would contain the source location of the reference, but since VS2005 doesn't use project files for ASP.NET projects, this is the replacement for that particular functionality.</p> </blockquote>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload