<div>
kaufmed,<br />
<br />
I've done my share of debugging on the production server. &nbsp;How does the PDB file relate to debugging?<br />
<br />
J &nbsp;
</div>


<div>
kaufmed,<br />
<br />
Sorry for the slow response. &nbsp;Thanks for the terrific response and follow up.
</div>


<div>
<div class="content wysiwyg-content">
I created an ASP.NET project, ProjectX. &nbsp;I ran a build and dropped the build files onto the production web server. &nbsp;<br />
<br />
I then modified some of the code under one of the ASPX pages, copied the modified ProjectX.dll from my development machine, and pasted it to the production server, overwriting the earlier copy. &nbsp;<br />
<br />
Here's the question, should I copy and paste ProjectX.pdb and ProjectX.xml to the production server as well?<br />
<br />
If yes, why?<br />
<br />
If no, why?
</div>
</div>


I created an ASP.NET project, ProjectX.  I ran a build and dropped the build files onto the production web server.  

I then modified some of the code under one of the ASPX pages, copied the modified ProjectX.dll from my development machine, and pasted it to the production server, overwriting the earlier copy.  

Here's the question, should I copy and paste ProjectX.pdb and ProjectX.xml to the production server as well?

If yes, why?

If no, why?

kaufmed,

I&amp;#39;ve done my share of debugging on the production server.  How does the PDB file relate to debugging?

J  

kaufmed,

Sorry for the slow response.  Thanks for the terrific response and follow up.

ASP.NET - PDB and XML files located in the bin folder.

I created an ASP.NET project, ProjectX.  I ran a build and dropped the build files onto the production web server.  

I then modified some of the code under one of the ASPX pages, copied the modified ProjectX.dll from my development machine, and pasted it to the production server, overwriting the earlier copy.  

Here&amp;#39;s the question, should I copy and paste ProjectX.pdb and ProjectX.xml to the production server as well?

If yes, why?

If no, why?

The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications

ASP.NET

Visual Basic .NET (VB.NET) is an object-oriented programming language implemented on the .NET framework, but also supported on other platforms such as Mono and Silverlight. Microsoft launched VB.NET as the successor to the Visual Basic language. Though it is similar in syntax to  Visual Basic pre-2002, it is not the same technology,

Visual Basic.NET

C# is an object-oriented programming language created in conjunction with Microsoft’s .NET framework. Compilation is usually done into the Microsoft Intermediate Language (MSIL), which is then JIT-compiled to native code (and cached) during execution in the Common Language Runtime (CLR).