<div>
James,<br />
<br />
Your response is one of the best EE responses I've ever seen (and I've seen quite a few). &nbsp;I've incorporated the full posting into my .NET lesson. &nbsp;<br />
<br />
Thanks!<br />
<br />
J
</div>


James,

Your response is one of the best EE responses I've ever seen (and I've seen quite a few).  I've incorporated the full posting into my .NET lesson.  

Thanks!

J

<div>
<div class="content wysiwyg-content">
What files need to get pushed to the production machine for a console app? &nbsp;You'll notice the app.config file is missing. &nbsp;I didn't use one in this project.<br />
<br />
AutoEmail.application - Don't think I include.<br />
AutoEmail.exe - Include<br />
AutoEmail.exe.config - Not sure<br />
AutoEmail.exe.manifest - Not sure.<br />
AutoEmail.pdb - Not needed if I don't need to debug the deployment.<br />
AutoEmail.vshost.applicati<wbr />on - Not sure.<br />
AutoEmail.vshost.exe - Don't think I need it.<br />
AutoEmail.vshost.exe.confi<wbr />g - Don't think I need it.<br />
AutoEmail.vshost.exe.manif<wbr />est - Don't think I need it.<br />
AutoEmail.xml - Not sure.<br />
<br />
Obviously, if I overcompensate, and deploy all or many of these files, it will work. &nbsp;My objective, however, is to deploy only what's necessary.
</div>
</div>


What files need to get pushed to the production machine for a console app?  You'll notice the app.config file is missing.  I didn't use one in this project.

AutoEmail.application - Don't think I include.
AutoEmail.exe - Include
AutoEmail.exe.config - Not sure
AutoEmail.exe.manifest - Not sure.
AutoEmail.pdb - Not needed if I don't need to debug the deployment.
AutoEmail.vshost.application - Not sure.
AutoEmail.vshost.exe - Don't think I need it.
AutoEmail.vshost.exe.config - Don't think I need it.
AutoEmail.vshost.exe.manifest - Don't think I need it.
AutoEmail.xml - Not sure.

Obviously, if I overcompensate, and deploy all or many of these files, it will work.  My objective, however, is to deploy only what's necessary.

.NET - x86 Project - What files need to get pushed to the production machine?

.NET application servers, a Windows Server role in an application role, includes Internet Information Services (IIS) to provide web server support, the .NET Framework to provide application support, ASP.NET to provide server side scripting, COM+ for application component communication, Message Queuing for multithreaded processing, and the Windows Communication Foundation (WCF) for application communication. There are also third party server systems that provide .NET support, including Mono, Base4, TNAPS and cc Devnet Data Access Server.

.NET App Servers

The .NET Framework is not specific to any one programming language; rather, it includes a library of functions that allows developers to rapidly build applications. Several supported languages include C#, VB.NET, C++ or ASP.NET.

.NET Programming

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).